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 problem with OMAP3503

Other Parts Discussed in Thread: OMAP3503

Hai Greats,

Hardware Platform: OMAP3503 with PoP NAND and DDR RAM (I2C Master),   MT9V024 (I2C slave).

                                       Note: I2C Bus used is I2C2 of OMAP3503.

Software Platform: Windows CE 6.0

Problem Description:

For Every 14.3 ms, Chip Control Register (Address 0x07) of  MT9V024 is updated through I2C  to enable the context switching. For this the chip control register is written with values 0x8388 and 0x0388 alternatively for consecutive frames. This access was continously done for more than 6 hours (that is only I2C write to that particular register with values 0x8388 for one frame and 0x0388 for the next frame and again 0x8388 for next frame and so on).After 6 hours (approximately), chip control register contains  the value 0x8007 instead of 0x8388 or 0x0388. The value written 0x8007 is not expected. And the next two registers shutter width 1 context A (address 0x08) and shutter width 2 context A (address 0x09) contains 0x0388, which is also NOT expected.

Before this problem occurs, the registers of camera are correct and the values in the registers are as expected.

This looks like some I2C write is getting corrupted.

Did anyone have seen such a problem? Will it be an issue of OMAP or the Camera device or the intermediate circuitary.

Please throw us a light on this issue.

Thanks,

ArunRM.

  • Hi ArunRM,

     

    I am having similar issues, the slave device got unexpected value after long hours of running. The I2C2 controller intermittently reports NACK and AL errors, and leaves incomplete transactions. Have you found a solution to your problem? 

     

    Thanks,

    Bin