Firmware update bricked printer - SPI connection has been reset

jay_s_uk

@p8blr it looks like 3.5.3-rc1 isn't currently on the DSF package feed so you can't update to it in SBC mode

p8blr

@jay_s_uk Interesting. How did you check that so I know for future reference? Is there no manual way to update firmware in SBC mode?

jay_s_uk

@p8blr was reported in the other thread. And you shouldn't manually update as there may be breaking changes between the firmware and DSF

timschneider

@p8blr was the extended delay able to get rid of the unknown driver messages?

the M122 looks normal to me.

p8blr

@timschneider The delay didn't make a difference, however, changing the brake code to S10 from S1000 seems to have fixed that particular issue.

M569.7 P0.2 C"out3" S10 ; driver 2 on board 6XD uses port out3 to control the brake
M569.7 P0.3 C"out4" S10 ; driver 3 on board 6XD uses port out4 to control the brake
M569.7 P0.4 C"out5" S10 ; driver 4 on board 6XD uses port out5 to control the brake
M569.7 P0.5 C"out6" S10 ; driver 5 on board 6XD uses port out6 to control the brake

Note that I was playing with increasing that value because my servos were getting position recovery errors.

chrishamm

@p8blr It's now available, looks like the GitHub Actions workflow for prereleases wasn't triggered correctly. Sorry for the inconvenience.

p8blr

@chrishamm Didn't work.

Process:
Removed SD card from duet, connected RPI ribbon cable, powered on, M997 S2 F"unstable", sudo apt update, sudo apt full-upgrade

chrishamm

@p8blr /dev/gpiochip4 is correct for the Pi 5. Is it still the same board or did you replace it?

p8blr

@chrishamm Exact same board. I'll reimage the pi and try again.

chrishamm

@p8blr If it's actually caused by a system update, don't use apt to install the latest system package versions, instead use M997 S2 only to update DSF. I'll investigate.

p8blr

@chrishamm new image with no updates works. M997 S2 F"unstable", M997 S2