Hi,Support team
I had some problems from the CPHY camera module on AGX Orin. The Jetpack version is 5.0.2. When we use the agx orin modules to capture image of CPHY mode and 3 trio , some of the modules can not capture image. It supports up-to 2.7Gsps per trio for running CPHY interface. The kernel log and rtcpu log are as follows. How to solve this problem? Thanks!
kernel(1).log (3.9 KB)
rtcpu.log (1.2 MB)
Could you share more information about your test?
We need to check the bandwidth firstly.
hello 0804,
we may need to confirm the output data rate you’re using. for example, 1-trio, 3-trio? 1.5 Gsps or higher?
would also like to know the hardware difference, since you’ve mentioned… some of the modules can not capture image
Hi Jerry,
The output data rate is 3-trio and 2.7Gsps.
hello 0804,
may I also confirm the hardware difference, why some of the modules can not capture image.
There was no difference in the hardware, we only replaced the module.
were those modules with different SKUs?
Hi Jerry，
May I ask how to view the SKU?
You can read the SN number in system or take a picture at the module,
Their is a QR code to record this.
The SN number are 1420123021643 and 1420223006668.
Sorry for confuse, the model num followed by SN indicate the SKU.
pls share this, we are checking internally based on your configuration.
Hi，alanz
The picture of the modules are as follows.
Hi , alanz
We have shared the SKU of the modle. How is the check going?
hello 0804,
they’re same modules, (i.e. Jetson AGX Orin 32GB) according to Jetson FAQ.
may I also confirm the trace length? did they (workable/non-workable environments) using the same camera setups?
Hi, Jerry
The trace length is about 3600mil. And they using the same camera setups.
Hi, Jerry
The trace length is about 3600mil. And they using the same camera setups. Do you need any more information?
the channel length is around 9.1cm, it should have little insertion loss. please give it try for setting higher symbol rates for testing.
Hi Jerry
We fail to capture image at this rate. Could you tell us why we should try a higher rate for testing? What do we need to analyze the problem without trying for setting a higher rate?
Thanks!
hello 0804,
please refer to developer guide, Sensor Pixel Clock to examine your clock calculation.
and… I meant trying with higher pix_clk_hz in the device tree property settings.
Hi Jerry
We have verified that raising the “pix_clk_hz” to 3.2Gsps and 3.8Gsps will also caused image capture failed.