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.

Problem with Aptina AR0331 sensor(HiSPi mode) on TI8127 IPNC platform



Hi,

   Does TI 8127 IPNC support Aptina AR0331 HiSpi mode via TI SN65LVDS bridge IC ?

   I tried to implement AR0331 1080P/60 HiSPi on IPNC via TI SN65LVDS bidge ic , but got some problem.

  SN65LVDS does work and PCLK , Hsync signal to IPNC is normal  . However only Vsync signal is random(invoke between several minutes)??

  Sensor and SN65LVDS I2C read/write function is OK.

   I also read out the SN65LVDS registers to check but didn't find out any error setting.   

  -----Check LVDS324 Register:----------------          
     R[0x00]= 0x20                                
    R[0x01]= 0x4c                                
    R[0x02]= 0x56                                
    R[0x03]= 0x44                                
    R[0x04]= 0x53                                
    R[0x05]= 0x33                                
    R[0x06]= 0x32                                
    R[0x07]= 0x34                                
    R[0x08]= 0x1                                 
    R[0x09]= 0x24                                
    R[0x0A]= 0x22                                
    R[0x0B]= 0x7                                 
    R[0x0C]= 0x80                                
    R[0x0D]= 0x4                                 
    R[0x0E]= 0x38                                
    R[0x0F]= 0x60                                
    R[0x10]= 0x0                                 
    R[0x11]= 0x0                                 
    R[0x12]= 0x0                                 
    R[0x13]= 0x0                                 
    R[0x14]= 0x0                                 
    R[0x15]= 0x0                                 
    R[0x16]= 0x0                                 
    R[0x17]= 0x0                                 
    R[0x18]= 0x0                                 
    R[0x19]= 0x0                                 
    R[0x1A]= 0x0                                 
    R[0x1B]= 0x0                                 
    R[0x1C]= 0x0                                 
    R[0x1D]= 0x0                                 
    R[0x1E]= 0x0                                 
    R[0x1F]= 0x7                                 
    R[0x20]= 0x80                                
    R[0x21]= 0x4                                 
    R[0x22]= 0x38                                

   Can anyone give some suggetion to solve.

  Thanks a lot!

  Sean  

 

  

 

 

  • Hi Sean,

    Does Vsync measure 60Hz, and after several minutes is there an unexpected transition?  Or does Vsync just go to 0V entirely?  Are you using the 12-bit mode of AR0331?  The DM8127 is designed to work with the AR0331 and LVDS324.

    Are you using the Engineering Converter Board to interface between the sensor board and DM8127?  If so, how long are the 2 FFC's?  (in this setup, short 3cm FFC's should be used).

    Thanks,
    RE

  • It would also be helpful if you could capture the waveform of the unexpected Vsync signal.

    Thanks,
    RE

  • Hi RE,

     1. I don't measure 60Hz of Vsync, Vsync just go to 0V entirely.

     2. I confige AR0331 as HiSpi 4-lane, 12-bit mode.

     3. The FFC is shorter than 3 cm.

    Do you think the 8127 pin configuration is OK?  Only the Vsync is abnormal , the others are normal. It's very strange.

    I use the IPNC RDK v3.00 firmware.

    Thanks,

    Sean

     

     

     

      

     

  • Sean, can you view the RS-232 log output from the DM8127?  Does it say anything when Vsync goes to 0V?  The log can help us determine what is happening.

    Thanks,
    RE

  • One thing I've seen before is noise on the I2C_SCL signal, since there's coupling from the adjacent D0 signal.  It's possible that this could be your problem (but the log would tell us better).  A simple fix to that issue is to add a 500-700pF cap from I2C_SCL to GND.

    Thanks,
    RE

  • Sean,

    Are you designing your own sensor board using the LVDS chip?

    When you saw VSYNC is abnormal, does it mean that the waveform shape is also random and looks noisy? I saw such a problem on another sensor board which was due to the power supply issue. Can you try connecting the sensor board to a independent power supply?

    Regards

    Rajat

  • Hi Sean, I wanted to make sure you were able to resolve your problem.

    Thanks,
    RE

  •  

    Hi RE:

    Unfortunately, it still doesn't work!

    I also found that M3VPSS main loop will shut down ??

    I tried to print message in the M3SVPSS main loop function to check it's status.

    After a few minutes, the message didn't print out anymore.

    We try to connect our main board to Aptina 9P003 sesnor board and use the ipnc code, so that we cound make sure our main board is OK!

    Thanks,

    Sean 

  • Sean, I understand that the M3VPSS stops printing once Vsync goes to 0V.  Is there any message that it prints right when it stops?  For example, the noise issue that I've seen before causes it to print "I2C: Arbitration lost !!!"  If you see some particular message, that can help us pinpoint the problem.

    Thanks,
    RE

  • Hi RE:

    Here is the RS232 log file,0434.8127_log.txt

    I print the AR0331 and LVDS register settings,but I didn't see the message you mentioned

     

    Thanks,

    Sean