• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 67 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CDCEL913 EEPROM Write Endurance

CDCEL913: EEPROM Write Endurance

Sean Heffernan1
Intellectual 260 points
Part Number: CDCEL913
Other Parts Discussed in Thread: CDCEL9XXPROGEVM

I saw in the datasheet (and in a previous Forum thread) that the "safe" number of EEPROM write cycles that may be performed is 1000; the same Forum thread mentioned that you can perform unlimited write cycles to the register RAM memory.

We are writing a software driver that will automatically write to the CDCEL913 registers every time our system powers up or resets. It is my understanding that if we set the EEPROM WRITE bit (Bit 0 of Byte 7) to "1" in our driver, then the register data will be written to the nonvolatile EEPROM memory every time the system resets; this process seems needlessly repetitive (since the EEPROM memory is nonvolatile), and we will exceed the 1000 "safe" write cycles fairly rapidly. But if we leave the EEPROM WRITE bit cleared "0"), then the driver will only write to the registers; we will basically be reconfiguring the CDCEL913 every time we power up our system, but since there is no limit to the number of register RAM writes that may be performed, this shouldn't be a problem.

Am I understanding this correctly?

Sean Heffernan

  • 0
    TI__Intellectual 2000 points

    Sean,

    Is there a reason you want to rewrite to the device every powerup? Writing to the CDCEL913's EEPROM once can allow for your custom configuration to be loaded to the device upon startup, eliminating the need for a constant rewrite to the registers.

    To answer your question, however, yes leaving EEWRITE as a 0 will only write to the registers, not the EEPROM, and should not be an issue.

    Best,

    Cris

  • 0
    Intellectual 260 points

    Hi Cris,

    I'm the hardware engineer on this project and will not be writing the actual configuration driver for programming the device, so I'm not exactly sure how the software team is going to implement the driver. I have a feeling they are just going to want to add this configuration to the rest of their "boot code", which means that it will run every time the system is powered up; if that is the case, I don't want to exceed the number of "safe" EEPROM write cycles by writing the EEPROM every time. If they would prefer to configure the device only once (during system assembly, for example), then I agree, it would be better to write to the EEPROM and be done with it. In the past, we have programmed our devices with the CDCEL9XXPROGEVM module prior to prototype board installation.