@SputnikOC3d I've updated the M997 Gcode entry with more examples, and made the notes a bit clearer: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

@SputnikOC3d said in 1LC Toolboard FW mismatch - M997 fails to update D3 Mini+SBC pi4:

I must be super daft ... cuz I really never saw this as a 2 step process in the docs.

It isn't a two stage process, because you rarely, if ever, need to update the bootloader. So all you needed was M997 B121 to update the firmware. And usually this is done automatically for you.

Ian

@droftarts Dear Ian, your efforts are highly appreciated. However, I consider now to use my 6HC in SBC mode, since I bought a new raspberry. Then firmware updates hopefully become less of a problem since Bossa worked like a charm on your raspi OS.

@droftarts - this issue is resolved - and now im into a new issue.

Ive abandoned the filezilla bu and just used the filed from the DWC backups.

Closing ... moved on

Closing this thread as Ive determined with guidance from those in the know, my path forward needs to be not merely just an update and upgrade to RRF, but to the debian install as well. Bookworm on SD Card fresh.

@droftarts Thank you for your reaction.

@waynehuish Please post your config.g and the repsonse to M122.

Do you mean you have recently updated the firmware on your controller board? What version were you running before, what are you running now? Which Duet board? Is your machine something like an Ooznest Workbee?

If it's to do with the firmware and the V-carve software Ooznest provide, you would be better off contacting their support.

Ian

@roshiposhi said in klipper & fluidd on Duet 3 mini 5+:

Hey guys,

I am a 3d printer newbie who got hands on a vcore 3.0 running RRF 2 on a duet3 mini 5+.
The machine hasn't been in use for a long time so thought of bringing it to life. I want to add klipper to it to replace RRF.

Duet 3 Mini never ran RRF 2 so you probably run an older version of RRF3.

I know it's not what you ask about, but the unofficial RatRig Discord has an rrf channel with a number of sample RRF configs for ratrig machines. Maybe that's an option as well ....

@MartinMV I assume one of the above posts from forum admins/mods got you going again? It would be good if you could respond with what resolved the issue for you, so that other users that have the same issue can find this thread, and don't get stuck down the same rabbit hole that you did.

Did you manage to complete the firmware update to the latest version successfully?

Ian

@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.

@droftarts

great thanks.

my printer is not there, but at least some effort to provide something for a few printers.

@Jords27 said in Uploading bootloader and firmware using Atmel Studio:

@dc42 Thank you again for your help. It took a while but we figured out that the external oscillator was not producing the correct frequency. After replacing the oscillator with another model everything was working as expected!

That's something I didn't think of! All Duet 3 expansion boards use a 25MHz crystal, so that is what the bootloader and firmware startup code assume.

@Phaedrux Thx 🙂 i was too dumb to see that i have to change the motor directions and edit the homing files so that it goes in the right direction.
Now this issue is solved, thanks a lot

@chrishamm yes, it is. great. thank you... now everything is fine

@chrishamm I bumped it up to what I believe is the max, 115200, and it's still inconsistent.