[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-gcc-list] Re: AVR-GCC-list Digest, Vol 15, Issue 18- Device fuses

From: Björn Haase
Subject: [avr-gcc-list] Re: AVR-GCC-list Digest, Vol 15, Issue 18- Device fuses
Date: Sat, 22 Apr 2006 08:18:05 +0200
User-agent: KMail/1.7.1

address@hidden wrote on Samstag, 22. April 2006 18:07 :
> Send AVR-GCC-list mailing list submissions to
>       address@hidden
> Message: 1
> Date: Sat, 22 Apr 2006 13:12:59 +0200
> From: "Anton Erasmus" <address@hidden>
> Subject: [avr-gcc-list] Suggestions for avr-gcc (Device fuses)
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=US-ASCII
> Hi,
> Wouldn't it be worthwhile to add a method of specifying device fuses
> in the C or assembler source file ?
> I think something similar to the way the EEPROM and PROGRAM memory is
> handled.
> something like:

That would not be difficult at all. One could agree on the name of some 
section that contains data for the fuses and the lock-bits. One would do 
something like:

#define SET_FUSE_BITS(F1,F2,F3,L) unsigned char fuses[4] __attribute___ 
((section (".fuses"))) = {F1,F2,F3,L};

The more time-consuming thing would be to teach your favorite programming tool 
to actually use the data in the .elf file.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]