We are having I2C communication issues with our latest board build, specifically with the TPS65950 I2C port where our test software comes back with an incorrect (or different) IDCODE. On our older digital boards, the IDCODE was 0x1009002F, but on the newer TPS65950 devices, the IDCODE is reading “0x3009002F”.
From your TPS65950 Technical Reference Manual, there is a note on the device IDCODE –
“NOTE: IDCODE field cannot be read correctly using the I2C interface. The IDCODE read back using I2C will have the value 0x1009 002F”
So for our acceptance test procedure, we were expecting and reading 0x1009002F but now it is reading back “0x3009002F”. This is occurring on all the newer TPS65950 parts (4 parts) so far.
We are also experiencing I2C errors while reading back the USB status registers within the TPS65950.
I’ve compared the package code for the older and newer parts and are the numbers:
GOOD (older) TPS65950
TPS65950B
05AZGYW C
G1
BAD (newer) TPS65950
TPS65950A2
18AK44W $4
G1
Is it possible we have a different silicon rev part that now gives a different IDCODE? I can’t tell from the nomenclature description in your Data Manual what rev we have, and what the IDCODE should be reading. Can you help me figure this out?
Thank you for your assistance.
