TMP102: cannot access address 4A

Shinichi Inoue

Guru 19701 points

Part Number: TMP102

Dear Specialists,

My customer is evaluating TMP102 and encountered the problem.

I would be grateful if you could advise.

---

I have confirmed the operation by mounting TMP102 on the board, but ACK is not output even if I access address 4A.

ACK is obtained for addresses 48 and 49.

An ACK is obtained by accessing the unused address 4B.

It seems 4A and 4B are swapped.

The device marking is CBZ.

Bad operation occurred in 2 out of 2 samples.

I purchased SEN-13314 SparkFun Electronics | DigiKey from DigiKey and checked the phenomenon, but ACK was obtained correctly.

SEN-13314 SparkFun Electronics | DigiKey

What's wrong with it?

Could you please confirm the file below and advise.

TMP102_slave address confirmation .xlsx

---

I appreciate your great help in advance.

Best regards,

Shinichi

over 2 years ago

0 Josh Wyatt over 2 years ago

TI__Guru* 91086 points

Dear Shinichi -

Here I did not see in your excel sheet that you connected SCL on the Sparkfun board, with the TMP102 mounted, to ADD0.

Here is the schematic for that board, from the link you originally provided: http://cdn.sparkfun.com/datasheets/Sensors/Temp/SparkFun_Digital_Temperature_Sensor_Breakout_-_TMP102.pdf

perhaps triple check the connections.

0 Shinichi Inoue over 2 years ago in reply to Josh Wyatt

Guru 19701 points

Hi Josh,

Thank you for your reply.

I confirm the customer and could obtain the data.

Could you please see attached file below.

TMP102 Sparkfun board connection_20210616.xlsx

I appreciate your great help and cooperation.

Best regards,

Shinichi

+1 Brandon Fisher94 over 2 years ago in reply to Shinichi Inoue

TI__Mastermind 27645 points

Hi Shinichi,

Looking at this transaction, the t_(HDDAT) looks like it could be marginal. Can they please measure their hold time?

Best Regards,
Brandon Fisher

0 Shinichi Inoue over 2 years ago in reply to Brandon Fisher94

Guru 19701 points

Hi Brandon,

Thank you for your reply.

I understand it needs to confirm hold time.

I'll ask the customer measure and feedback to you.

I appreciate your great help and cooperation.

Best regards,

Shinichi

0 Shinichi Inoue over 2 years ago

Guru 19701 points

Hi Brandon,

The customer could solve the problem.

As you mentioned, because of the tHDDAT, it could not access 4A.

Could you please see below for more detail.

---

A result of investigation, there was a register that was protected on the master side that adjusted the I2C standard tHDDAT.

The default setting did not satisfy the I2C standard with tHDDAT = 300ns or higher.

When I changed the above register and set tHDDAT = 320ns, the address in question (4A) was able to communicate with I2C.

It was found that this phenomenon had occurred due to a setting error on the master side, and it was resolved.

---

So I'd like to close this thread.

I appreciate your great help and cooperation.

Best regards,

Shinichi

0 Brandon Fisher94 over 2 years ago in reply to Shinichi Inoue

TI__Mastermind 27645 points

Hi Shinichi,

Thank you for confirming the customer's solution worked.

We will close this thread. Feel free to post again if they have any additional questions or issues.

Best Regards,
Brandon Fisher

Sensors

Sensors forum

TMP102: cannot access address 4A