Chasing bad SPI checksums.

gtj0

@wilriker Can I just say "ew"?

Get a Jetson Nano.

Danal

First, my cable layout. Nothing really near; nothing crossing; anything even sort of near at 90 degrees.

Second, no joy on eliminating thermal management of the core clock.

/boot/config.txt
core_freq=250
core_freq_min=250

And a reboot does not eliminate all of my checksum messages. I'm beginning to think I have a hardware problem. Time to power off and re-seat cables.

By the way, I did check that the commands had the desired effect:

pi@duet3:~ $ vcgencmd measure_clock core
frequency(1)=250000496
pi@duet3:~ $ vcgencmd measure_clock core
frequency(1)=250000496
pi@duet3:~ $ vcgencmd measure_clock core
frequency(1)=250000496

Danal

Well... very VERY interesting. Hard to prove a negative... but... I reseated the ribbon cable at both ends, and as of this moment, I've run about 5x the testing that reliably produced a checksum error in the past, with no errors logged.

Update: Hours and Hours of printing. No Checksum errors.

Looks like re-seating the cables fixed it.

3mm

And in your spare time you fly 5 T-Rex's...heh heh. Is there no limit to your robopsychosis?