Raven060 (kodak80 build)

[kodak80]

I updated the firmware in my UniJoysticle 2 and thought I would test it on the Raven. The UniJoysticle 2 PCB is my design with just a single 9 pin connector. It did not fit under an Atari ST standard computer so I had almost filed it in the bin but it fits perfectly on the Raven socket.

IMG_0871.jpg (251.54 KiB) Viewed 1463 times

IMG_0872.jpg (205.39 KiB) Viewed 1463 times

Works as designed. Tyrian works fine with the Xbox controller. Doom, works but have not figured out how to open a door with the Xbox controller.

[kodak80]

Just documenting my AUTO folder and order I use with my PicoGUS v2 (with wavetable attached for MIDI).

I have the PicoGUS set to SoundBlaster mode and this is saved:

pgusinit.prg /mode sb /save

Once the above have been run, I do not need PGUINIT.PRG unless I want to change the settings.

Below is the files and order in my AUTO folder and are used for a standard EmuTOS boot only.

AUTOEXEC.PRG
ISA_BIOS.PRG
RVBIOS.PRG
RVNOVA.PRG
SETENV.PRG
MPU401.PRG

MPU401.PRG is needed to have the wavetable MIDI active on my PicoGUS v2. If this is not loaded, I get no MIDI sound output.

I have my ScummST games set to:
Sound driver: SoundBlaster
Music driver: General Midi

[luciodra]

MPU401.PRG is needed to have the wavetable MIDI active on my PicoGUS v2. If this is not loaded, I get no MIDI sound output.

I have my ScummST games set to:
Sound driver: SoundBlaster
Music driver: General Midi

But you have this expansion, right? I don't and to get midi music I have to start Oplmidi...

Raven060 kodak80 PicoGUS v2.0 20241219.jpg (42.4 KiB) Viewed 1378 times

[kodak80]

MPU401.PRG is needed to have the wavetable MIDI active on my PicoGUS v2. If this is not loaded, I get no MIDI sound output.

I have my ScummST games set to:
Sound driver: SoundBlaster
Music driver: General Midi

But you have this expansion, right? I don't and to get midi music I have to start Oplmidi...

Raven060 kodak80 PicoGUS v2.0 20241219.jpg

Correct, OPLMIDI.PRG redirects MIDI to the PicoGUS (SoundBlaster mode) as OPL audio. If I remove MPU401.PRG and add OPLMIDI.PRG in my AUTO folder, the MIDI is sent direct to the PicoGUS and audio is processed through the 3.5mm audio output.

With the OLMIDI.PRG running, Doom, Tyrian and the ScummST games audio all still works, but the audio is a bit tinny compared to having the MIDI played by the wavetable device.

I am also running the latest update for the PicoGUS: https://github.com/polpo/picogus/releases/tag/v2.2.0

[luciodra]

Correct, OPLMIDI.PRG redirects MIDI to the PicoGUS (SoundBlaster mode) as OPL audio. If I remove MPU401.PRG and add OPLMIDI.PRG in my AUTO folder, the MIDI is sent direct to the PicoGUS and audio is processed through the 3.5mm audio output.

With the OLMIDI.PRG running, Doom, Tyrian and the ScummST games audio all still works, but the audio is a bit tinny compared to having the MIDI played by the wavetable device.

I am also running the latest update for the PicoGUS: https://github.com/polpo/picogus/releases/tag/v2.2.0

With your suggestions I got midi sounds on mxplay and jam. Scumm, gnuboy and Tyrian ok. Unfortunately Doom can hear sfx and midi but after a few minutes it freezes . If I launch it without oplmidi I only have sfx but the game is stable.
Does Doom work well with sfx and midi for you ?

Small note, to set Picogus remembering the SB firmware upon reboot I have to give:

Code: Select all

pgusinit /mode sb /save

in the same line.

[kodak80]

I jumped the gun and already ordered these PCBs.

I've built mine today and from an initial quick test the hardware appears to work.
Though it looks like there's an important software issues to fix before it's properly usable -- I tried a non-debug build for the first time and notice mouse isn't entirely happy (same behaviour for usb, ps2 and joyport mice which I'm happy about since that strongly indicates a problem in the common mouse code)

