Module is NOT present, data is NOT present

[ejsol]

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: 32864 (0x8060) RevPi DIO V0.0
Module is NOT present, data is NOT available!!!
input offset: 11
length: 70
output offset: 81 length: 18

PICtory looks fine, swapped this DIO with another DIO, same problem. Core 3 light become green, but DIO licht remains red.

What to do?

[dirk]

Hello ejsol, okay maybe your modules need an update as well - please try to update the firmware of the module(s):
https://revolutionpi.com/en/tutorials/i ... are-update

[ejsol]

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 lights are on)

see attachment: "Module is present, Address: 32 module type: 96 RevPi DIO V1.4"

Strange, on bookworm on a Core 3 it does work, on an older Core 1 with Strech is does work?

Any tips what to do next. (I can't update/upgrade stretch anymore, not maintained).

[ejsol]

sorry on the Core it doesn't work.

[ejsol]

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?

[ejsol]

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 with Bullseye and Bookworm. Tested with the DIO one time on left and one time on the right side. I also run PICtory from a Mac and Windows computer and from the Core 3 itself to exclude that the configuration file by PICtory was not properly saved, but that seems neither the case. The DIO main led remains (blinking) red and piTest is reporting that there is no module present.

[dirk]

Hello ejsol, Okay, the RevPi Core 1 is unfortunately a bit weak on the chest with only one CPU core. It is therefore no longer compatible with the latest images. I recommend that you switch to the latest hardware. But you still have a RevPi Core 3 module in use. If it still has 4 GB eMMC then this module also dates back to the early days of the Revolution Pi era. If this is the case, then unfortunately I can't guarantee anything because the manufacturer's warranty has also expired. However, you are welcome to send us and me an SOS report so that we can take a closer look at things.
https://kunbus-gmbh.atlassian.net/servi ... 2036400208

[ejsol]

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

[dirk]

Dear ejsol,
okay, I didn't really understand that means the communication doesn't work with this image? Or can you try it with this freshly released image?

• RevPi Bookworm 64-bit (10/2024) (ID: 9162)

Can you please check whether the firmware of the IO modules can be updated? This works quite simply with executing the command as long as there are modules that can be updated:

Code: Select all

piTest -f

In general, please follow the steps in this helpful checklist:

• Revolution Pi Checklist

If the faulty behavior persists, can you please send me and us an SOS report? Thank you!