Hi
I have made a serdes setup and written a script to enable a communication path using GMSL protocol , and when I run the nvgstcapture-1.0 command i face the issue/error below where my camera is showing blank screen with error below
i have attached the logs after boosting the clocks
imx477_logs.txt (6.7 KB)
Version : R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI:aarch64
Board Jetson Xavier NX
Camera IMX477
HI @ShaneCCC
Is this related to disabling ECC or rtcpu firmware ?
Do you boost the clocks to try?
The error tell the lane control error. Maybe confirm the lane configuration.
@ShaneCCC
yes, i did try with boosting clocks , i confirmed the lane configuration , everything is fine, still i could see the error
and by the way what do you mean by lane control error?
The err_intr_cil_data_lane_ctrl_err0_a of REG PHY_INTR0: NVCSI_PHY_0_CILA_INTR_0_STATUS_CILA_0 maybe confirm the lane configuration for the GMSL setting.
HI @ShaneCCC ,
can you give some more idea on lane configuration for GMSL setting ?
hi @ShaneCCC
corrected the above error by changing the csi lanes from hardware side
Camera node 1
Output Strean W 1920 H 1000
seconds to Run
Frame Rate- 59.999999
GST ARGUS: Setup Complete, Starting captures for o seconds GST ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected, continuing.
CONSUMER: ERROR OCCURRED
ERROR on bust by /GstPipeline:capture_native_pipeline/Gstbin:cap_bin/GsTNvArgus
CameraSrc:nvarguscamerasrcoI TIMEOUT
debug Infor Argus Error Status
GST ARGUS: Cleaning up
**Ressage: 00:41:18.8111 <matn14744» Capture completed
**Hessager 08:41:18.8511 14795» Camera application will now exit
any idea on the timeout error
hi @ShaneCCC
do i need to change lib and RCE firmware as mentioned in this topic Nvarguscamerasrc TIMEOUT
if so i am using 35.4.1 version
can you share the library files necessary for this version ?
What’s the new trace log?
i got this error in the dmesg
[ [1294.501837] [RCE] ERROR: camera-ip/v15/vi5.c:745 [vi5_handle_eof] "General e
rror queue is out of sync with frame queue. ts=1319314104224 sof_ts=13193385306 BB gerror_code=2 gerror_data=400060 notify_bits=20006"
[1552.985792] [RCE] ERROR: camera-1p/v15/vl5.c:745 [vis_handle_eof] "General e rror queue is out of sync with frame queue. ts=1577801262752 sof_ts=15778256890
88 gerror_code=2 gerror_data=400068 notify_bits=20000"
once i got this
[RCE] ERROR: camera-ip/vi5/vi5.c:745 [vi5_handle_eof] "General error queue is out of sync with frame queue. ts=446121787744 sof_ts=446146214464 gerror_code=2 gerror_data=400060 notify_bits=0"
logs_imx477.txt (8.4 MB)
imx477_logs_timeout.txt (68.6 KB
any thoughts @ShaneCCC ?
Apply the attached RCE firmware for it.
I am using Jetson xavier NX , is this the file or any other file with camera-rtcpu-t194-rce.img for Xavier serials as you mentioned above
I have these files below
camera-rtcpu-sce.img
camera-rtcpu-t194-rce.img
camera-rtcpu-t234-rce.img
a) I think what you shared is for Orin Camera failed with log:VIFALC_TDSTATE on Jetpack5.0.2 - #4 by JerryChang, correct me if I am wrong
what are the steps need to be followed to flash on to the Soc?
Note:
Package: nvidia-jetpack
Version: 5.1.2-b104
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.2-b104), nvidia-jetpack-dev (= 5.1.2-b104)
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.2-b104_arm64.deb
For the Xavier need camera-rtcpu-t194.img for it.
camera-rtcpu-t194-rce.img.r35.4.1.asynchronous (513.4 KB)
Hi @ShaneCCC
It’s RCE firmware issue that fixed in later release.
Thanks
Hi @ShaneCCC
thank you for the response,
Now we encountered i2c transfer timeout issue after taking reboot but works fine during power cycle ?
Hi @ShaneCCC ,
I am facing the same error when I take system reboot
Nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
and when i run v4l2-ctl -c bypass_mode=0 --stream-mmap
i see below error
VIDIOC_S_EXT_CTRLS: failed: Device or resource busy bypass_mode: Device or resource busy VIDIOC_REQBUFS returned -1 (Device or resource busy)
I feel this is related to camera reset , can you throw some thoughts on this
What do you mean take system reboot?