TDA4VM: How to debug and test CSIRX module?

Hi,

I think python script is used for vlab, pc emulation mode. This cannot be used on EVM. 

What exactly issue are you facing? Could you help us understand? Do you want to enable logging in the CSIRX driver?

Regards,

Brijesh 

Hi Brijesh,

I've the same issue. I'm debuging CSIRx driver too. And I don't know where to see GT_Trace output.

Python 3 is included and enabled in psdk v7.2 defaultly, so it can be used on EVM.

root@j7-evm:~# python3 --version
Python 3.8.2

Hi Keelung Yang,

Could you help me understand with what exactly issue are you facing? Do you want to enable trace output to get the debug messages?

Regards,

Brijesh

Hi Brijesh,

Thanks for your quickly reply.

I just want to see csirx's driver debug log when I run ./run_app_single_cam.sh in /opt/vision_apps.

Since I've following timing of operations and the mipi csi clock seems correct once Sensor_StreamOn() is called. I don't know why CSI_RX_IF_VBUS2APB_DPHY_STATUS have no changing on value 0x00222206.That's the reason why I want to debug csirx driver.

Here are my timing of operations from power on to streaming on:

static int32_t Sensor_PowerOn(uint32_t chMask, void *pSensorHdl)
{
    // Set SoC GPIO to high to power on Des(mipi csi output enabled defaultly)
    // Disable Des's mipi csi output since CSIRx is not initialized
}


static int32_t Sensor_Probe(uint32_t chId, void *pSensorHdl)
{
    // Read & log Des/Der/Sensor info
}

static int32_t Sensor_Config(uint32_t chId, void *pSensorHdl, uint32_t sensor_features_requested)
{
    // 1. Config Ser to receive streaming from Sensor
    // 2. Config Sensor to start streaming(Just for debug, since Des mipi csi output is disabled after powering on)
    // 3. Config Des to receive streaming from Ser
}

static int32_t Sensor_StreamOn(uint32_t chId, void *pSensorHdl)
{
    // Enable Des mipi csi output
}

Hi Keelung Yang,

Can you please first below things? 

1, is the number of lanes and lane position setup correctly in the driver data structure?

2, is the lane speed setup correctly, as per the output rate from your sensor/deserializer? 

3, can you please make sure to start deserializer and sensor only after VerifyGraph is called? 

Regards,

Brijesh

Hi Brijesh,

1. Yes. It's 4 lane phy in our des, and the data lane mapping as in UB960 rawtest sensor. And I've confirm them with our hardware team.

2. I've changed our Des DPLL speed to 800Mbps to meet TDA4 defualt speed 400MHz. The PCLK and bandwidth limition among Sensor/Ser/Des are all comfirmed.

3. Des csi output is disabled before VerifyGraph is called, but sensor still streams on in sensor_config(), because I've no sensor datasheet to control it, according some business reasons.

Finally, It works now. It's single cam app in vision_apps: It's trying to create and connect aewb note in graph, no matter aewb is supported in sensor driver. I'll check it in PSDK v7.3 and open a new thread if this issue still exists.

But I'm in the same stuation as the orignal author asked: Where or How can I see GT_trace log output in csirx driver? 

I can see many replies about MIPI CSI from you. They are very helpfull. Thanks for you info again!