• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 335 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DS90UB926QSEVB

Michael Denzin
Prodigy 60 points
Other Parts Discussed in Thread: ALP

After looking through the forums, I found a similar question, but no resolution. I am using this eval board along with the ALP software to prove a link between the DS90UB926 on the eval board and a DS90UB921 on our custom board. 

I have lock and can see the 926 on the eval board, but the "Partner Information" is listed as unknown for the 921.

 

  • 0
    TI__Guru* 94190 points

    Hello Michael,

    This looks like a bug in the 921/925 SER ALP Profile. This should be correected in the next ALP releases.

  • 0 in reply to Hamzeh Jaradat
    Prodigy 60 points

    Is it still possible to use the ALP interface to view and change registers on the remote device? The "remote registers" tab is not functional.  Also, is it expected that the I2C interface can be used to communicate with devices on the remote I2C bus?  Thank you.

  • 0 in reply to Michael Denzin
    TI__Guru* 94190 points

    Hello Michael,

    Yes, you can remotely communicate with the SER over the "Scripting" tab.

  • 0 in reply to Hamzeh Jaradat
    Prodigy 60 points

    My system reflects the image above where the deserializer is the 926EVB and the serializer is the 921.  I am not able to see any activity on the serializer side of the I2C. I have set up the deserializer(local) as follows; Back Channel Enabled, Pass-Through enabled, SlaveID set to 0x46 and SlaveAlias set to 0x46. I have a slave device on the serializer(remote) side with an address of 0x46. I have not changed any registers in the serializer(remote) device.

    Using ALP scripting I have proven that I can read the local deserializer using board.Readreg() or even using the address, which is 0x58 using board.ReadI2C(0x58,0x00,1). I can read the serializer registers using its address which is 0x18 by  board.ReadI2C(0x18,0x00,1) and I can write to the serializer using board.WriteI2C(0x18,0x03, 0xXX).

    Summary; Local Deserializer address 0x58. Remote Serializer address 0x18. Remote slave device address 0x46.

    I never see any activity on the serializer (remote) I2C bus when I try to read/write to an external device on that bus. Is there something I need to set up on the remote side for I2C activity? 

    Thanks.

  • 0 in reply to Michael Denzin
    TI__Guru* 94190 points

    Hello Michael,

    Communicating with the remote slave from the DES to SER over the BC is called Camera Mode. For using the Camera Mode you just need to make sure you do followings:

    1) Make sure Back channel is enabled, DES reg 0x01[2]

    2) Make sure either I2C Pass-Through reg 0x03[3] or I2C Pass-Through-All reg 0x05[7] is enabeld.

    3) Make sure the I2C Master on the SER side does support Multi-Master mode, otherwise there will be conflicts.

  • 0 in reply to Michael Denzin
    TI__Guru* 94190 points

    Hello Michael,

    Communicating with the remote slave from the DES to SER over the BC is called Camera Mode. For using the Camera Mode you just need to make sure you do followings:

    1) Make sure Back channel is enabled, DES reg 0x01[2]

    2) Make sure either I2C Pass-Through reg 0x03[3] or I2C Pass-Through-All reg 0x05[7] is enabeld.

    3) Make sure the I2C Master on the SER side does support Multi-Master mode, otherwise there will be conflicts.

  • 0 in reply to Hamzeh Jaradat
    Prodigy 60 points

    Hi Hamzeh,

    One more clarification. The serializer, on the remote end, should just pass I2C activity from the local deserializer, as long as the registers on the local deserializer end are set as you state. 

    There are no registers to set on the remote serializer in order to have the I2C communication from the local side show on the bus.

    Thanks again. 

  • +1 in reply to Michael Denzin
    TI__Guru* 94190 points

    Hello Michael,

    Yes, once you are communicating using your I2C Master on the DES side, the commands will be sent to the SER, which is the Proxy master, and will be forwarded to the appropriate slaves, without the need of changing any register on the SER.