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

OK, Got it. I figured it was a "I'm on a Mac" thing. Instead of just downloading the file, I right-click on the download link and did a "save As". It downloaded it with a longer name and that zip file worked fine.

@oliof I think in my case it was an interaction with the way my home automation system controls the lights using UPB.

http://www.simply-automated.com/UPB_Technology.php

Thank you for all communications.
The printer is well on its way to return to an active role in creative projects.

@jay_s_uk
Worked great! Thanks for the suggestion.

@droftarts Thank you! FAN0 and FAN2 don't work. I ordered a few MOSFETS. The newer ones, that are installed at the Duet3 mainboard. I hope i have them tomorrow, otherwise it will be de day after tomorrow. I'll post the results here. 🤞

@chrishamm said in Problem on new installation / upgrade:

Bookworm

Thnaks you all. I think this post can be considered as SOLVED.

As a recap:
at least for me, the 64 bits version is really not running with enough resources on a a raspi 3 B+, too slow, I got many weird erros on daemoin.g file, camera issues, etc.

The 32 bit version is now running as suposed to.

LCD touch screen in my case needs extra config to run on bookworm, I found the solucion here: https://www.waveshare.com/wiki/Main_Page#RPi-Displays (llok for your model)

Looks and sounds like the same issue I have.
https://forum.duet3d.com/topic/36643/randomly-reconnect-of-dwc-on-duet2-ethernet?_=1727016238232 isn't it? Started with 3.5.2 and also present with 3.5.3.

@Phaedrux Sorry, for my late reply! I was very busy the past 2 days. I found a old config file. I'm using the same settings. Now i have another problem with the Fans. But i will post a new question for this.

@chrishamm Yes, the values are back! Thank you very much!
What's the reason why tools[0].retraction.extraStart has a new naming?
In RRF3.4.1 it was named tools[0].retraction.extraRestart...

@Phaedrux That was it. Thank you for your help.

@chrishamm Thanks! That worked than it didn't The new error is:

W: Sources disagree on hashes for supposedly identical version '1.1.0' of 'duetsd:arm64'.

Seeing as its actively being updated today, i'll wait 🙂

What did you download to get your firmware file?
What firmware are you currently running? Send M115 to check.
You may also require IAP files from the firmware bundle to correctly flash the firmware with the M997 command. The better way to flash is to upload the complete firmware zip file via DWC if you have access.

@Orbital I suggest you read the upgrade notes for RRF 3.5.2 and whatever versions you skipped. From the symptoms you describe I suspect you have a M667 command in config.g that needs to be replaced by a suitable M669 command.

@chrishamm new image with no updates works. M997 S2 F"unstable", M997 S2