Difference between revisions of "eLinux.org:Jetson/L4T/Camera BringUp"

From eLinux.org
Jump to: navigation, search
(Replaced content with "Move to https://elinux.org/Jetson/l4t/Camera_BringUp")
(Tag: Replaced)
 
(28 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Get Prepared ==
+
Move to https://elinux.org/Jetson/l4t/Camera_BringUp
* Please read through "Camera Development" section in https://developer.nvidia.com/embedded/dlc/l4t-documentation-28-1
 
== FAQ ==
 
=== Tips for debugging ===
 
 
 
'''TX1'''
 
* if you saw below error message
 
tegra-vi4 15700000.vi: PXL_SOF syncpt timeout! err = -11
 
 
 
* please check below 4 items in your sensor device tree, these should follow the settings in your sensor datasheet
 
                                mode0 {
 
                                        cil_settletime = "0";
 
                                        active_w = "1920";
 
                                        active_h = "1080";
 
                                        embedded_metadata_height = "1";
 
 
 
* if you saw below error message
 
video4linux video0: MW_ACK_DONE syncpoint time out!
 
 
 
* Enable the csi debug message from below command, and use v4l2-ctl to verify the driver first.
 
sudo su
 
cd /sys/kernel/debug/dynamic_debug/
 
echo file csi2_fops.c +p > control
 
 
 
v4l2-ctl -d /dev/video0 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=3
 
 
 
* please check below
 
please review the configuration of "line_length" in sensor driver
 
try to increase the delay between video lines data send via CSI
 
review the sensor datasheet to check the settings of FPS range
 
 
 
 
 
 
 
 
 
'''TX2'''
 
* if you saw below message it could be the sensor output embedded data line but DT didn't declare embedded_metadata_height or it value is 0
 
arm-smmu 12000000.iommu: Unhandled context fault: iova=0x00000000, fsynr=0x200011, cb=19, sid=4(0x4 - VI), pgd=0, pud=0, pmd=0, pte=0
 
 
 
<br />
 
=== Steps to enable more debug messages ===
 
* To enable trace for more information
 
echo 1 > /sys/kernel/debug/tracing/tracing_on
 
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
 
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
 
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
 
echo 2 > /sys/kernel/debug/camrtc/log-level
 
echo > /sys/kernel/debug/tracing/trace
 
cat /sys/kernel/debug/tracing/trace
 
 
 
* if you saw below error message from the trace
 
It could be CRC error at frame end package. Please contact with sensor vendor to check the CRC header.
 
    kworker/0:1-2059  [000] ...1  434.733650: rtcpu_vinotify_handle_msg: tstamp:13948014423 tag:CSIMUX_FRAME channel:0x00 frame:2 vi_tstamp:1063112012 data:0x00400060
 
    kworker/0:1-2059  [000] ...1  434.733654: rtcpu_vinotify_handle_msg: tstamp:13949051348 tag:CSIMUX_FRAME channel:0x00 frame:3 vi_tstamp:1064148939 data:0x00400060
 
 
 
* if you saw below error message from the trace
 
It could be the pix_clk_hz in DT too small cause the ISP can't handle the input.
 
    kworker/5:2-248 [005] ...1 297.951130: rtcpu_vinotify_handle_msg: tstamp:9663302491 tag:CSIMUX_FRAME channel:0x00 frame:13 vi_tstamp:1073367484 data:0x00400062
 
    kworker/5:2-248 [005] ...1 297.951133: rtcpu_vinotify_handle_msg: tstamp:9663324801 tag:ISPBUF_FS channel:0x00 frame:14 vi_tstamp:1073389804 data:0x00000000
 
    kworker/5:2-248 [005] ...1 297.951133: rtcpu_vinotify_handle_msg: tstamp:9663335039 tag:CHANSEL_PXL_SOF channel:0x00 frame:14 vi_tstamp:1073400039 data:0x00000001
 
    kworker/5:2-248 [005] ...1 297.951134: rtcpu_vinotify_handle_msg: tstamp:9664344311 tag:CHANSEL_SHORT_FRAME channel:0x04 frame:14 vi_tstamp:1074409154 data:0x00000001
 
    kworker/5:2-248 [005] ...1 297.951135: rtcpu_vinotify_handle_msg: tstamp:9664344499 tag:ISPBUF_FE channel:0x00 frame:14 vi_tstamp:1074409155 data:0x00000000
 
OR
 
    kworker/5:3-1359  [005] ...1  253.671469: rtcpu_vinotify_handle_msg: tstamp:8279208283 tag:CSIMUX_FRAME channel:0x03 frame:1276 vi_tstamp:3984240577 data:0x000004a2
 
    kworker/5:3-1359  [005] ...1  253.671476: rtcpu_vinotify_handle_msg: tstamp:8279969727 tag:CHANSEL_PXL_SOF channel:0x00 frame:12340 vi_tstamp:3985001693 data:0x00000001
 
    kworker/5:3-1359  [005] ...1  253.671478: rtcpu_vinotify_handle_msg: tstamp:8279969890 tag:ISPBUF_FIFO_OVERFLOW channel:0x00 frame:12340 vi_tstamp:3985001981 data:0x00000000
 
    kworker/5:3-1359  [005] ...1  253.671481: rtcpu_vinotify_handle_msg: tstamp:8279970411 tag:CHANSEL_FAULT channel:0x00 frame:12340 vi_tstamp:3985001998 data:0x00000100
 
* if you saw below error message from the trace
 
Lose the FE package cause the FS_FAULT
 
    kworker/4:0-30 [004] ...1 241.772647: rtcpu_vinotify_handle_msg: tstamp:7868673094 tag:CHANSEL_PXL_EOF channel:0x00 frame:1 vi_tstamp:3573705283 data:0x08ad0002
 
    kworker/4:0-30 [004] ...1 241.772651: rtcpu_vinotify_handle_msg: tstamp:7868711648 tag:CSIMUX_FRAME channel:0x00 frame:1 vi_tstamp:3573743671 data:0x000000a0
 
    kworker/4:0-30 [004] ...1 241.772656: rtcpu_vinotify_handle_msg: tstamp:7868712008 tag:ATOMP_FE channel:0x00 frame:1 vi_tstamp:3573743672 data:0x00000000
 
 
 
* To enable logs from user-space for more details
 
sudo su
 
kill the process of argus_daemon or nvcamera-daemon
 
export enableCamPclLogs=5
 
export enableCamScfLogs=5
 
/usr/sbin/argus_daemon      option for argus
 
/usr/sbin/nvcamera-daemon  option for gst-launch
 
 
 
launch camera from another console
 

Latest revision as of 01:13, 2 June 2021