Duet3 Expansion Board 3hc blocks during downgrade

jay_s_uk

@danielpetrea it would involve the use of S3 in the M997 arguement but I wouldn't recommend downloading the bootloader, especially not to a version lower than 2.3 as there were issues with some of the timing code. And as I stated before, I also don't know whether the firmware is bootloader dependant

DanielPetrea

@jay_s_uk i uploaded the bootloader 2.3 but when i upload firmware 3.1.1 the expansion board don't work (led status not blinking).

jay_s_uk

@danielpetrea i'm not sure what to further suggest then. maybe @Phaedrux can comment?

DanielPetrea

@jay_s_uk after uploaded the bootloader 1.3 on expansion board 3hc , the status led blinks 3 times.
Do you know what this is meaning? thanks

jay_s_uk

@danielpetrea they're listed here https://docs.duet3d.com/User_manual/Machine_configuration/CAN_connection#led-behaviour-and-error-codes
3 blinks is Bad firmware CRC

DanielPetrea

@jay_s_uk said in Duet3 Expansion Board 3hc blocks during downgrade:

s Bad firmware CRC

do you know what should be the cause to this error? i tried to install the firmware 3.1.1 with hard reset procedure (all swich off and then power on) but don't upload this firmware

jay_s_uk

@danielpetrea i don't i'm afraid. but as i've said before, all of the CAN-FD boards perform poorly using 3.1.1

DanielPetrea

@jay_s_uk i'm using this firmware with other machines and works well, i don't encountered CAN problems with 3.1.1.
What's the difference between Duet3 EB 3HC v1.0 and Duet Eb3HC v1.0.1 ?
Thanks

DanielPetrea

@danielpetrea Anyone who can assit me to solve this problem? Thanks

Phaedrux

Is there no way to bring the customized firmware up to date?

dc42

@danielpetrea said in Duet3 Expansion Board 3hc blocks during downgrade:

@jay_s_uk said in Duet3 Expansion Board 3hc blocks during downgrade:

s Bad firmware CRC

do you know what should be the cause to this error? i tried to install the firmware 3.1.1 with hard reset procedure (all swich off and then power on) but don't upload this firmware

It sounds to me that the customised firmware for the 3HC doesn't have the CRC appended at the end of the build step.

DanielPetrea

@dc42
Hi,
This error is generating when i try to upload the official release. First at all i want to install the official release then i proceed with the customized firmware.

DanielPetrea

@Phaedrux
For this moment i'm not planing to update this firmware, i understand that is a good update but for now the timing don't alows me. I don't understand why this board is not retro compatible? There is any reason?

Phaedrux

Is the Duet3 currently running the Duet 3.1.1 firmware, or your custom firmware?

Can you provide a M122 and M122 B# for the 3HC when it is responding?

Can you please try uploading this zip file for 3.1.1 (as is, don't extract it first) to the system tab in DWC and allow it to update the firmware again.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip

At that point, what state is the 3HC in?

DanielPetrea

@phaedrux Hi,
I'm starting from this situation:
m122 b0
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7J1FL-3S46L-KSK38
Used output buffers: 1 of 40 (20 max)

m122 b1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.4.0 (2022-03-15 08:59:40)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
All averaging filters OK

the boards works well.

I upload the ZIP file of 3.1.1 (https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip)
confirm to update
AFTER
m122 b0
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7J1FL-3S46L-KSK38
Used output buffers: 1 of 40 (20 max)

m122 b1
Error: M122: Response timeout: CAN addr 1, req type 6024, RID=12

the Expansion board diag LED don't blink and don't response to the mainboard.

dc42

@danielpetrea there was an issue with clock startup that affected both the bootloader and the main firmware on some expansion boards. It's dependent on VIN voltage and temperature, so a board can pass our testing, and even work for a while in a machine, before ceasing to start up reliably - for example of the temperature has changed. The symptom was that the power LEDs light up, but the red activity LED doesn't blink either continuously or intermittently to signal an error.

I made a series of changes to the startup code to fix this, the final one being in April 2021. But firmware 3.1.1 was released in May 2020 so it doesn't include these changes. I think it's likely that this explains why firmware 3.1.1 won't start up on that board. It's possible that if you leave the board powered up for an hour or two, it may eventually start up.

I strongly advise against running such old firmware. We fixed a number of bugs relating to movement commands sent over CAN to expansion boards in firmware version 3.3, and one more in 3.4. My advice is that you apply your customisations to firmware 3.4 or 3.4.1.

fcwilt

@dc42 said in Duet3 Expansion Board 3hc blocks during downgrade:

I made a series of changes to the startup code to fix this, the final one being in April 2021. But firmware 3.3.1 was released in May 2020 so it doesn't include these changes. I think it's likely that this explains why firmware 3.3.1 won't start up on that board. It's possible that if you leave the board powered up for an hour or two, it may eventually start up.

Did you mean 3.1.1 rather than 3.3.1?

Frederick

dc42

@fcwilt thanks, I did - now corrected.

DanielPetrea

@dc42 Hi dc42,
That's not the first duet3hc expansion board that i'm using, i've uploaded the firmware very well in many boards.
With the last version of board( V1.01) is not possible to upload this firmware.
Did you think that is a problem of this single board or the new version of board?
Thanks

dc42

@danielpetrea now that you come to mention it, I can see another problem. Early 3HC boards used 12MHz crystals, but later versions use 25MHz instead. The later bootloader and RRF versions detect the crystal frequency automatically. Firmware 3.1.1 is probably too old to include the frequency detection code.