Some of the upper bits of the fuse bytes are not actually used, so it does not really matter what is set for those. However, avrdude reads back all bits after setting them and compares them to what they were supposed to be set as. If it does not agree an error message is created.
Apparently at one stage the way avrdude reads back the not used bits was changed. So, if I remember this correctly, for older versions the lock byte has to be written as FF, but for newer versions of avrdude it has to be 3F, to prevent the error message. The actual setting is the same.
Cost me a lot of time….
Peter
> On 21 Sep 2017, at 23:28, Aymeric <ult...@bl...> wrote:
>
> Aymeric said :
>> Mikael Nordman said :
>>> How did you set the fuses ? That is the first thing to check.
>>> The fuses must be set to BOOTSIZE=1024 words and the BOOTRESET should be
>>> active.
>>>
>>> [..]
>>>
>>> I think these fuses should work for the 168.
>>>
>>> avrdude -p m168 -c usbtiny -e -u -U flash:w:ff-atmega.hex:i -U
>>> efuse:w:0xf8:m -U hfuse:w:0xff:m -U lfuse:w:0xff:m
>>
>> I cannot set SPIEN to 0 on this board, so I used this:
>>
>> -U lfuse:w:0xFF:m -U hfuse:w:0xDF:m -U efuse:w:0xF8:m
>>
>> Unfortunately I still do not get anything when I try to connect with
>> screen.
>
> I gave it another try and this time I could set the hfuse to FF, I don't
> understand why it did not work last time (it was on another machine,
> with another version of avrdude though...). However I still end up with
> a blank screen.
>
> Is there anything else I could try? Or should I just get an Arduino that
> is already supported/tested?
>
> Thanks!
> Aymeric
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Flashforth-devel mailing list
> Fla...@li...
> https://lists.sourceforge.net/lists/listinfo/flashforth-devel
|
