[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avr-libc-dev] Re: [RFC] Unified ELF file
From: |
Colin O'Flynn |
Subject: |
[avr-libc-dev] Re: [RFC] Unified ELF file |
Date: |
Sun, 23 Sep 2007 02:30:30 -0300 |
User-agent: |
KMail/1.8.2 |
Hello,
> - How can the API be changed to ensure that all fuse bytes are set by the
> user?
Not fixing that problem, but what about providing some indication that not all
fuse bytes were set?
By this I mean providing a "magic sequence" at the end of the fuse bytes. So
the ELF file in the .fuse section looks like:
LFUSE HFUSE EFUSE 0xAA 0x00 0x00 0x00
Then avrdude can check that the 0xAA is in the correct spot (just made up
numbers, can select better magic values). If the AVR being programmed has all
three fuses, but in the forth location 0x00 is read instead of 0xAA, the
layout is messed up. The 0x00's are part of the sequence to ensure that when
bytes are left out the magic number will be guaranteed wrong.
Regards,
-Colin
- [avr-libc-dev] RE: [RFC] Unified ELF file, Eric Weddington, 2007/09/22
- [avr-libc-dev] Re: [RFC] Unified ELF file,
Colin O'Flynn <=
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Eric Weddington, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/24
- RE: [avr-libc-dev] Re: [RFC] Unified ELF file, Colin O'Flynn, 2007/09/26
- Re: [avr-libc-dev] Re: [RFC] Unified ELF file, Dave Hylands, 2007/09/26
- Re: [avr-libc-dev] Re: [RFC] Unified ELF file, Michael Hennebry, 2007/09/26