On Tue, 2009-01-06 at 13:40 -0600, David Kelly wrote:
Notice the starting address of eeprom is 1 byte above the physical
address of start of eeprom because there was some rumor stating some
models of AVR would accidentally trash the first byte under some
circumstances. Perhaps when the rest
Older AVRs had the problem, if a the voltage dropped under the limit
during a eeprom write, adr 0 was corrupted as well as the one written.
But current AVRs -- at least with the brown out detector enabled -- does
not show this bug anymore...
If you look at the EEPROM Address Register in the
-Original Message-
From:
avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Bob Paddock
Sent: Friday, January 09, 2009 6:50 AM
To: avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list]
On Mon, 5 Jan 2009 23:26:13 +0100
Sascha Silbe sascha-ml-uc-avr-...@silbe.org wrote:
Sounds like you copied something from an obfuscating mailing list web
archive into your Makefile, probably with improperly wrapped lines.
Inspect your Makefile closely.
I copied my Makefile below, if someone
thanks Sascha and Preston, you got it right indeed, it was this very
list's archive web front end that replaced the actual option with this
addr...@hidden stuff ! Grrr.
David Kelly wrote:
Vincent, as the original author of your Makefile
Thanks for hearing my call, David ! ;-)
(didn't ge
From: dke...@hiwaay.net[...] Notice the starting address of eeprom is 1 byte
above the physical address of start of eeprom because there was some rumor
stating some models of AVR would accidentally trash the first byte under some
circumstances. Perhaps when the rest of the device was wiped
Hi list (and happy new year to everyone)
The last time I workd on my AVr project it was gcc version 3.x
something, a while ago then. I resuming work on that project now, with
a more current version of gcc (4.3.0), and I notice something new :
Everytime I run make to compile the project, a weird
