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

DS90UB960-Q1: 960+953 Implementation Questions

Sepeedah Zadeh
Expert 3310 points

Part Number: DS90UB960-Q1

Hello team, 

We are considering a design with customer using 960+953 and had below questions:

- Is there a way to have PDM mic data in the same line? I'm not finding anything in this regard

- How much power can we drive through coax with POC? What is the max power draw (peak and steady)?

- If there is a separate I2C interface for each camera, and if there are 4 FPD interfaces and 2 I2C interfaces, how would that work? There will also be a few other non-camera I2C devices on this line--> What I understand is that the secondary I2C line on 960 is only recommended to be used if there are two host processors (rather than trying to address each camera individually). I see this app note (http://www.ti.com/lit/an/snla222/snla222.pdf) but am still not quite sure how it would apply to 960 since there is one DES address. 

Thanks!

  • 0
    TI__Expert 3390 points

    Hi Sepeedah,

    1) That interface is not available. We offer i2s on some parts but not these two.

    2) We have a recommended network in the datasheet on Figure 40 which is rated for about 250mA, typically it is used with a 12V source from a battery.

    3) You'll need to assign alias addresses to each camera, so you can communicate to each one individually. Check section 7.5.3-7.5.5, basically in the registers tab of the 960, you can assign an alias and ping that alias to communicate with the remote sensors or Serializers.

    a) If you have more than one Deserializer, then you'll need to strap each one to it's own i2c address via the IDX strap pin.

    Regards,

    Mandeep Singh

  • 0 in reply to Mandeep S
    TI__Expert 3310 points

    Thank you Mandeep! Some follow on questions:

    1) The infotainment parts would be the ones with I2S support, correct?

    2) Thanks for pointing out the example, so assuming 12V from source, then 3W for this specific implementation. Can you please confirm the max power (peak and steady) we'd be able to support using PoC? Do we have any tools for PoC filter design based on customer implementation? I'm not finding any other than recommendations we have in datasheet and EVM. I see this post  mentioning higher current levels (>500mA) being possible, so an understanding of what is our max threshold and major factors that dictate this threshold would be very helpful.

    Thank you!

  • 0 in reply to Sepeedah Zadeh
    TI__Expert 3310 points

    Mandeep, 

    Follow on to point 1) is there a way to use GPIOs for I2S?

    Thanks!

  • 0 in reply to Sepeedah Zadeh
    TI__Expert 3390 points

    Hi Sepeedah,

    Take a look at the app note below, it discusses this topic in detail.

    Regards,

    Mandeep Singh