• Resolved

DS90UB933-Q1: Problem in Serializer Powerup Sequence

Intellectual 820 points

Replies: 15

Views: 224

Part Number: DS90UB933-Q1

Hi all,

I am using TDA2Sx with DS90UB933-DS90UB934 pair to communicate with sensor. I am unable to establish connection with Serializer from Deserializer. My hardware team is also looking into this issue. I am suspecting problem in power-up sequence.

In UB933 Serializer Datasheet page#35 8.1.2 Power-Up Requirements and PDB Pin Section it is given that GPO2 should be low when PDB goes high for power-up sequence. But it also says

"If GPO2 state is not determined when PDB goes high, DS90UB933 registers must be programmed to configure the transmission mode. Mode Select register 0x05[5] must be set to 1 and register 0x05 bit 1 and 0 are to be selected based on desired 12-bit or 10-bit transmit data format."

In our case , we see that GPO2 is High (probed with CRO)

I am surprised to see, without power-up sequence and i2c communication, How are we supposed to program the register 0x05.

I am little bit confused, whether did we missed anything?

Looking for support to understand and overcome this problem.

Regards,

ARUNKUMAR V N

  • Hello Arun,

    The programming steps would be performed locally to the 933 in this case if the GPO2 state was incorrect when the part powered up - not over the back channel. 

    But you are correct to suspect this as the culprit for your issue because the GPO2 state is critical for the power sequence of the device. Please provision to keep it low before PDB starts rising. 

    Best Regards,

    Casey 

  • In reply to Casey McCrea:

    Hi Casey,

    As you know, GPO2 is output pin. My Hardware team modified PDB pin resistance and made power sequence is seems like proper. LOCK and PASS also High. But, Still i2c communication is not established. Unable to get the i2c address from i2c-probe.

    Could you please see the below screenshot and tell me, if we need pull down resistor for GPO2 or any other modifications required to do ?

    Regards,

    ARUNKUMAR V N

  • In reply to ARUN KUMAR1:

    Hello Arun,

    Can you please tell me the sensor address and any register configurations you have done to 934 after power up?

    Thanks,

    Casey 

  • In reply to Casey McCrea:

    Hi Casey,

    Thanks for quick reply,

    Please see the below configuration of Deserializer - 0x34 (7-bit)

    {0x01, 0x02},

    {0x4c, 0x01},

    {0x02, 0x9e},  

    {0x6D, 0x03},

    {0x58, 0x58},

    {0x5B, 0xB0}, -> 933 Serializer Address 0xB0 (8-bit)

    {0x5C, 0xBC}, -> 933 Serializer Alias Address 0xBC (8-bit)

    {0x5D, 0xC0}, -> Camera Address 0xC0 (8-bit)

    {0x65, 0xCC}, -> Camera Alias Address 0xCC (8-bit)

    I changed {0x58, 0xDE} and tried for expermentation.

    Please see the below query asked in forum regarding 934 sequence :

    Regards,

    ARUNKUMAR V N

  • In reply to ARUN KUMAR1:

    Ok Arun,

    So first thing - can you confirm the cabling type used here? Is it coax or STP? Also what is the MODE setting for this system? Is RAW10 mode the correct one for the sensor?

    Also can you read/write registers from the remote serializer? Or are you unable to communicate with both the serializer and the sensor itself?

    Best Regards,

    Casey 

  • In reply to Casey McCrea:

    Hi Casey,

    can you confirm the cabling type used here?

    I am using STP Communication via USB-C (USB 3.1).

    Is it coax or STP? Also what is the MODE setting for this system? Is it coax or STP? Also what is the MODE setting for this system?

    Mode : Raw10

    Yes, I am using OV2311 Monochrome Sensor which gives output in format : 10-bit Raw.

    read/write registers from the remote serializer? Or are you unable to communicate with both the serializer and the sensor itself?

    Still, communication is not established from Deserializer to Serializer, So unable to communicate with both sensor & serializer.


    Regards,

    ARUNKUMAR V N

     

  • In reply to ARUN KUMAR1:

    Hi Arun,

    Please provide the schematic of the board.  There are hardware differences between STP (not shown in the evm) and coax (as shown on the evm).

    Also, please verify the following:

    1) Ability to read the registers from the deserializer via a direct i2c connection

    2) Ability to read the registers from the serializer via a direct i2c connection

    With the direct connection, read the register with respect to the link status.  Please ensure that the link status is solid and doesn't drop out intermittently.  Verify the link status with both devices directly.

    Ultimately, the i2c and slave addressing will need to be configured.  Assuming all of the steps above were successful with a link, the next steps would be a proper bring up and configuration of the addresses the devices will use. 

    There is a good example script in the 954 Reference scripts found in ALP.  It doesn't map 1:1, but provides a good path forward showing how to the 954 is configured followed by the remote+slave.

    The example script may be found in your install of Analog Launch Pad, found here:

    C:\YOUR_INSTALLATION_PATH\Analog LaunchPAD v1.57.0010\Analog LaunchPAD v1.57.0010\PreDefScripts\DS90UB954\sensor_init_1920_1080_30fps_REMOTE.py

    Sincerely,
    Bryan Kahler

  • In reply to Bryan Kahler:

    Hi Arun,

    Haven't heard back in a few days - hope all is going well.  If the issue still persists, please let us know.

    Sincerely,
    Bryan Kahler

  • In reply to Bryan Kahler:

    Hi Bryan Kahler,

    Thanks for your input.

    There is some hardware problem before and i don't have an option to read serializer directly. My Hardware team doing this setup. After setup i'll check it.

    At present, with same USB-C setup i can able to read and write serializer and sensor. But, Camera capture is not happening. please see the below log.

     [HOST] [IPU2  ]     88.287531 s:  CAPTURE: VIP3 Slice0 PortA FRAME MODE
     [HOST] [IPU2  ]     88.287653 s:  
     [HOST] [IPU2  ]     88.287714 s:  [ CAPTURE ] Link Statistics,
     [HOST] [IPU2  ]     88.287775 s:  ******************************
     [HOST] [IPU2  ]     88.287836 s:  
     [HOST] [IPU2  ]     88.287866 s:  Elapsed time       = 27167 msec
     [HOST] [IPU2  ]     88.287958 s:  
     [HOST] [IPU2  ]     88.287988 s:  
     [HOST] [IPU2  ]     88.288019 s:  Input Statistics,
     [HOST] [IPU2  ]     88.288080 s:  
     [HOST] [IPU2  ]     88.288110 s:  CH | In Recv | In Drop | In User Drop | In Process
     [HOST] [IPU2  ]     88.288202 s:     | FPS     | FPS     | FPS          | FPS        
     [HOST] [IPU2  ]     88.288293 s:  --------------------------------------------------
     [HOST] [IPU2  ]     88.288354 s:  
     [HOST] [IPU2  ]     88.288415 s:  Output Statistics,
     [HOST] [IPU2  ]     88.288476 s:  
     [HOST] [IPU2  ]     88.288507 s:  CH | Out | Out     | Out Drop | Out User Drop
     [HOST] [IPU2  ]     88.288568 s:     | ID  | FPS     | FPS      | FPS           
     [HOST] [IPU2  ]     88.288659 s:  ---------------------------------------------
     [HOST] [IPU2  ]     88.288873 s:  
     [HOST] [IPU2  ]     88.288934 s:  [VIP3 Slice0 PortA] Statistics
     [HOST] [IPU2  ]     88.288995 s:  ==============================
     [HOST] [IPU2  ]     88.289056 s:  Number of request queued  : 1
     [HOST] [IPU2  ]     88.289117 s:  Number of request dequeued: 0
     [HOST] [IPU2  ]     88.289178 s:  Overflow Count            : 0
     [HOST] [IPU2  ]     88.289269 s:  
     [HOST] [IPU2  ]     88.289300 s:     CH    |     Q      DQ     Total   Top     Bot    Total  Top    Bot   Min/Max     Min/Max   Dropped  Repeat   Fid   Desc
     [HOST] [IPU2  ]     88.289422 s:  (I/S/CH) |   Count   Count  Fields  Fields  Fields   FPS   FPS    FPS    Width       Height   Frames   Frames  Repeat Error
     [HOST] [IPU2  ]     88.289574 s:  ---------------------------------------------------------------------------------------------------------------------------
     [HOST] [IPU2  ]     88.289879 s:   08.0.00 |       6       0       0       0       0      0     0     0     0/0         0/0           0       0       0     0
     [HOST] [IPU2  ]     88.290001 s:  
     [HOST] [IPU2  ]     88.290550 s:  
     [HOST] [IPU2  ]     88.290611 s:  [ ENCODE ] Link Statistics,
     [HOST] [IPU2  ]     88.290703 s:  ******************************
     [HOST] [IPU2  ]     88.290764 s:  
     [HOST] [IPU2  ]     88.290794 s:  Elapsed time       = 27010 msec
     [HOST] [IPU2  ]     88.290855 s:  
     [HOST] [IPU2  ]     88.290916 s:  
     [HOST] [IPU2  ]     88.290947 s:  Input Statistics,
     [HOST] [IPU2  ]     88.291008 s:  
     [HOST] [IPU2  ]     88.291038 s:  CH | In Recv | In Drop | In User Drop | In Process
     [HOST] [IPU2  ]     88.291130 s:     | FPS     | FPS     | FPS          | FPS        
     [HOST] [IPU2  ]     88.291191 s:  --------------------------------------------------
     [HOST] [IPU2  ]     88.291313 s:  ENCODE: Num process reqest count for chId: 0 = 0
     [HOST] [IPU2  ]     88.291404 s:  ENCODE: Num process complete count for chId: 0 = 0
     [HOST] [IPU2  ]     88.291496 s:  
     [HOST] [IPU2  ]     88.291526 s:  [ ENCODE ] LATENCY,
     [HOST] [IPU2  ]     88.291587 s:  ********************
     [HOST] [IPU2  ]     88.291648 s:  
     [HOST] [IPU2  ]     88.291709 s:  HDVICP-ID: 0
     [HOST] [IPU2  ]     88.291770 s:  
     [HOST] [IPU2  ]     88.292106 s:  
     [HOST] [IPU2  ]     88.292136 s:  [ IPC_OUT_0 ] Link Statistics,
     [HOST] [IPU2  ]     88.292197 s:  ******************************
     [HOST] [IPU2  ]     88.292258 s:  
     [HOST] [IPU2  ]     88.292289 s:  Elapsed time       = 27011 msec
     [HOST] [IPU2  ]     88.292380 s:  
     [HOST] [IPU2  ]     88.292411 s:  Driver/Notify Cb   =  96.36 fps
     [HOST] [IPU2  ]     88.292502 s:  
     [HOST] [IPU2  ]     88.292533 s:  Input Statistics,
     [HOST] [IPU2  ]     88.292594 s:  
     [HOST] [IPU2  ]     88.292655 s:  CH | In Recv | In Drop | In User Drop | In Process
     [HOST] [IPU2  ]     88.292746 s:     | FPS     | FPS     | FPS          | FPS        
     [HOST] [IPU2  ]     88.292807 s:  --------------------------------------------------
     [HOST] [IPU2  ]     88.292899 s:  
     [HOST] [IPU2  ]     88.292929 s:  Output Statistics,
     [HOST] [IPU2  ]     88.292990 s:  
     [HOST] [IPU2  ]     88.293021 s:  CH | Out | Out     | Out Drop | Out User Drop
     [HOST] [IPU2  ]     88.293112 s:     | ID  | FPS     | FPS      | FPS           
     [HOST] [IPU2  ]     88.293173 s:  ---------------------------------------------
     [HOST] [IPU2  ]     88.293387 s:  
     [HOST] [IPU2  ]     88.293417 s:  [ IPC_OUT_0 ] LATENCY,
     [HOST] [IPU2  ]     88.293478 s:  ********************
     [HOST] [IPU2  ]     88.293509 s:  
     [HOST] [IPU2  ]     88.295247 s:  
     [HOST] [IPU2  ]     88.295308 s:  [ VPE ] Link Statistics,
     [HOST] [IPU2  ]     88.295369 s:  ******************************
     [HOST] [IPU2  ]     88.295430 s:  
     [HOST] [IPU2  ]     88.295461 s:  Elapsed time       = 26756 msec
     [HOST] [IPU2  ]     88.295552 s:  
     [HOST] [IPU2  ]     88.295583 s:  
     [HOST] [IPU2  ]     88.295674 s:  Input Statistics,
     [HOST] [IPU2  ]     88.295705 s:  
     [HOST] [IPU2  ]     88.295766 s:  CH | In Recv | In Drop | In User Drop | In Process
     [HOST] [IPU2  ]     88.295827 s:     | FPS     | FPS     | FPS          | FPS        
     [HOST] [IPU2  ]     88.295918 s:  --------------------------------------------------
     [HOST] [IPU2  ]     88.296010 s:  
     [HOST] [IPU2  ]     88.296040 s:  Output Statistics,
     [HOST] [IPU2  ]     88.296101 s:  
     [HOST] [IPU2  ]     88.296132 s:  CH | Out | Out     | Out Drop | Out User Drop
     [HOST] [IPU2  ]     88.296193 s:     | ID  | FPS     | FPS      | FPS           
     [HOST] [IPU2  ]     88.296284 s:  --------------------------�-------------------

    Regards,

    ARUNKUMAR V N

  • In reply to ARUN KUMAR1:

    Hi Arunkumar,

    Thanks.  Please let us know when you're able to communicate with the device.

    Sincerely,
    Bryan Kahler