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.

MIPI camera interface on OMAP3530 CUS package

Other Parts Discussed in Thread: OMAP3530

My customer has a couple of questions about using the CSI1b interface on the OMAP3530. He has a CUS package, so he cannot use CSI2, for which we actually have a driver available (WInMo, but it's close enough to WInCE for him to be able to use), so he will have to make some changes. The following HW questions I have not been able to answer, please help:

1.  When only using CSI1 (cam_d6 through cam_d9) can the other camera bus bit be left floating or should they be pulled ?

2. For the MIPI use on the receiving end at the OMAP is there any need for external termination resistors like 100 ohms for subLVDS? Is that built in the OMAP?

Any help on this would be appreciated.

Regards

Tiemen

  • 1.  When only using CSI1 (cam_d6 through cam_d9) can the other camera bus bit be left floating or should they be pulled ?

    o     Other cam pins in this scenario could be used as general purpose I/Os with exception of cam_d0 and cam_d1 which would be Input only.  Internal PU and/or PD options exist in pad configuration for these pins so they could be configured internally and left floating externally for this configuration.

    ·         2. For the MIPI use on the receiving end at the OMAP is there any need for external termination resistors like 100 ohms for subLVDS? Is that built in the OMAP

    o    DSI & CSI  on OMAP35x do not require external terminations. They are part of the chip’s internal device structure so that the terminations can be switched on and off as needed under MIPI spec.