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.

DS90UB633A-Q1: How to transmit sensor's error to DS90UB662-q1?

Part Number: DS90UB633A-Q1
Other Parts Discussed in Thread: DS90UB662-Q1,

Dear team,

The DS90UB633A-Q1 serializer GPOs cannot be configured as inputs for remote communication with deserializer. If we need to transmit sensor's error to the ADAS ECU(DS90UB662-Q1 board), how to achieve it?

Thanks & Best Regards,

Sherry

  • Hello Sherry,

    you just want to use a SER GPIO as an Input to transmit the sensor's error to the ECU via DES GPIO, correct?

    Can you specify which GPIO you would like to use on bth sides?

  • Hi Hamzeh,

    Thanks for your reply!

    Yes, I hope to use SER GPIO as an input to pass through sensor's error to ECU via DES GPIO.

    GPIO 1 or GPIO 3 will be good choices. Can we achieve this pass through?

    In the 662 datasheet, it said that forward channel GPIO is not available for 633, so in my understanding, 633 can't achieve GPIO pass through function when 633's GPIO acts as input. Then how do we transmit the sensor's error to ECU? Can we use 633's DIN pin to achieve this function, but how to achieve it?

    Thanks & Best Regards,

    Sherry

  • Hello Sherry,

    please use the following settings:

    On the SER:

    0x0D=0x00

    0x0E=0x0F

    0x33=0x05

    On the DES:

    0x0F=0x77

    0x13=0x61

  • Hi Hamzeh,

    Based on your reply, our 633 can pass the sensor error to 662 via GPIO, right?

    But I can't understand your register configuration. Is your configuration for GPIO3 or GPIO1? Customer said that their GPIO2 is no use now, so we have to use GPIO2 to pass through. In my understanding, on the SER, we have to set GPIO2 as input signal, so we set 0X0e bit3-0=0001. I don't understand why you also set 0x0e and 0x0d at the same time. In addition, could you please tell me what is 0x33 which is reserved in the datasheet? On the DES, we need to set GPIO2 as output, so we set 0X0F bit2=0 and 0x12=0x41.

    I tried to test it in our 964 and 933 demo board, but I can't change 933's 0x33, then I failed. I tried to write it in the scripting, board.writeI2C(0xb0,0x33,0x05), but I can't write successfully with unknown reason. I tried to use 960&933, but it seems 960's default hardware configuration should be changed because the lock is always loss when I connect 960 to 933 while 964&933 works normal.

    Could you please tell me whether GPIO's pass through function can achieve this function? If it can, please help list the register configuration again, thank you!

    Thanks & Best Regards,

    Sherry

  • Hi Hamzeh,

    Could you please give me a reply? My customer is waiting for the answer to continue the schematic.

    Thanks & Best Regards,

    Sherry

  • Hello Sherry,

    My apologies for the confusion. The UB633 does not have any GPIOs, only GPOs.

    If you need to send an additional signal through the forward channel then you would need to use one of the video data bits as an input instead of for video. Or the UB633 side can access the remote deserializer via I2C if there is a local master at the serializer 

  • Hi Hamzeh,

    Thanks for your reply! 

    If I use 32 pin--DIN[11] to pass sensor error, then how do we decode the signal from 662 side?

    Thanks & Best Regards,

    Sherry

  • Hi Sherry,

    again sorry for the confusion. This will ofcourse only works if the SER is paired to a parallel DES not an CSI-2 DES!!

  • Hi Hamzeh,

    Thanks for your reply!

    When we use 633 and 662, do we have any other solution to pass through the signal from 633 to 662?

    Thanks & Best Regards,

    Sherry

  • Hello Sherry,

    I believe the only way is that the UB633 side can access the remote deserializer via I2C, but this will only work if there is a local master at the serializer side.

  • Hi Hamzeh,

    Ok, got it! 

    Thanks & Best Regards,

    Sherry