Hello, Sorry I've been moving, so missed this thread! I did have some code to make a unified ELF file some time ago, it used the many-different-name scheme. See http://savannah.nongnu.org/task/?5093
At any rate - the reason I never got around to doing offsets is I wasn't sure of the answer to this question: Say you have an offset that looks like: 0x820000 LFUSE 0x820001 HFUSE 0x820002 EFUSE (note: I just hit '0' a bunch of times after 82, that might not be the right number) What happens in the hex file if you just specify an LFUSE and EFUSE. Does the hex file generate two lines, each with just one byte in it? Or does it generate a continous line where LFUSE and EFUSE are what you specified, and HFUSE is the default? The reason being we need a way to figure out if a fuse value was specified. If the user forgets to specify a certain fuse, I don't think it should set it to any default. Even if the default was set up to make sense (aka state chip is shipped in). Instead if no value is specified, it shouldn't mess with the fuses. Warm Regards, -Colin O'Flynn On Friday 31 August 2007 08:11, Joerg Wunsch wrote: > Eric Weddington <[EMAIL PROTECTED]> wrote: > > I just wanted to let you know that I saw your post on avr-libc-dev > > (and I'm sure Joerg did too). > > I won't have any time to spend on it until around mid next week. _______________________________________________ AVR-libc-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
