Re: [avr-libc-dev] Problem with eeprom_write_byte

[Matthias Fechner]

Hi Jörg,

Am 07.06.10 21:42, schrieb Joerg Wunsch:
> The library functions are not meant to be used in an interrupt-
> controlled access scheme.  Users who want interrupt controlled EEPROM
> writes are expected to create their own library.
>
> That doesn't mean it couldn't be useful to add some inline asm macro
> to the header file that implements just the low-level access (where
> you have to pass in the IO address from outside, so it's device
> independent).
>
>    

hm ok, but if the function would not touch the EERIE bit you could use 
it without problems in an interrupt content.
Or is it a site-effect that this bit it reseted to 0?
Sorry if I ask such a stupid question, but maybe I get an easy answer 
here before I have to look into the source code of the AVR LibC to see why.

Bye,
Matthias

--
"Programming today is a race between software engineers striving to build bigger and 
better idiot-proof programs, and the universe trying to produce bigger and better idiots. 
So far, the universe is winning." -- Rich Cook