I'm sure more stuff will be found when the more uncommon ikbd modes are tested too so don't throw away that Eiffel PIC just yet

Unimplemented so far:
- fan control
- cpu temp (requires motherboard patch wire)
- software power-off (requires motherboard patch wire + Raven support in MiNT)

Untested so far:
- joyport mouse right button (requires motherboard patch wire)

You shouldn't need to solder J104 if you don't want to, but it also won't hurt it you do.
Normal operation is having the header completely open (support for external oscillator is not implemented)
First-time programming can be done without jumpering for programming mode, and subsequent programming can be initiated from software. Jumpering for programming mode should only be needed if it for some reason ends up bricked.
Pin0 is 115200 baud serial output for debug builds of the firmware

Also don't forget to remove the pin for the key position if you're using a normal 2x5 pinheader on J103

Screenshot 2025-06-18 at 23.21.49.png

Chips arrived, CKBD rev.C board built, CH559L chip programmed. Quickly tested in my Raven with PS2 mouse and keyboard and they seem to work fine. Will look to test USB over the weekend all being well.

IMG_1155.jpg (341.99 KiB) Viewed 1182 times

IMG_1156.jpg (286.19 KiB) Viewed 1182 times

[agranlund]

usb.png (1.02 MiB) Viewed 1166 times

(most internal usb plugs have that position blocked)

In hindsight, I should have changed the footprint to not have a through-hole there.

[agranlund]

If you need to change settings you can manipulate them directly from the raven serial monitor:
(Update: I realised you need the latest bootrom to do these things. I'll make a new release package this weekend )

reading a value (it prints 4 bytes starting at the index you specify)
kbd get <idx>

setting a value
kbd set <idx> <byte>

commit changes to ckbd flash
kbd save


fuint16_t scaling values are 16 bit fixed point in 8.8 format. The first byte of the setting is the decimal part and the second is the integer.

for example, set Usb mouse scale to 1.0

Code: Select all

kbd set $14 0
kbd set $15 1

example, set Usb mouse scale to 1.5

Code: Select all

kbd set $14 128
kbd set $15 1

example, setting legacy mouse mode to Amiga

Code: Select all

kbd set $22 1

Here's the entire settings structure (the eiffel parts can be manipulated with the EiffelCF program)

Code: Select all

typedef struct
{
/* 0x00 */  uint32_t Magic;
/* 0x04 */  uint32_t Version;
/* 0x08 */  uint32_t Changed;
            uint8_t pad0C[4];
/* 0x10 */  fuint16_t PS2MouseScale;
/* 0x12 */  fuint16_t PS2WheelScale;
/* 0x14 */  fuint16_t UsbMouseScale;
/* 0x16 */  fuint16_t UsbWheelScale;
/* 0x18 */  fuint16_t LegacyMouseScale;
            uint8_t pad1A[6];
/* 0x20 */  uint8_t UsbKeyboardReportMode;          // usb keyboard boot or report mode
/* 0x21 */  uint8_t UsbMouseReportMode;             // usb mouse boot or report mode
/* 0x22 */  uint8_t LegacyMouseAmiga;               // atari or amiga mouse
/* 0x23 */  uint8_t CoreTempShutdown;               // abbbbbbb. a = enable, b = temp (0-127)
/* 0x24 */  uint8_t FanControl0;
/* 0x25 */  uint8_t FanControl1;
            uint8_t pad26[10];
/* 0x30 */  settings_eiffel_mouse_t EiffelMouse;    // eiffel mouse settings
/* 0x38 */  settings_eiffel_temp_t EiffelTemp[2];   // eiffel temperature tables
/* 0x6C */  uint8_t EiffelKeymap[0x90];             // eiffel keyboard usertable

} settings_t;

[kodak80]

Additional USB erroneous header pin has been removed and I found a USB motherboard adapter to fit the rear slots and have now successfully tested a Dell USB keyboard and USB Microsoft Basic Mouse.

Both work fine.

I guess I will need to get the various firmware updates just released programmed and tested...

https://github.com/agranlund/raven/rele ... .A1.latest

[agranlund]

Dell USB keyboard and USB Microsoft Basic Mouse.
Both work fine.

That's awesome! Always very nice to know it worked for someone else too and not just my particular setup