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.

PGA305: EEPROM usage for cells not described in datasheet

Part Number: PGA305

Hello,

I have a similar question to the one asked here https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/748112/pga305-pga305-eeprom/2785850?tisearch=e2e-sitesearch&keymatch=PGA305%25252525252525252520eeprom#2785850, but it did not get an answer to the part of the question that I am interested in.

In the EEPROM register map there are gaps. For example from 0x4000006A to 0x4000007E the EEPROM contents or usage is not defined. Do these cells need to be maintained with their power-on defaults or are they free for use by the user?

Thank you.

  • Hi David,

    In the EEPROM register map there are gaps. For example from 0x4000006A to 0x4000007E the EEPROM contents or usage is not defined. Do these cells need to be maintained with their power-on defaults or are they free for use by the user?

    The gaps in the register map do not to be maintained and can be overridden. I believe 0x4000005A and 0x4000005B are other examples. 

    In the case of TEMP_CTRL and other almost blank registers:

    However, this is not for registers that are specifically called out in the datasheet (which is what the linked post is talking about). Most of these cases are where a specific register space has a name but most of the bit numerations are not defined. For example, DAC_CONFIG, TEMP_CTRL, and the reserved spaces of DIG_IF_CTRL. They do have defaults and should maintained. Granted, you'll find that most of those are 0b. However, they are not defined for a reason and datasheet should be followed.

    Hopefully this answers your question.

    Best,

    -Cole

  • Hello Cole,

    Thank you for your quick and complete answer.

    Kind regards,

    David.