Downgrading to kernel 5.10.152 removed the errors with AIO. When upgrading again to the latest kernel, the errors came back.
I am happy to provide an img file of the system.
I ran piTest -f and the last line could be a clue. The lines are printed in reverse order as I used journalctl -r. May 01 21:16:00 Pi1 kernel: pi-bridge serial1-0: receive head error in io-req May 01 21:15:58 Pi1 kernel: piControl: piAIOComm_Init(30) done 0 May 01 21:15:58 Pi1 kernel: piControl: piA...
The above commands worked and I have updated the bootloader to 1:1.20230405-1. The vcgencmd is also up to date. I am still getting errors in journalctl. I have also noticed that /var/log will get filled up after ~2 days due to the error messages. Then network is affected, it disconnected after too m...
Thank you for your reply. It looks like the bootloader is indeed older. dpkg -l |more ii raspberrypi-bootloader 1:1.20230509~buster-1 armhf Raspberry Pi bootloader I upgraded the Kernel using the instructions below and vcgencmd is now correct, but the issue still appears. Download the latest Bullsey...
No packages awaiting to be upgraded. I was thinking about how to upgrade the raspberrypi-bootloader and I tried the following in two separate attempts: sudo rpi-update sudo rpi-update 22d9210842402780c9e6c74668b2d3eae94c5192 didn’t work However, I would get errors such as: This appears on startup fa...
I know it is due to the upgrade as I was not getting the error message before the upgrade to Bullseye. Do you want me to update the bootloader? Is there anything I can do to debug the piControl driver? I am also reading the RS485 channels and the AIO and I saw the update to kernel 6.1 relates to the...
Hi Nicolai, Attached is the SOS report. Unfortunately, it is an upgraded image which was upgraded to Buster and then to Bullsesye which is required for the Connect 4. The same symptoms are with this forum poster who has also upgraded. https://revolutionpi.com/forum/viewtopic.php?p=15160 cat /etc/rev...