Raven060 (kodak80 build)

[agranlund]

Edit2: Made my own TRS to MIDI adapter cable....I now have MIDI output from the PicoGUS using MXPlay under EmuTOS output to my MT32-Pi.

Awesome!! :cheers:

On other news...It was a rainy day here on Saturday, so Aussie Raven060 number 2 has now been built/hatched and is up and flying.

Ooh, that makes Australia tied for the lead with Sweden!
Though my first one is just acting as a piece of wall-art nowadays so that probably puts Australia in the lead actually.

[JezC]

Edit2: Made my own TRS to MIDI adapter cable....I now have MIDI output from the PicoGUS using MXPlay under EmuTOS output to my MT32-Pi.

Awesome!! :cheers:

On other news...It was a rainy day here on Saturday, so Aussie Raven060 number 2 has now been built/hatched and is up and flying.

Ooh, that makes Australia tied for the lead with Sweden!
Though my first one is just acting as a piece of wall-art nowadays so that probably puts Australia in the lead actually.

I'm more than a little envious of that bit of wall art!
:D

[agranlund]

I note that the PicoGUS has a new update available:
https://github.com/polpo/picogus/releases/tag/v2.2.0

I've just updated the Atari version of pgusinit from latest on Ian's Github.

It looks like the changes are mostly about being able to use the new NE2000/Wifi feature.
Which... I suspect will work on Raven using "drivers/ne2000/eneh.xif"

I haven't been able to test the new pgusinit.prg so give us a shout if it's borked :)

[kodak80]

I note that the PicoGUS has a new update available:
https://github.com/polpo/picogus/releases/tag/v2.2.0

I've just updated the Atari version of pgusinit from latest on Ian's Github.

It looks like the changes are mostly about being able to use the new NE2000/Wifi feature.
Which... I suspect will work on Raven using "drivers/ne2000/eneh.xif"

I haven't been able to test the new pgusinit.prg so give us a shout if it's borked :)

Thank you. Will look to test this. Network card was my next step. So will see how the PicoGUS NE2000/Wifi works as well now. Need to build another PicoGUS with the Pico W. The first 2 boards have a non-W Pico soldered directly to the main PCB.

[kodak80]

PicoGUS v2.0 arrived today. Got the S2 wavetable card installed and this now outputs midi audio from the Raven060 without the need for the MT32pi.

Raven060 kodak80 PicoGUS v2.0 20241219.jpg

[kodak80]

I have soldered up and built another PicoGUS v1.2 board to allow me to play and test the new NE2000 Wifi network functionality.

Took some time to get the SMT components soldered in place. I initially tested this with the normal PicoGUS v2.2.0 firmware and confirmed that the MIDI files still played with mxPLAY. Audio output was working fine.

I then swapped the Pico for a wireless one programmed with the new pg-ne2k.uf2 firmware.

The new pgusinit.prg works fine to set the wireless SSID and password. /WifiStatus shows that it is connected. :)

Now I need to get the Atari and FreeMint network side going. Happy that the new PicoGUS board is working.

[kodak80]

I tried using the new PicoGUS with a Pico W with the network firmware but was struggling to get things working.

I decided to use a known working ISA network card I had built and were working on my MicroATX Atari with EtherNEC adapter.

kodak80 isa8_eth boards.jpg

At first, I was struggling with getting STing working under EmuTOS in my Raven060. Some of this was reminding myself on how STing is configured to work.

Here are the steps (from memory) I followed:
1. copy STING folder and files to C:\STING
2. copy 3x STing CPX files to C:\CPX
3. copy STING.PRG and STING.INF to C:\AUTO
4. edit STING.INF to contain the location of STING:

Code: Select all

C:\STING

5. copy Raven NE2000 driver eneh.stx to C:\STING
6. edit STING\ROUTE.TAB to set my router IP as the route address shown on the last line below as 192.168.1.1 (Each item on the line is separated by TABs) Use your own router IP address:

Code: Select all

#
#  This is the routing table, to be used by the router to route IP datagrams
#
#  Format of routes comprises four entries, separated by TABs :
#    - First the network (subnet number) which can be reached by using this
#       route.
#    - Next the subnet mask associated with that network.
#    - Then the port name follows. This is the name as listed by ConfSTinG or
#       STNGPORT.CPX.
#    - Last entry is the IP address of a host on the attached network that 
#       can act as a gateway.
#
#  The network specified can be directly attached to the specified port, in
#  that case no gateway is needed, as the datagram can be routed directly.
#  For a route to a network that is directly attached therefore the gateway 
#  entry should be set to 0.0.0.0.
#
#  For an attached Ethernet the gateway entry specifies the gateway out of 
#  the Ethernet, for a serial line it is simply the host at the other end.
#
#  It is advisable to finish the table by a default route. This route is most
#  easily obtained by specifying a network 0.0.0.0 with a netmask 0.0.0.0.
#
#  Routes with invalid addresses or absent ports are ignored.
#
# 192.68.0.0		255.255.255.240		Modem 1		192.68.0.1
# 130.75.75.0		255.255.255.128		Ser.2/LAN	0.0.0.0
# 0.0.0.0		0.0.0.0			Ser.2/LAN	130.75.75.16
#
# 192.168.255.2	255.255.255.0	EtherNet	192.168.255.1
# 0.0.0.0		0.0.0.0		Modem 1		0.0.0.0
0.0.0.0		0.0.0.0		EtherNet		192.168.1.1

7. Edit STING\DEFAULT.CFG to set the NAMESERVER:

Code: Select all

#  The one following is also redefined by the dialer, and you only need to
#  define it here if you use a local network, so all machines in that net
#  can find the nameserver (the dialer only defines it on one machine).
#  Note that the value of NAMESERVER variables should always be a numeric
#  IP address, since another nameserver would be needed to resolve a URI.
#  You can specify more than one address, separated by ", " .
#   (eg: "NAMESERVER = 193.45.240.2, 193.45.240.4")
#
NAMESERVER  = 8.8.8.8

8. reboot Raven060 to activate STing
9. Open Control Panel
10a. Open STing Port Setup. Set IP address and Subnet Mask to your network settings. Ensure the Active checkbox is crossed/active.
10b. Click on the Addressing box and select General. The under Choose Hardware, click and select the NE2000. Ignore the MAC address as this is set from your network card when you click the OK button.
11. Save your STing Port Setup settings. Save to C:\STING.PRT
12. Now open the STing Protocols CPX and check/set the RESOLVER has the NAMESERVER you set in step 7.
13. reboot Raven060 to activate STing once more to boot with your new settings.
14. Use STING\TOOLS\PING.PRG to set pinging 8.8.8.8 and it should work.

Here are the files from my Raven060 for my STing setup:

STING-Raven060-KDK.zip

[luciodra]

Great guide, and that's pretty much what I did, but the ping isn't going in or out. I need to try connecting Raven directly to the Mac.

[kodak80]

Just updated the MC68150 to the MOT FN40 version although the Freescale FN33 chips were working fine. Picture shows both chips.

Raven060 kodak80 MC68150FN40 20241223.jpg

[agranlund]

Thanks for the guide!
I’ve never really tried Sting but with that guide it feels like I have to give it a go :)