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

ti8168 evm i2c timeouts

Carl Blake
Expert 1160 points
Other Parts Discussed in Thread: TVP7002

I'm writing some code trying to access some of the i2c devices on the i2c-2 bus and I keep getting timeout errors.  I've tried running i2cdetect on both the i2c-1 bus and the i2c-2 bus.  i2cdetect on the i2c-1 bus (command "i2cdetect -r 1") returns valid information - no timeouts.  i2cdetect on the i2c-2 bus (command "i2cdetect -r 2) returns "omap_i2c omap_i2c.2: controller timed out" for every address attempted.  Any suggestions?

Carl

 

  • 0
    TI__Mastermind 20245 points

    Hi,

    I2C-2 is controlled by media controller binary. So if you are using open_max you should not try to access I2C-2. Else you can access.

     

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Expert 1160 points

    I'm not running any application (including matrix-gui-e) which uses open_max.  I would think I would be able to access I2C-2 without any problems.  Is there another process running that might prevent me from being able to do this?  I can access I2C-1 without any problems at all.  It works every time.  I just want to be able to access the TVP7002 within my application.  I also want to be able to access the SIL9022 and the SIL1161.

    Carl

     

  • 0 in reply to Carl Blake
    Expert 1160 points

    I've got the access to I2C-2 working now.  I updated the system to use slaveloader to load the new firmware from TI816x-HDVPSS-01.00.01.33 and now the accesses to I2C devices on the I2C-2 bus return correct data and no longer timeout.  I'm using EZSDK version 5.03.01.15.

    Carl

     

  • 0 in reply to Carl Blake
    TI__Guru 65710 points

    If M3 firmwar from SDK is used, then i2c is controlled by M3 and A8(linux) can not acces and i2c_mode=1 must be set during loading vpss.ko

    If M3 firmware from PSP is used, then I2c is controlled by A8. there is no need to set i2c_mode

    Regards,

    yihe