hello Kevin_Wang2025,
it looks okay basically.
please note that, SerDes chip as a bridge for sending MIPI packets, serdes_pix_clk_hz should be greater than or equal to pixel_clk_hz, it depends-on your actual use-case.
Hi Jerry,
Now the dual camera works fine by setting pixel_clk_hz to 148500000, and serdes_pix_clk_hz to 750000000. Thank you for your recent patient help. ^_^
Next I have another question about CPHY test.
I recently tested CPHY on the Orin Dev Kit. The deserializer on the acquisition board hardware is currently only connected to the CSI-E port of Orin, but the port is in DPHY mode by default. I did not find CSI-related keywords in the pinmux.dtsi file generated by the pinmux table. How can I modify it? Thank you.
hello Kevin_Wang2025,
please refer to developer guide, Individual Imaging Devices for the phy_mode settings.
you may also update those device tree settings accordingly for changing to CPHY.
let’s have another new discussion thread for your follow up issues.
Hi Jerry,
I have create a new discussion 336982 to follow up.
Hi Jerry,
I found that most of the time four videos can work well, but sometimes one of the videos will report VI uncorr_err “request timed out after 25000 ms”, but the serdes’s status register show the camera has send data to VI module. What reason causes that happen? Thank you!
hello Kevin_Wang2025,
may I know which Jetpack release version it is?
what’s the condition to reproduce the failure, any failure rate for reference?
since this is thread for SerDes camera bring-up, which has completed.
let’s open a new topic for tracking stability issue
Hi Jerry,
The issue I have fixed by remove phy force enable register configuration to deserializer start streaming function. And fix the nvcsi channel 3 port-index to correct.
BTW, this is thread for SerDes camera bring-up, which has completed.
are we able to close this discussion thread?
Hi Jerry,
Yes , you can.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.