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

DM355 EVM MT9T001 question!

winkyxiao
Intellectual 265 points
Other Parts Discussed in Thread: TVP5146

I am trying to get the CCDC driver running and talking to a M9T001 image sensor hooked up  on the DVEVM DM355.I have a custom pcb that adapts the sensor to the J30，J31  interface using the
same level translators that are used for the tv decoder chip on the board. I
have the CAPTURE_EN pulled high to disable the on-board tv chip.
I compiled the CCDC driver into the kernel as a static module.
I add the following to the bootargs:

bootargs=console=ttyS0,115200n8 noinitrd ip=dhcp root=/dev/nfs rw nfsroot=192.168.0.81:/home/xiao/workdir/filesys mem=116M v4l2_video_capture=:device=MT9T001

 

When i boot the image I get a long list of failed I2C actions (shown below)


Does anyone know what could cause this problem?
Maybe it is an I2C address problem, or some other communication problem,
although I see with the scope that there is definitely I2C data coming into
the M9T001.
Any help would be appreciated.
Thanks,

-winkyxiao

Linux video capture interface: v1.00
Registering platform device 'vpfe.1'. Parent at platform

DaVinci I2C WARNING: i2c: AL detected
DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,                    icstr = 0x410

 
5d<4>DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: RAR detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: RAR detected


5d<4>DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: RAR detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: RAR detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: RAR detected

 


 

  • 0
    TI__Mastermind 37340 points

    Option should read "v4l2_video_capture=device:MT9T001"

    I am guessing it is confused with regards to which I2C device (MT9T001, MT9T031, or TVP5146) to access.  I assume you have the right sensore duaghter card on J30 and J31 connector.

     

     

  • 0 in reply to Juan Gonzales
    Intellectual 265 points

    I make a pice of circuit board for sesor duaghter card , I wonder if that hardware schematic diagram is justify !

    I make PCB board according to the mt9t001's pdf typically Application circuit ! Now DM355 develops the board output to be able to display!

    But cannot the display image, this image likely fingerprint, quite chaotic!please advise!

    thanks everybody!

  • 0 in reply to winkyxiao
    TI__Mastermind 37340 points

    I am not sure I understand this last e-mail.

    1) Can I assume you made your own daughter card based on MT9T001?  Or did you buy the one that is readily available from : http://www.aptina.com/products/demo_kits/mt9t031p12stcd/#overview

    2) How does display fit into the picture?  MT9T001 involves video capture (as opposed to video display) interface.

    If you can help us understand your system, we will be able to advise accordingly.

  • 0 in reply to Juan Gonzales
    Intellectual 265 points

    thanks for you reply!

    sorry for my enlish!I think you have taken my words amiss, that was not my meaning. I did

    not use mt9t001 to show that instead of tv show!tv show Image is not normal,The image shows

    the same as the fog.

    I suspect the problem may be kernel version,My kernel version is 2.6.10_ mv4l, not DVSDK V1.30 Linux Kernel.my The bus because the two devices(tvp5146 and mt9t001) conflict, which could detect I2C bus failed.I think I need to update the kernel version.Now, I do not know where DVSDK V1.30 Linux Kerne version download, I used google search did not find.You give me the URL I read. In fact, I do not want to buy, I need to create its own hands.If everyone can help me, I am very grateful!
     thanks !
    winkyxiao!

    ,

  • 0 in reply to winkyxiao
    TI__Mastermind 41665 points

    If you do not have the proper kernel version than that could explain such issues, you can download the DVSDK software packages which include the kernel at www.ti.com/davinciregistration after you have registered your board, in particular https://www-a.ti.com/extranet/cm/product/dvevmsw/dspswext/general/dm355_dvevm.shtml should open after logging into your my.ti account after registering your board.

  • 0 in reply to Bernie Thompson TI
    Intellectual 265 points

    hi,everyone! 

    I updated version of the kernel, the problem still exists below.

    When i boot the image I get a long list of failed I2C actions (shown below)


    Linux video capture interface: v1.00
    Registering platform device 'vpfe.1'. Parent at platform
    DaVinci I2C WARNING: i2c: AL detected
    DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,                 0

    DaVinci I2C WARNING: i2c: AL detected
    DaVinci I2C WARNING: i2c: NACK detected
    DaVinci I2C WARNING: i2c: RAR detected
    DaVinci I2C WARNING: i2c: NACK detected
    DaVinci I2C WARNING: i2c: RAR detected
    DaVinci I2C WARNING: i2c: NACK detected
    DaVinci I2C WARNING: i2c: RAR detected
    DaVinci I2C WARNING: i2c: NACK detected
    DaVinci I2C WARNING: i2c: RAR detected
    DaVinci I2C WARNING: i2c: NACK detected
    DaVinci I2C WARNING: i2c: RAR detected
    DaVinci I2C WARNING: i2c: AL detected
    DaVinci I2C WARNING: i2c: cmd complete failed: complete = 0x0,                 0

    Who knows the reasons for this problem there?I have been trouble for this issue!
    I do this work for a long time, Hope that someone will guide!
    I2C need to delay the clock too fast?
    thanks!

  • 0 in reply to winkyxiao
    TI__Mastermind 37340 points

     

    TVP5146 vs MT9T001 is software selectable via MSP430 (i2c device); if you pass in the correct information via bootargs to select MT9T001, the drivers will try to talk to it, hence if you do not have a micron daughter card connected on J30 and J31, you will see I2C error.  This is why I was asking if you bought the appropriate off-the-shelf micron daughter card earlier.