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.
Dear Hugh -
Please follow this link to request NIST document for the TMP117:
(this is found on the product page in between Product Details and Technical Docs sections)
https://www.ti.com/product/TMP117#product-details
Regarding the EEPROM, EEPROM 1 is used for NIST, EEPROM 2 and 3 are open for your use. This is discussed in the datasheet https://www.ti.com/lit/ds/symlink/tmp117.pdf starting on page 29.
Hi Josh,
So does it mean that the unique identifier is 16 bits large?
Several inconsistencies in the datasheet:
7.6.1.7 EEPROM2 Register (address = 06h) [reset = 0000h]
Reset value doesn't appear to be 0000h but 6F79h on the sample I have here.
In Table 3, the reset value suggests that the reset value is xxxxh.
EEPROM[4:1] are preprogrammed during manufacturing with the unique ID that can be
overwritten. To support NIST traceability do not delete or reprogram the EEPROM[1] register.
This suggests that only EEPROM[1] is used for NIST traceability, as you mentioned, but also suggests that all of the EEPROM is used with a unique ID, which seems to makes sense given the reset values specified. Not sure what EEPROM[4] is referring to in this component?
Hi Josh, as well as Ben's queries, the link to request NIST data doesn't work for me..
Hugh -
It worked for me, sorry it did not for you - perhaps try going to the product page and using the link there (should be same), click it and this should take you to login.ti.com page.
Hi Josh
I did try that before, and have again - same result - encountering resistance! I'm using Chrome, if that has anything to do with it...
Any answer to Ben's questions above? He is developing firmware with the part, I'm looking at our longer term plans.
All the best
Hugh
Hugh/Ben -
I saw Ben was able to request access and access has been granted - you will get email with a link from the system soon.
I have assigned this post to Applications Engineer on the team, as I see what I think you mean about the ambiguity on the description of the registers - they will respond back on this within 24 hours.
Hi Ben,
All of the EEPROM locations in TMP117 are being used for NIST traceability. Some of the mistakes are due to the changes from TMP116 to TMP117. The TMP116 does not have the offset functionality, and that memory location can be used by the customer without losing NIST data. In the TMP116, the 3 NIST registers and the offset register are collectively EEPROM 1 through 4.
thanks,
ren