spi connection resets
-
Im having from some time many SPI conection resets sinbce upgraded to 3.5. Im not saying is the reason but yes I have noticed a considerable increment on this events.
Probably I will create a brand new sd card image to start from fresh (this one has been being upgraded since version 3.1 all the way to 3.5.2)
Just to try to detect other sources, can someone please list all potential causes for this?
Also, Im thinking on creating a macro to detect this and launch the resurrect.g file as if a power failure happened. Do you think this would be possible? Ideas on how to detect a spi event happened?Thanks in advance for the help. This is a duet3 + SBC, 3.5.2 firmware
-
@Tinchus These errors seem to fall into three categories:
- Interference on the SPI bus, caused by motor/heater wires running too close to the unshielded ribbon cable between RPi and Duet. Fix: reroute noisy wires, shield ribbon cable with ferrite and aluminium foil
- Possibly too much IO happening on the RPi, or failing SD card. Fix - replace SD card, re-image SD card
- Other RPi-based issues eg firmware update.
Here are a few threads on "Warning: SPI connection has been reset" errors.
https://forum.duet3d.com/topic/35993/significant-warning-spi-connection-has-been-reset - fix was to update RPi 5 firmware
https://forum.duet3d.com/topic/35709/spi-connection-reset-on-duet-3-mini-5/ - possibly interference from other wires
https://forum.duet3d.com/post/330279 - interference analysis from @timschneider
https://forum.duet3d.com/topic/34349/spi-reset-issue-after-upgrading-duet-firmware - possible slow or failing SD cardIf none of that helps, post what steps you have taken, post the RPi logs, and @chrishamm may be able to take a look and help.
Ian
-
@droftarts Thanks very much for all the info. I guess my most probable cause the sd card, may be is too old by now (been under heavy use for 3 years I think? and also has been upgraded for at least 5 times for sure a little more).
Thanks!