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.

TDA4AL-Q1: bringup new camera rtos platform, the func CsirxDrv_udmaTDCEventCb not callback

Part Number: TDA4AL-Q1

SDK verison: 08_06_00

We have configure a new image sensor by guide. The registers are written correctly.
When streamOn, The capture node cannot capture the correct image data, and the CsirxDrv_udmaTDCEventCb not callback.

Now have two question:
1. The relationship between i2cInst and CSIRX_INSTANCE_ID
2. The CSIRX_GetDphyStatus method call results are as follows, whether it seems that csirx is not working?
[MCU2_0] 40.409354 s: ------Csirx_setDphyCfg------
[MCU2_0] 40.409385 s: CSIRX_GetDphyStatus ok
[MCU2_0] 40.409417 s: -dphyStatus.cl_StopState = 1
[MCU2_0] 40.409451 s: -dphyStatus.cl_ULPSActiveNot = 1
[MCU2_0] 40.409487 s: -dphyStatus.cl_RxULPSClkNot = 1
[MCU2_0] 40.409534 s: -dphyStatus.dlStopState = [1, 1, 1, 1]
[MCU2_0] 40.409583 s: -dphyStatus.dlULPSActiveNot = [1, 1, 1, 1]
[MCU2_0] 40.409632 s: -dphyStatus.dlRxULPSEsc = [0, 0, 0, 0]

  • Hi li liu,

    Can you please check and confirm that 

    - the number of lanes configured in the CSIRx is matching with what is connected from the sensor/deserializer?

    - lane polarity is matching.

    - the lane speed is correctly configured in the CSIRX and is matching with output lane speed in deserializer

    - output data type and virtual channel are correct and as per the output in derializer/sensor.

    - sensor/deserializer output is only enabled in streamon callback and not before this callback. It is ok to have clock output enabled, but data output must be enabled only in streamon callback. 

    Regards,

    Brijesh

  • We have fixed this issue. it is caused by wrong speed configured.