M997: Firmware binary is not valid for this electronics [SOLVED]

SamanthaJaneyCake

Morning!
I've been struggling to update my Duet 2 WiFi from RRF 3.3 to 3.5.
I did a fresh SD using the RRF Config website but despite having selected 3.5 it defaulted to 3.1.1.
So I managed to manually get it up to 3.3 with the aim of getting to 3.5 in the next step.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03

DWC V3.5.1

No firmware files in 0:/sys
0:/firmware contains the following:

Duet2and3firmware (directory, V3.5.2)
__MACOSX
DuetWiFiServer.bin
Duet2CombinedIAP.bin
Duet2CombinedFirmware.bin
Duet2_sdiap32_WiFiEth.bin

When I run M997 S0 I get this error:

M997: Firmware binary "0:/firmware/Duet2CombinedFirmware.bin" is not valid for this electronics

Any ideas on what I can do to fix this? Thanks for all the help!

dc42

@SamanthaJaneyCake try uploading Duet2CombinedFirmware.bin again.

SamanthaJaneyCake

@dc42 thanks for the suggestion! I just tried that with a fresh download of Duet2CombinedFirmware.bin version 3.5.2 and uploaded to 0:/firmware.
It uploads and asks if I want to install the file, which I agree to. After reconnecting I queried with M115 and got this back:

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03

I then tried M997 and M997 S0 both times returning the same thing. I've deleted out the Duet2and3firmware directory and retried.

Interestingly it hasn't complained about the file not being valid, but hasn't actually updated by the look of things.

LogFile:

28/07/2024, 20:43:34	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
28/07/2024, 20:43:10	Upload of Duet2CombinedFirmware.bin successful after 2s
28/07/2024, 20:42:54	Successfully deleted Duet2and3Firmware
28/07/2024, 20:42:49	Successfully deleted 17 items
28/07/2024, 20:42:25	Successfully deleted Duet2CombinedFirmware.bin
28/07/2024, 20:41:51	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
28/07/2024, 20:41:38	M997 S0M115
28/07/2024, 20:41:22	M997 S0
28/07/2024, 20:41:05	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
28/07/2024, 20:40:43	Upload of Duet2CombinedFirmware.bin successful after 1s
28/07/2024, 20:39:03	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
28/07/2024, 20:38:55	Connection established
28/07/2024, 20:38:44	M997
28/07/2024, 20:38:25	M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
28/07/2024, 20:37:50	Upload of Duet2CombinedFirmware.bin successful after 2s
28/07/2024, 20:37:06	Successfully deleted Duet2CombinedFirmware.bin

dc42

@SamanthaJaneyCake I suggest you download the 3.3 version of the IAP file for Duet 2 here https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2_SDiap32_WiFiEth.bin, copy it into /firmware on your SD card, and run M997 again.

Do you have a PanelDue connected to the board? If so, and the baud rate is set to 57600 then then you can watch the progress of the firmware update on it.

SamanthaJaneyCake

@dc42 Good afternoon and thanks!
I deleted out the current IAP and uploaded the one linked (thanks). M997 took longer to execute this time and upon running M115 I am happy to report she's now on RRF 3.5.2!

EDIT: I am however getting the following error:

Error in macro line 47 while starting up: exactly one of EFHJPSR must be given

I can't seem to find reference to this anywhere.

dc42

@SamanthaJaneyCake what command do you have on line 47 of config.g ?

SamanthaJaneyCake

@dc42 Sorry, got there myself with some playing around when it got more verbose and pointed me towards config.g and now sorting my config properly. That's irrelevant to this topic so I'll mark it as solved ◡̈

o_lampe

@SamanthaJaneyCake Now I wonder, if this FW update issue was also the cause for your "M3 command not working" problem with your spindle?

SamanthaJaneyCake

@o_lampe it wasn’t, as it happens. I redid the firmware from scratch using the RRF configuration tool which gave a slightly different setup to the one I was working on when I asked the spindle question.
Ironically having fixed the issues I’m back to essentially my original spindle config.
What I’ve ended up doing to solve that original issue is break out heater3 (and 4 for the laser) and use those to PWM drive an external MOS chip that level shifts the PWM to a breakout from the fan 5V… which is then the right level and “side” of the spindle controller to control it properly!

It seemed to work when I tried it at 9:00 last night but that’s my cutoff time for trusting my brain not to do something stupid so I’ll be doing more tests and checks this afternoon.