Fly-RRF-36 RP2040 Based CAN-FD Toolboard

fractalengineer

@jay_s_uk any thoughts on this?

jay_s_uk

@fractalengineer maybe try without the stealthchop parameters

fractalengineer

@jay_s_uk Well I'd be damned; didn't think of removing them but these were indeed tied to my TMC5160 tuning

Also somehow missed that I had M569 set to D3...

Set it back to D2, disabled M915 and it seems to be running like a champ now, thank you very much!

Let's push some plastic now

jay_s_uk

@KenW ah yes, the update thing should be fixed in RC2.
To get round it at the moment, create/upload a file called Duet3Firmware_Fly36RRF.bin in the firmware folder
It doesn't matter what the file is or what it contains. This will trick RRF into updating the toolboard

gloomyandy

@jay_s_uk Just to clarify, you will also need to use this trick to install RC2 (when it is available) as there are changes in both the main RRF and in the toolboard code. Once everything is on RC2+ then you should not need the trick again.

jay_s_uk

@KenW yes, the 101 to 102 change only affect mainboard firmware

fractalengineer

Just a heads up, the fw file names appear to be case sensitive, but the https://github.com/gloomyandy/RepRapFirmware/releases repo produces wrong case (Duet3Firmware_FLY36RRF where M997 expects Fly)

This is also erroneous on the docs: https://teamgloomy.github.io/fly_rrf_36_general.html

I've figured simply correcting the case on both .bin and .uf2 made the flash successful

Perhaps have GitHub produce case correct filename and reflect it in the docs for further reference?

Apart from that still happy with the board, thank you!

jay_s_uk

@fractalengineer thanks, I'll update it once I'm home

A Former User

@fractalengineer Posted this problem back when I was not able to update the firmware and was told to create a bin file. I had to correct the case to Fly on the .uf2 to match the .bin like you did. But for some reason all my postings on the board vanished. Never found out why that happened. Asked if I had done something wrong and was told no so?

Not had them vanish since.

gloomyandy

@KenW @fractalengineer That's interesting. I fixed the names in the latest rc2 version (the filenames are now uppercase). But I've never actually seen this issue when updating. Are you by any chance running an SBC configuration?

fractalengineer

@gloomyandy This was my first time updating from the Duet; RC1 was a fresh flash from USB, but yep I'm on Duet3 MB6HC + SBC