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.

I2C Remote Slave with DS90UH948 EVM

Other Parts Discussed in Thread: ALP

I am from DLP group in Dallas using the 925 Serializer EVM with 948 Deserializer EVM and we have our Automotive EVM hooked up to 948 on both the OpenLDI and I2C interfaces.

 

The Video is working fine however we are not able to setup the I2C Remote Slave. Here is the configuration.

 

Laptop (ALP App) <-> 925 <-> 948 <-> DLP Automotive EVM

 

Basically the Laptop is connected to 925 EVM and the Remote Slave is DLP EVM. The I2C addresses for 925 is 0x18 (default), 948 is 0x58 (default) and our DLP EVM is 0x36.

It is not clear how to configure the I2C on the Remote Deserializer to behave as the Master Proxy for the DLP EVM. I have setup the Remote Slave ID address on the Serializer correctly

and also setup the enabled pass-thru on both 925 Serializer and 948 Deserializer.

 

There is an App Note SNLA131A  however it does not have clear instructions or an example. Could you provide the exact steps to setup this correctly.

 

I can be reached at 214-384-5602.

 

This is an important task for us so any help is much appreciated.

 

Regards,

Balaji Srinivasan

214-384-5602

 

  • The system topology tab will reset the aliasing in order to fill out the tree.
    Doesn’t sound like you need this anyway.

    Recommend using the scripting tab instead.
    You would load 0x36 into the alias and ID registers 7 and 8 in the 925.
    You don’t really need to configure the deserializer as it should know to act as a master.

    Please see I2C app note referenced in the product folder for more details
    www.ti.com/.../snla131