Synth-DIY Yahoo! Groups Archives

RE: [AVR-Chat] prevent attiny2313 flash corruption

2009-11-04 by Tim Mitchell

----Original Message----

Show quoted textHide quoted text

From: AVR-Chat@yahoogroups.com
[mailto:AVR-Chat@yahoogroups.com] On Behalf Of David
VanHorn Sent: 04 November 2009 13:59 To:
AVR-Chat@yahoogroups.com Subject: Re: [AVR-Chat] prevent
attiny2313 flash corruption 

> You need to make sure that the write will complete before
> power goes 
> out of spec.
> You also need to make sure that the address you're
> writing to is 
> correct, and that the data is correct.
> 
> Generally, when not actively using the EE, I leave the
> EEAR pointing 
> at 0x00, so that a wild write for whatever reason, should
> overwrite 
> this address, which I dont use.
> 
> When I set up a program to specifically investigate this
> in the 8515, 
> I never caught a single instance of EE corruption, when
> the code 
> followed the rules above.



Sorry, are we talking about Flash (ie program memory) or Eeprom
corruption here?

I have experienced Eeprom corruption caused by dodgy power. Never seen
or heard of flash corruption.

-- 
Tim Mitchell

Re: [AVR-Chat] prevent attiny2313 flash corruption

2009-11-04 by David VanHorn

Sorry!   Insuficient caffiene errror.
I was thinking EE, but still most of the same issues apply.
Writing while the power is failing is a bad idea, as is writing while
the power is coming up.
Sometimes, a power supply can have a glitch in its rise, such that the
power goes invalid again, before it rises all the way.

Show quoted textHide quoted text

On Wed, Nov 4, 2009 at 9:43 AM, Tim Mitchell <tim@sabretechnology.co.uk> wrote:
> ----Original Message----
> From: AVR-Chat@yahoogroups.com
> [mailto:AVR-Chat@yahoogroups.com] On Behalf Of David
> VanHorn Sent: 04 November 2009 13:59 To:
> AVR-Chat@yahoogroups.com Subject: Re: [AVR-Chat] prevent
> attiny2313 flash corruption
>
>> You need to make sure that the write will complete before
>> power goes
>> out of spec.
>> You also need to make sure that the address you're
>> writing to is
>> correct, and that the data is correct.
>>
>> Generally, when not actively using the EE, I leave the
>> EEAR pointing
>> at 0x00, so that a wild write for whatever reason, should
>> overwrite
>> this address, which I dont use.
>>
>> When I set up a program to specifically investigate this
>> in the 8515,
>> I never caught a single instance of EE corruption, when
>> the code
>> followed the rules above.
>
>
>
> Sorry, are we talking about Flash (ie program memory) or Eeprom
> corruption here?
>
> I have experienced Eeprom corruption caused by dodgy power. Never seen
> or heard of flash corruption.
>
> --
> Tim Mitchell
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>