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.

Dm8168 in m3vpss side can not use i2c0?

hello everyone!

    I have a question about use i2c0 in m3vpss side!  The hdvpss version is HDVPSS_01_00_01_28.

    I  find  that if I write code like this   <   *(volatile unsigned short *)(0x480280a4) = (0)  > on dsp bios6 system.(0x480280a4 is i2c0 CON Register).

     the bios6 system is look like halt. when code is run there .

 

So can someone tell me what's problem?

 

thanks!

  • Hi,

    We have found issue with I2C driver inside HDVPSS. We are in process of fixing it. You will get fix in next HDVPSS release. Please refer that code for programming of I2C on DSP side.

    Regards,

    Hardik Shah

  • thank you for your reply

    BUT I do not understand that problem is software problem. net HDVPSS can fix it?

    on HDVPSS side , we use phy addr to read write I2c Register.So How can software fix this? I think this is hardware problem? on HDVPSS side we could not acess I2C0 Register? But I have not datasheet to confirm this .... Right?

     

    Thanks

  • In the current HDVPSS SW, only I2C1(DM816X) or I2C2(DM814X) was used. since you want to access I2C0, first I2C0 should be configured properly in the PRCM module, such as enable the clock, bring it out of reset. without having these, accessing I2C0 register could cause sysem isssue. You can refer how I2C1 or I2C2 is configured.

    Regards,

    yihe

  • Thank you very much!

     As you say!  I have fixed this problem!

     

    Thank you

  • Good to hear this, I has verified the answer and closed this post.

    Thanks.

    yihe

  • Hi yihe,

    Could you please tell us why HDVPSS-M3 firmware access I2C? Do you mean the I2C1, in case of DM8168, cannot be used by other applications?

    Best regards,

    Jed ZHU

  • I2C1 instance(if count from 0) is used for video capture/display via the daughter cards. The capture/display drivers are developed in M3 side. therefore accessing i2c1 from A8(linux) is not allowed.

    But this issue has been solved since SDK 05.03 release. Two different M3 firmware have been provided: dm816x_hdvpss.xem3(having I2C1 control from M3), dm816x_hdvpss_v4l2.xem3(having i2c1 control from A8).

    You can choose the right firmware to load.

    Regards,

    yihe