As Dawid Buchwald wrote:
> There is, however, one more thing that mcudude mentioned - at the
> end of programming AVRDUDE would list values of lfuse/hfuse/efuse in
> its goodbye message. It is pretty irrelevant to the modern chips,
> since they don’t really have any of these, they just have array
Thanks for the detailed explanation. This use case (lousy parallel port
connection) makes sense, and indeed, this is not applicable to the SerialUPDI
implementation.
In fact, with how the NVM model works it’s actually impossible to change fuses
by accident (like writing to flash at incorrect
On Wed, Dec 15, 2021 at 7:18 AM Joerg Wunsch wrote:
>
> As Dawid Buchwald wrote:
>
> > After some more investigation I concluded that there are actually
> > different scenarios where Safemode is disabled, so I would really
> > leave that for now.
>
> Just as a side-note, and since there is also
As Dawid Buchwald wrote:
> After some more investigation I concluded that there are actually
> different scenarios where Safemode is disabled, so I would really
> leave that for now.
Just as a side-note, and since there is also one large patch
regarding safemode which I decided to not apply
Follow-up Comment #24, bug #61624 (project avrdude):
Let me start with reply, followed by status update.
> Makes me wonder why they didn't just come up with one mode to rule them all,
instead of three.
I suppose this is because they are in process of finalising the design? I have
no idea, but I
