We used RevPi in many projects and recently encountered to a weird behavior using RevPi Bookworm 64-bit Lite (01/2025)
Hardware used are as below and both of them are configured in PiCtory correctly.
1) RevPi Core S
2) RevPi DIO
When check with piTest -d, expecting to see only 2 devices but it show 4 devices as below picture.
So we remove both of them in PiCtory and configure to below instead.
1) RevPi Connect S
2) RevPi DIO
And check with piTest -d again, everything seems work perfectly as below picture.
Running piTest with all the input and output for both RevPi Core S and RevPi DIO also woked perfectly.
But the weid thing is actual hardware is RevPi Core S instead of RevPi Connect S.
We have also tried revpi-factory-reset and piTest -x but the behavior is still the same.
Would you help review if we missed out something here?
RevPi Core S has to be configured as RevPi Connect S in PiCtory
RevPi Core S has to be configured as RevPi Connect S in PiCtory
Last edited by tsm on 13 Mar 2025, 18:17, edited 1 time in total.
Re: RevPi Core S has to be configured as RevPi Connect S in PiCtory
Hello tsm can you send an SOS report?
https://kunbus-gmbh.atlassian.net/servi ... 2036400208
https://kunbus-gmbh.atlassian.net/servi ... 2036400208
Re: RevPi Core S has to be configured as RevPi Connect S in PiCtory
Just to close the loop that we decided to use RevPi Bookworm 64-Bit Default (01/2025) instead and the issue was resolved.
Unfortunately we haven't create the SOS report yet and we don't have the chance to reproduce it again at the moment.
Thank you Dirk for the idea about SOS report.
If something weird happens next time, we will create it before installing the new image.
Unfortunately we haven't create the SOS report yet and we don't have the chance to reproduce it again at the moment.
Thank you Dirk for the idea about SOS report.
If something weird happens next time, we will create it before installing the new image.
Re: RevPi Core S has to be configured as RevPi Connect S in PiCtory
My guess is that during factory reset the wrong device was selected and thus the picontrol driver expected a different device to be present.