Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 271 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.

DS90UB948-Q1: Is there a way to set Serial Control Bus Address to 0x6A

Wei Xiao
Intellectual 455 points
Part Number: DS90UB948-Q1

In our application, we need to set deserializer's Serial Control Bus Address to 0x6A. Is there a way to set it that way for DS90UB948?

  • 0
    TI__Mastermind 23200 points

    Hi Wei,

    No, unfortunately, 0x6A is not a configurable address for the UB948. One option you may be able to do is set 0x6A to a deserializer alias so that any instructions with the address 0x6A will be directed to that deserializer.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    Intellectual 455 points

    Hi Ryan,

    Thanks for the reply. Please let me know how to set the Alias for a deserializer. 

    Basically, after we set the alias, then communications intended for a deserializer with 0x6A address will be directed to the deserializer with 0x6A alias and all bidirectional communications should be normal?

  • 0 in reply to Wei Xiao
    TI__Mastermind 23200 points

    Hi Wei,

    This is done by setting the one of the SlaveID[x] and SlaveAlias[x] registers to the value of the ID and alias ID respectively (I.E SlaveID[0] and SlaveAlias[0]). This should have any instruction sent to the address specified in SlaveAlias to go to the corresponding SlaveID.

    You also need to enable I2C passthrough in register 0x05.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    Intellectual 455 points

    Hi Ryan,

    Thanks for the information. I checked out the data sheet. I am not sure if I understand it correctly. I think the SlaveID and SlaveAlias settings of deserializer are for deserializer communicating with remote devices attached to the serializer.

    However, you mean if we set deserializer address through IDx pin to 0x6C, set deserializer register SlaveID[0] to 0x6C and SlaveAlias[0] to 0x6A and enable I2C pass through , then communication coming from serializer intended for 0x6A will be directed to the deserializer itself?

  • 0 in reply to Wei Xiao
    TI__Mastermind 23200 points

    Hi Wei,

    Sorry, I should've been more specific.

    If you do these settings at your serializer, rather than your deserializer, instructions correlated with the alias set for the deserializer should be sent to the deserializer. 

    Please let me know if you have any other questions or concerns.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    Intellectual 455 points

    Hi Ryan,

    If serializer is on a remote device not designed by us, then no way to make ub948 communicate with it if serializer was designed to communicate with deserializer with 0x6A address?

    thanks

  • 0 in reply to Wei Xiao
    TI__Mastermind 23200 points

    Hi Wei,

    Could you draw a block diagram to illustrate the setup?

    If the 948 is able to communicate locally with the serializer, it should be able to set the needed registers.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    Intellectual 455 points

    Original design is like below picture. Ub925 is on HMI, and ub926 is on screen. The address for ub926 is 0x6A. Now we are designing a device to replace the screen to interface with the HMI. We want to use ub940 or ub948. They are only connected to HMI through STP cable. We have no control over the hardware and software of HMI. In this case, how can we make the pair work properly ? Both display and touch are communicated through the STP cable.

  • 0 in reply to Wei Xiao
    TI__Mastermind 23200 points

    Hi Wei,

    If you are unable to talk to the 925 or update the software/script surrounding the 925, then I am not sure that you will be able to update the 925 for the different addresses, as you will need to be able to communicate with the 925 for this process.

    Thanks,

    Ryan

  • 0 in reply to Ryan Kitto
    Intellectual 455 points

    Hi Ryan,

     I wonder if there is any workaround. For example, can ub948 pass the I2C communication to another ic downstream with 0x6A address then the ic acts as communication intermediate of ub925 and ub948?

  • 0 in reply to Wei Xiao
    TI__Mastermind 23200 points

    Hi Wei,

    This is not something we have tested on our end, so I can't say for sure whether this is a possibility or not. Our best recommendation is to see if there is away to get around the issue of being unable to edit the software surrounding the ub925.

    Thanks,

    Ryan