• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 734 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.

TMP006 Write Problem - Read OK

Michael Banak
Intellectual 915 points
Other Parts Discussed in Thread: TMP006

I have no problem reading the TMP006. But I cannot seem to write to it. Additionally, other I2C devices respond nicely for a wide range of I2C functions, include Read, Write and Read Block.

I have two pods, wired identicaally, except for ADDR1 = 1, or 0, between the 2 cases.

ADDR1 = 1, tied right to Vcc 3.3V

Is there some common problem that I should watch for? I see no mention of a seal code in the Data Sheet.

If I successfully READ all locations, and have given up writing, after trying locations 0x02,  0xFE, 0XFF.

Please tell me what you can about this.

Thanks,

Michael A. Banak

  • 0
    Intellectual 915 points
    OK. I just saw that the addresses FE and FF are read only.

    I still have location 0x02, the config register, which reads out OK, but refuses to take a write. Any Ideas?
  • 0 in reply to Michael Banak
    TI__Mastermind 34440 points

    Hi Michael,

    You should be able to write to the configuration register as well as read from it.

    It seems there are other I2C device on the bus. I assume that you are certain that when you read the response indeed comes from TMP006, not one of the other devices, the manufacturer ID and Device ID should be unique. I also assume when you say it “it refuses to take a Write”, you meant you have performed a Write and then perform a Read, and expect to see the same exact value you just wrote to the device? Is it possible for you to capture and send the scope shots for this sequence, including READ and WRITE?

    Guang

    Apps-Sensing Products

  • 0 in reply to Guang Zhou
    Intellectual 915 points
    Thanks, Guang.

    My I2C write/read tool successfully accesses a number of devices on my I2C bus. I have used the same tool to write and read words to other devices, with no problem.

    I have learned that the abilty to write to the device is not part of my functional spec for the system. So, now it is not a priority. I continue to read just fine, though, across both Temperature pods, with their unique addresses. It still bothers me, though, that I cannot do this basic fuinction on these TMP006's.

    If I do not provide the screen shots within a week, you may count this closed.

    BTW: I wish we *could* write to the ID fields. It would help make each response unique.

    Cheers.
    Michael A. Banak
  • 0 in reply to Michael Banak
    TI__Mastermind 34440 points

    Hi Michael,

    You are right it is bothersome when you can read from but not able to write to the device, even if you don’t need the function in your application.

    It may be beneficial to find the root cause from a reliability stand point though. All we need for the scope shots are SCL and SDA signals. Normally you’ll have pull-ups for these pins, and therefore relatively easily accessed.

    Guang

    Apps-Sensing Products

  • 0 in reply to Guang Zhou
    Intellectual 915 points
    Right, Guang. But you, know, of course, I will be studying it before I send it off to you. And that will take a little extra time : - )

    I'm inclined to resolve this, because it may indicate some deeper issue.

    I have a 4-channel oscilloscope, and Ch1 and Ch2 are ALWAYS on the SCL and SDA lines. The behaviour of those lines tells me so much, much like a stethoscope tells a doctor much about the patient.

    Kind regards,
    Michael A. Banak
  • 0 in reply to Michael Banak
    TI__Mastermind 34440 points

    Hi Michael,

    I understand. Please do let us know what you find out.

    Guang

    Apps-Sensing Products