Network

[tinspin]

Found these:

https://github.com/rsta2/circle
https://github.com/rsta2/circle/tree/master/addon/wlan/sample/hello_wlan

Now I just need to figure out the C64 side...

I think a ELI5 for the C64 -> Zero interface would be awesome.

First what is the difference between the sidekick and the rad.

Which pins do what and how can you access them from the Pi/C64?

Even two simple basic+asm programs to POKE things over to the Pi and a simple C program to send things to the C64 would be nice!

[frntc]

A good example for C64<->RAD communication via the IO-address range is https://github.com/frntc/RAD/blob/main/Source/Firmware/rad_georam.h

... in includes a small loop handling the bus communication, and has two functions for reading and writing values.

For LAN/WLAN: keep in mind that the network on the RPi is a USB-device and Circle handles USB-communication via interrupts. Unfortunately these interrupts can (and do!) interfere with the bus communication and screw things up very easily. You might want to have a look at the Sidekick64-network kernals by @hpingel : https://github.com/hpingel/Sidekick64

The difference between Sidekick64 and RAD: the interfacing logic to map the many expansion port signals to the few GPIOs is very different, thus the intersecting set of functionality of the 2 cartridges is quite small.

[tinspin]

Does https://github.com/frntc/RAD/blob/main/Source/Firmware/rad_georam.h use the same data pins as are present on the user port? IE would the same code translate somewhat to the Wic64 if you disregard the Hayes part?

What about C64 -> Zero?

Wait, sidekick64 has network?

I found https://github.com/hpingel/Sidekick64/blob/net-rebase-on-v0.51d/Source/Firmware/net.h is that correct?

Can you draw us a picture of how RAD and SideKick differ in routing the pins? Could you (in theory) make a PCB that has a switch to flip between them?