Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
03/07/08 21:27
Read: times


 
#152018 - Try reading the Atmel app notes.
Responding to: ???'s previous message
Eric,

The OP said that he was using an eeprom. He did not say whether he was on a multi-master bus.

I do not know whether there are other masters, and if I had to wait for a full life-history from the OP it would not be possible to know.

Assuming that he is using the eeprom in a single master environment, he is going to read the eeprom on demand and write back when he chooses. If he receives a power failure during a write, then at least he knows what he was doing at the time.

Perhaps you can suggest a scenario where this is unsafe, compared to setting up an IRQ buffer and state machine. There is an equal risk of power failure, and subsequent recovery.

In practice you are always going to do other things while a read/write takes place. You will be polling for an IRQ state to have completed or polling for each individual TWI operation to complete. Sometimes it is worth keeping code simple.

Have you read the Atmel example code ?

David.

List of 12 messages in thread
TopicAuthorDate
Problem using TWI of AT89C5131AM            01/01/70 00:00      
   TWI            01/01/70 00:00      
      I2C is a Philips/NXP Trademark            01/01/70 00:00      
      Problem using TWI of AT89C5131AM            01/01/70 00:00      
         There's an echo in here            01/01/70 00:00      
         Register addressing of i2c devices            01/01/70 00:00      
   TWI and AT89C5131            01/01/70 00:00      
      how do you know??            01/01/70 00:00      
         Try reading the Atmel app notes.            01/01/70 00:00      
            Problem using TWI of AT89C5131AM            01/01/70 00:00      
               There's an echo in here            01/01/70 00:00      
   just had a look            01/01/70 00:00      

Back to Subject List