Upgrade from 3.5.2 to 3.5.3, sbc mode, not connecting

bug2k22

I have a 6HC connected to a Pi5 and has been running on version 3.5.2.
Have just upgraded from the Pi and now I am unable to connect to the web interface. I am getting the message "Could not connect to the Duet: Timeout while waiting for transfer ready pin."
When upgrading I received this on the reprapfirmware update:

Setting up reprapfirmware (3.5.3-1) ...
There is 1 outdated board:
- Duet 3 MB6HC (3.5.2 -> 3.5.3)
Would you like to update them all (Y/n)? y
Updating firmware on mainboard... Error: A task was canceled.

I had a similar issue with another machine where the issue was the "GpioChipDevice" line in the file /opt/dsf/conf/config.json. This line appears to be correct. I have tried deleting the file and it has been recreated automatically, but I still have the same error.

Any help appreciated.

jay_s_uk

@bug2k22 what's the diag LED light like on the 6HC? Is it flashing once a second or is it dim?

bug2k22

@jay_s_uk said in Upgrade from 3.5.2 to 3.5.3, sbc mode, not connecting:

@bug2k22 what's the diag LED light like on the 6HC? Is it flashing once a second or is it dim?

All four 'power' leds are lit, the 'status' and 'act' are not lit.

This was working before the upgrade.

Phaedrux

https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6HC_Hardware_Overview#led-indications

If the status LED is off or dim, that means the firmware was erased for flashing, but the flash wasn't successful for some reason.

All is not lost though. The firmware can always be reflashed using a USB connection and flashing software. See here for detailed instructions.

https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_firmware#fallback-procedure-2

bug2k22

@Phaedrux Reflashing the firmware has fixed the issue. I think I'll perform any reprapfirmware updates first from the web interface and then upgrade the rest of the components from the pi terminal, this is the second of my machines that has problems upgrading the firmware from the apt terminal update/upgrade.

Phaedrux

@bug2k22 said in Upgrade from 3.5.2 to 3.5.3, sbc mode, not connecting:

I think I'll perform any reprapfirmware updates first from the web interface

That will definitely result in issues. When using SBC mode you must use the Pi terminal to update. On the rare occasion when an update fails, that's when a usb reflash may be required, or if the firmware is still present but hasn't updated, you may send M997 to trigger a manual flash.