Hi , nvidia teams:
our board is base on “xavier som”,and still use Jetpack 4.4 version, there is a critical issue - “camera causing SError issue”, the log is as:
" CPU3: SError detected, daif=140, spsr=0x40400045, mpidr=80000101, esr=be000000"
I see same log in other posts, these posts all use “Jetpack 4.4” or more older version . and in some of the posts, your suggestion is upgrade “Jetpack”, so, can you confirm, this issue is solved in “Jetpack 5.0.2” and later “Jetpack” version?
the posts for this issue:
The system restarts after the camera is turned on and off continuously for a period of time . Open camera command is “gst-launch-1.0 -v v4l2src device=/dev/video1 ! fakesink” .
The attachment is the test script and kernel log . The kernel error start on line 14152.
[ 3840.652835] TI960-1 0x1 = 0x0[ 3840.818873] CPU4: SError detected, daif=1c0, spsr=0x40c000c5, mpidr=80000200, esr=be000000
[ 3840.818879] CPU2: SError detected, daif=1c0, spsr=0x40c000c5, mpidr=80000100, esr=be000000
[ 3840.81…
Sorry I don’t have this kind of patch now.
The version of jetpack we used was Jetpack4.4_R32.4.3.This is our customer board, there is a restart failure when running on the customer side.The csi interface is 0 and 1,connected with two 2M cameras,mipi frequency is 600Mhz, the system runs immediately after startup, while can0 and can1 have been sending and receiving data.
In my mind, even though have the CSI/VI error, this should not cause a system root problem. The OS system should keep robustness.
https://forums.developer.nvidia.com/t/mipi-csi-vc-problem/189993/15
https://forums.developer.nvidia.com/t/when-the-camera-image-is-obtained-through-v4l2-an-error-
is-reported-which-causes-the-system-to-restart/154608/5
Dear all,
We are setting up 5 OV10635 cameras that using SerDes on Xavier.
The first one is connected to MAX96705-MAX9288 SerDes and it could work as well.
The other four cameras are connected to MAX96705-MAX9286 and even one of them could not work.
I could verify that there was MIPI output from MAX9286 to Xavier but it was so difficult to confirm the correctness.
Then I tried to capture the image with simple v4l2 command and the result as below
v4l2-ctl -d /dev/video1 --stream-mmap --stre…
hello 261136636,
we would like to confirm what’s your use-case.
for example, I don’t see SError detected
errors with normal camera use-case in the latest Jetpack-5.1.3 (r35.5.0) release version.
Hi, JerryChang:
Our boards use-case is in this post:
Open camera, possibilities system reboot - #3 by ShaneCCC
So if we upgrade the “JetPack” version to “Jetpack-5.1.3 (r35.5.0)”, this issue will be solved?
please upgrade to JP-5.1.3 for verification since we also had some bug fixes for SerDes chip use-case.
system
Closed
May 22, 2024, 2:02am
7
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.