• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 35 subscribers
  • Views 387 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.

Original question:

DS90UB949-Q1EVM: Accessing remote I2C MCU slave connected with Deserializer-DS90UB926 via Serializer DS90UB949

DS90UB949-Q1EVM: Serializer with default Device Address can't able to detect Deserializer (DS90UB926)

Mohamed Suhaib
Prodigy 20 points
Part Number: DS90UB949-Q1EVM
Other Parts Discussed in Thread: USB2ANY, ALP

Hi, I using the Serializer(DS90UB949 I2C ID- "0x18") and Deserializer(DS90UB926  I2C ID- "0x5A").

Currently I am developing a QT application to read and write to a MCU( I2C ID - "0x6C"), which is connected with the Deserializer(DS90UB926).

The QT tool will run in a host computer, which is connected to the Serializer EVM via USB2ANY - I2C. The Serializer and Deserializer are connected via FPD-Link cable.

For initial setup, I am using ALP tool, I am facing an issue here. Serializer with default Device Address-0x18, can't able to detect Deserializer (DS90UB926)- 0x5A in ALP tool.

If I do "scan connected devices", I am getting a virtual address "0x1A", if I click that "0x1A" option, Deserializer is showing up.

Using this setup, I can able to read and write data to MCU slave using ALP scripts.

But, If I am trying to implement the same Slave ID and Slave Alias ID in QT Application along with Serializer Device address to "0x1A" and General config register(0x03) value as '0xDA' (pass through), MCU communication is not working in QT tool.

Also Serializer-EVM is not storing the register values when we set via ALP tool as well as QT Application. If I power off the EVM, the register values goes off.

I have the below questions,

1. Whether using the Serializer in Virtual address 0x1A is the correct way of communication?

2. Do we need to write Serializer register with ALP tool every time if turning the device power OFF and ON?

  • 0
    TI__Intellectual 2830 points

    Hi Mohamed,

    Thank you for reaching out.

    1. Verify your IDx for the 949 according to Table 9 from the datasheet:

    You can also verify if it's detecting the serializer properly according to it's address by using the follow in the Scripting tab:

    board.ReadI2C(0x18,0)

    2. Yes, doing a power cycle of the device will reset the registers back to their default values.

    Thanks,

    Kate

  • 0 in reply to Kate Hawkins
    Prodigy 20 points

    Hi, I checked the IDx Switch S3 - only first switch is enabled, which is 0x18. I also tested with board.ReadI2C(0x18,0) in ALP scripting Tab, I am getting decimal equivalent value "24" for hexadecimal address (0x18). But still I am confused why deserializer is not showing up in ALP information Tab?

    And Deserializer is connecting only when we select the "0x1A" in "scan connected devices" option. I confused, from where the ALP tool is getting this "0x1A" address?

  • 0 in reply to Mohamed Suhaib
    TI__Intellectual 2830 points

    Hi Mohamed,

    Since you're getting the right feedback from your board.read, this might just be a bug with the information tab in ALP. Have you tried using 0x18 as your address with the QT Tool? Are you getting lock with the 926?

    Thanks,

    Kate