Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

RE: [AVR-Chat] ATTiny24a EEPROM troubles

2017-03-20 by BryanW

I’m not sure about the tiny24, but is there an EESAVE fuse, as this will protect the EEPROM data when a bulk erase is issued. Otherwise the only way to preserve the EEPROM is by reading it first and then re-writing it.

Sent from Mail for Windows 10

From: Richard Purcella repurcella@gmail.com [AVR-Chat]
Sent: 20 March 2017 15:16
To: AVR-Chat@yahoogroups.com
Subject: Re: [AVR-Chat] ATTiny24a EEPROM troubles

  
There is a bulk erase in the avr studio programming ide. It often runs  every programming cycle.

On Mar 19, 2017 11:48 PM, "richros@adamswells.com [AVR-Chat]" <AVR-Chat@yahoogroups.com> wrote:
  
I'm an old-timer in micro's, started back in the mid-70's and have experience in
just about every one made up through 2002.  (Started with Intel's 4004 & 8008.)
Didn't get to do much with the Atmel devices then but made up for it since
retiring.

I've used most of the ATTiny and some of the ATMega devices and have used
the EEPROM in several.  This is the first time I used it on the ATTiny24 and
I've put in nearly a 40 hour week trying to tame it!

I've used the programming examples right out of the spec sheet and several
variations of it but no cigars!  I'm pretty sure that the Write works, I can
program several bytes and then read the micro's EEProm with the AVR
Studio 4's HEX file read capability.  I can shut down everything and it's
still there after a complete power-up.  The problem is that everytime I
do an EEPROM_Read it erases everything.  I don't see anything in the
specs about a bulk erase!  

Is there a problem with the ATTiny24A?  The same sequence works with all
the other devices.

Oh, by the way, I'm an assembly language programmer and can run circles
around any of the C programming kids.

Any help would be greatly appreciated.

Rich




[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.