• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 941 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.

Original question:

TDA4VM: QNX710 + vision_apps : I2C timeout issue

TDA4VM: i2c timeout error in vision app. stop working

user782719
Intellectual 295 points

Part Number: TDA4VM

We use i2c0_main in our sensor driver, however, when we config the sensor, the I2C device encounter a timeout issue, almost every time at the same place. 

We use PSDK 7.01,  and the I2C0_MAIN was disabled in the Linux A72 side. The pinmux of i2c device is configured during the initialization stage.

what could be the problem? Does the i2c0_main was used by other system firmware.

what also capture the i2c signal at the moment i2c0 went dead.

Thank you.

  • 0
    TI__Guru*** 126931 points

    Hi,

    One possibility is that the I2C driver is also being used by the A72 and is causing a conflict. 

    Please try using "slay" or "kill" to stop the I2C0 instance from running on QNX A72, before running the vision_apps test case.

    For example "pidin ar | grep i2c-omap" should show:

    7 i2c-omap35xx -p0x2000000 -i232 -d
    8 i2c-omap35xx -p0x2010000 -i233

    Using the command "kill -9 7" will stop I2C0.   If the test case is then successful, consider removing the I2C driver from the BSP, build file.

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 295 points

    We using linux+rtos, and the i2c instance is disabled in Linux (no show in /dev/ ).    This problem seems only happen when we enable the GSML link between ser/des.

  • +1 in reply to user782719
    TI__Guru*** 126931 points

    Apologies, had seen QNX in the older title and responded accordingly, didn't notice the change.

    Please be aware GMSL is outside of TI support.

    Based on the attached log, it seems that in general I2C writes are working, and it is only one particular write that is failing.  Any chance the device being communicated with has changed state such that it's I2C capability has been impacted?  Does the I2C error always occur always for the same write?

    Regards,

    kb

  • 0 in reply to KB
    Intellectual 295 points

    yes, the i2c controller always down at the same place. we will contact GMSL support for the issue. Thank you.