• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 101 subscribers
  • Views 374 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.

AM62A7: Using DRV201 VCM driver with AM62AX processor

Jay Kaneria
Intellectual 560 points
Part Number: AM62A7
Other Parts Discussed in Thread: DRV201

Tool/software:

Hi TI Team, 

Yocto SDK: 09_02_00

Board: AM62A SK EVM

We are using the DRV201 VCM driver for camera lens movement with AM62Ax processor. DRV201 is working fine until too much data send and receive happens on that i2c bus. We have observed that when there are too many transaction on the i2c bus on which drv201 is connected, we see SCL is pulled low for more than 0.5ms. according to DRV201's datasheet "The device remains in ACTIVE mode until the
SW_RST bit in the CONTROL register is set, SCL is pulled low for duration of 0.5ms". So looks like DRV201 VCM is getting reset when SCL is pulled low for more than 0.5ms. Please check signal of that i2c bus when clock is pulled low more than 0.5ms.

How can avoid the clock stretching more than 0.5ms from AM62Ax processor side. So, that won't affect the VCM. 

Regards,

Jay

  • 0
    TI__Guru** 100740 points

    Hello Jay,

    Which core is controlling the I2C bus, and what OS is running on that core?

    Is there anything else on the I2C bus other than the AM62Ax and the DRV201?

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Intellectual 560 points

    Hi Nick,

    Thank you for your reply.

    VCM is connected on i2c bus 2 of A53 core. Linux kernel is "6.1.46-rt13-gb871cdee8c". We are using the RT-Linux.

    There is no other device on that i2c bus apart from VCM-DRV201. There was image sensor but we have disconnected image sensor and did continuous register read DRV201 and observed DRV201 reset.

    We have tried to change the i2c bus frequency from 400KHz to 100Khz but issue remain same. We have checked i2c signal i/o level on CRO and those are in the range as well.

    Regards,

    Jay

  • 0 in reply to Jay Kaneria
    TI__Guru**** 189029 points

    Hello Jay, 

    Help me understand the I2C interface you are using.

    Are you able to share the interface schematics.

    Did you see any issue with the I2C interface when the sensor was connected.

    Have you reached out to the DRV201 PL? 

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    Intellectual 560 points

    Hi Sreenivasa, 

    Thank you for your reply.

    Kallikuppa Sreenivasa said:
    Are you able to share the interface schematics.

    Below is the schematics of DRV01 which is connected to i2c-2 (i2c line 2) of A53 processor core.

    10k pull-up is also provided on the i2c line.

    Kallikuppa Sreenivasa said:
    Did you see any issue with the I2C interface when the sensor was connected.

    We haven't seen failure of camera sensor configuration register write.

    Kallikuppa Sreenivasa said:
    Have you reached out to the DRV201 PL?

    I didn't understand this sentence. Can you explain what do you mean by DRV201 PL?

    Regards,

    Jay

  • 0 in reply to Jay Kaneria
    TI__Guru**** 189029 points

    Hello Jay, 

    Thank you.

    Jay Kaneria said:
    Have you reached out to the DRV201 PL?

    I didn't understand this sentence. Can you explain what do you mean by DRV201 PL?

    PL is the product line. I wanted to check if you have also reached out to the DRV201 support.

    I see the I2C2 pulls marked as DNI - could you conform these are installed or if there is pullup somewhere else for the I2C2 interface.

    Regards,

    Sreenivasa

  • 0 in reply to Kallikuppa Sreenivasa
    Intellectual 560 points

    Hi Sreenivasa,

    Thank you for your reply.

    Kallikuppa Sreenivasa said:
    I wanted to check if you have also reached out to the DRV201 support.

    No, We haven't reached to DRV201 support. But looks like it is not problem of DRV201. DRV201 datasheet mentioned "The device remains in ACTIVE mode until the SW_RST bit in the CONTROL register is set, SCL is pulled low for duration of 0.5ms". As you can see in the picture, Clock line is pulled low for 1.6ms and it resets DRV201. Let us know your thoughts on this.

    Kallikuppa Sreenivasa said:
    I see the I2C2 pulls marked as DNI - could you conform these are installed or if there is pullup somewhere else for the I2C2 interface.

    Yes, 10k pull-up is somewhere else for I2C2 interface as shown below.

    Let us know if any other details required.

    Regards,

  • 0 in reply to Jay Kaneria
    TI__Guru**** 189029 points

    Hello Jay, 

    Thank you.

    I am checking with the expert.

    Jay Kaneria said:
    Did you see any issue with the I2C interface when the sensor was connected.

    We haven't seen failure of camera sensor configuration register write.

    Since the issue is with the DRV201, i would suggest checking with the DRV201 Product line.

    Regards,

    Sreenivasa