• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 588 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TUSB3210 Corrupt EEPROM

Robert Parr
Prodigy 150 points

Hi,

We have a design for a keyboard based on TUSB3210 keyboard dev kit and generally it works fine.

However we are having a small number of failures in the field where the keyboard stops working altogether when we read back the data from the EEPROM the first byte has been erased (set to FF).

Does anyone have any suggestions as to what would cause this? I thought the TUSB3210 was just reading from the EEPROM when it starts up and so it shouldn't perform an erase or a write unless connected to the PC software to program it?

Our circuit is a copy of the dev kit schematic.

Regards,

Rob Parr

  • 0
    TI__Genius 11255 points
    Hello Robert,

    You are correct, the TUSB3210 default behavior is just read the EEPROM information at the startup.

    What software are you using to write on the EEPROM? Is that software (or other software used to Write on EEPROM) installed on the failing systems?

    The EEPROM data is suddenly changed after some time or it never works?

    Regards,
    Roberto
  • 0 in reply to Roberto Diaz
    Prodigy 150 points

    Hi Roberto,

    The EEPROMs are programmed at production using an Aardvark I2C EEPROM programmer.

    There is no software running in the system which writes to the EEPROM, it works exactly as the TUSB3210 keyboard dev kit with some remapping of keys and changes to the codes.

    The keyboard works as expected through production testing and then again works fine in the field and then some of the units are failing after what at the moment appears to be a random period of time.

    When I got a failed unit and read back the EEPROM data the first byte was erased or was set to 0xFF.

    Regards,

    Robert