• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 653 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.

DS90UB948-Q1: I2C Communication Over FPD-Link III with address 0x00

Patrick Chen(TPE System & Application)
Expert 3430 points
Part Number: DS90UB948-Q1

Hi Sir,

My customer is trying to use UB947 to send I2C command through FPD-link to UB948, but they found that they could no send 0x00h slave address to UB948, but they could send other address.

May I know if this is a limitation of FPD-link I2C communication?

Many thanks,

Patrick 

  • 0
    TI__Mastermind 30515 points

    Patrick,

    sorry I can't understand the "can't send 0x00 slave addr. to ub948". But for the remote de-ser / remote slave I2C device, the setting progress is:

    1. I2C master is put in UB947 side, then UB947's 0x03[3] pass-through should be enabled. also to visit the downstream ub948, the 0x1E is set as 0x01 (default) if UB948 is linked to port0 of UB947

    2. UB947's reg. 0x06 is uploaded from UB948 directly after power-on, pls check whether this reg. is UB948's IDX? if NOT, it means the link is not connected correctly, we need resolve this link issue firstly.

    3.You can set the remote slave ID and remote slave ID alias in the reg. of UB947 (total 8 remote slave ID / alias ID can be used)

    4. you can visit ub948 with 0x06 reg. in ub947 as IDX and visit remote slave I2C (which is linked to UB948's I2C bus) with remote slave alias that is set in step3.

    regards,

    Steven

  • 0 in reply to Steven(Shenzhen) Shi
    TI__Expert 3430 points

    Hi Sir,

    Customer already follow those steps and works fine on other I2C address except slave address 0x00h.

    I am sorry that you do not understand my question. let me try to explain again.

    The reason I am asking this is because the I2C address 0x00 is a general call address, I wish to know if UB94x could also support this address as remote slave ID / alias ID?

    1. I2C master is put in UB947 side, then UB947's 0x03[3] pass-through should be enabled. also to visit the downstream ub948, the 0x1E is set as 0x01 (default) if UB948 is linked to port0 of UB947

    Done

    2. UB947's reg. 0x06 is uploaded from UB948 directly after power-on, pls check whether this reg. is UB948's IDX? if NOT, it means the link is not connected correctly, we need resolve this link issue firstly.

    Done

    3.You can set the remote slave ID and remote slave ID alias in the reg. of UB947 (total 8 remote slave ID / alias ID can be used)

    Done with address other than 0x00h. if customer set 0x00h, the I2C command could not be send from UB947 side to UB948 side.

    4. you can visit ub948 with 0x06 reg. in ub947 as IDX and visit remote slave I2C (which is linked to UB948's I2C bus) with remote slave alias that is set in step3.

    Thanks,

    Patrick 

  • 0 in reply to Patrick Chen(TPE System & Application)
    TI__Mastermind 30515 points

    Patrick,

    For your slave addr. 0x00, if my understanding is correct, please check below comments:

    1. For de-ser, the slave addr. is assigned by the de-ser IDX setting, it can't be 0x00.

    2. For the  remote slave IDx, totally FPD-Link can support 8 remote slave ID and 8 remote slave alias ID, all the initial status are 0x00. so all the remote slave ID or the remote alias ID can't be set as 0x00. Actually.

    Steven

  • 0 in reply to Patrick Chen(TPE System & Application)
    TI__Mastermind 30515 points

    Patrick,

    For your slave addr. 0x00, if my understanding is correct, please check below comments:

    1. For de-ser, the slave addr. is assigned by the de-ser IDX setting, it can't be 0x00.

    2. For the  remote slave IDx, totally FPD-Link can support 8 remote slave ID and 8 remote slave alias ID, all the initial status are 0x00. so all the remote slave ID or the remote alias ID can't be set as 0x00. .

    Steven