Yeah, with this older Core3 it only works with Stretch and Bulleyes, but with the more recent version the DIO were not visible.

Four years ago it worked perfectly. Then the installation was not used for a long time. Recently upgrading to Bookworm, the installation with the Core 3 does not see the DIO. Then I started testing. Both DIO's works with an older Core 1 with Stretch, but with the Core 3 both don't work. Tested both ...

I wanted to test the DIO on the other site of the core, but now PICtory (from bookworm cockpit) does not start from within cockpit.
Strange as it did worked nicely as of yesterday. How to reinstall PICtory extension in cockpit?

sorry on the Core it doesn't work.

Did it already, but piTest -f come back with "Virtual modules don't have firmware to update" I thought may be it is because both DIO have not be used for around 4 years (last login on Core 1 was in 2020) I swap it with a Core (1) system with Strech. There it runs fine (all three green ligh...

RevPi setup worked 4 years ago fine (Strech release), installed recently Bookworm, but DIO does not come up. pi@RevPi17181:~$ piTest -d Found 2 devices: Address: 0 module type: 95 (0x5f) RevPi Core V1.2 Module is present input offset: 0 length: 6 output offset: 6 length: 5 Address: 32 module type: 3...

I got it running by deductive testing. An unreliable USB cable was the cause of the problem. After switching on the RevPi with the rotten cable the RevPi lights did lit up for a Rpiboot boot, but no data was received either at the Unix or the Windows machine. It was not a bad connection in the compu...

New to RaspberryPi, I started with a new Revolution setup, everything works fine (local, headless, etc), but rpiboot doesn't get beyond the Waiting for ..

Tried with a Windows PC and with an Ubuntu machine following all the instructions and connection/start order.

What can I do next? any tips?