Hi There,
I’m trying to migrate camera driver from TX2 to Xavier NX. We’re using the same sensor (IMX385) and JetPack (4.4.1) for both SOMs. I didn’t change anything in the deriver but modified the device tree to match the new carrier board.
I was able to set camera parameter using v4l2-ctrl, however I was not able to stream anything.
dmesg shows
[ 23.130545] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 23.130722] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 23.130883] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 23.139535] tegra194-vi5 15c10000.vi: unable to find linked csi subdev
[ 23.139699] tegra194-vi5 15c10000.vi: fatal: error recovery failed
I searched around the forum and found that this could be tegra194-vi4 to tegra194-vi5 issue, but I’m not so sure how to debug and what are the required change for moving from vi4 to vi5. I also got this fatal error while trying to do v4l2 streaming.
[10132.120720] >>>>> imx385_power_on
[10132.125873] tegra194-vi5 15c10000.vi: ================= START STATUS =================
[10132.125906] tegra194-vi5 15c10000.vi: ================== END STATUS ==================
[10132.127468] >>>>> imx385_set_group_hold
[10132.127474] >>>>> imx385_write_reg
[10132.128658] >>>>> imx385_set_group_hold
[10132.128665] >>>>> imx385_write_reg
[10132.129097] >>>>> imx385_set_group_hold
[10132.129102] >>>>> imx385_write_reg
[10132.129487] >>>>> imx385_set_group_hold
[10132.129492] >>>>> imx385_write_reg
[10132.130046] >>>>> imx385_set_group_hold
[10132.130052] >>>>> imx385_write_reg
[10132.130442] >>>>> imx385_set_group_hold
[10132.130447] >>>>> imx385_write_reg
[10132.131281] >>>>> imx385_set_group_hold
[10132.131287] >>>>> imx385_write_reg
[10132.132287] >>>>> imx385_set_group_hold
[10132.132293] >>>>> imx385_write_reg
[10132.132781] >>>>> imx385_set_group_hold
[10132.132786] >>>>> imx385_write_reg
[10132.142834] >>>>> imx385_set_group_hold
[10132.142840] >>>>> imx385_write_reg
[10132.143403] >>>>> imx385_set_group_hold
[10132.143408] >>>>> imx385_write_reg
[10132.143879] >>>>> imx385_power_off
[10280.022915] >>>>> imx385_power_on
[10280.030639] >>>>> imx385_power_off
[10505.664859] >>>>> imx385_power_on
[10505.694633] >>>>> imx385_set_mode
[10505.694639] >>>>> imx385_write_table
[10505.711979] >>>> imx385_start_streaming
[10505.711986] >>>>> imx385_write_table
[10505.724027] [RCE] Configuring VI GoS.
[10505.724045] [RCE] VM GOS[#0] addr=0xc2100000
[10505.724059] [RCE] VM GOS[#1] addr=0xc2101000
[10505.724101] [RCE] VM GOS[#2] addr=0xc2102000
[10505.724114] [RCE] VM GOS[#3] addr=0xc2103000
[10505.724128] [RCE] VM GOS[#4] addr=0xc2104000
[10505.724140] [RCE] VM GOS[#5] addr=0xc2105000
[10505.724156] [RCE] vi5_hwinit: firmware CL2018101701 protocol version 2.2
[10505.724202] [RCE] VI GOS[#0] set to VM GOS[4] base 0xc2104000
[10508.283968] tegra194-vi5 15c10000.vi: no reply from camera processor
[10508.284149] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[10508.284302] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[10508.289288] tegra194-vi5 15c10000.vi: unable to find linked csi subdev
[10508.289440] tegra194-vi5 15c10000.vi: fatal: error recovery failed
[10533.799153] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[10533.799321] Mem abort info:
[10533.799379] ESR = 0x96000005
[10533.799437] Exception class = DABT (current EL), IL = 32 bits
[10533.799541] SET = 0, FnV = 0
[10533.799600] EA = 0, S1PTW = 0
[10533.799655] Data abort info:
[10533.800517] ISV = 0, ISS = 0x00000005
[10533.800604] CM = 0, WnR = 0
[10533.800679] user pgtable: 4k pages, 39-bit VAs, pgd = ffffffc1d9209000
[10533.800794] [0000000000000000] *pgd=0000000000000000, *pud=0000000000000000
[10533.800955] Internal error: Oops: 96000005 [#1] PREEMPT SMP
[10533.801064] Modules linked in: hid_logitech_hidpp hid_logitech_dj bnep fuse zram overlay spidev nvgpu bluedroid_pm ip_tables x_tables
[10533.801403] CPU: 1 PID: 12040 Comm: v4l2-ctl Not tainted 4.9.140-tegra #5
[10533.801522] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[10533.801638] task: ffffffc1988ed400 task.stack: ffffffc161d74000
[10533.801779] PC is at exit_creds+0x2c/0x78
[10533.802075] LR is at __put_task_struct+0x4c/0x140
[10533.804629] pc : [<ffffff80080deefc>] lr : [<ffffff80080b012c>] pstate: 60400045
[10533.811977] sp : ffffffc161d77a10
[10533.815130] x29: ffffffc161d77a10 x28: 0000000000000008
[10533.820912] x27: ffffff8008f72000 x26: ffffffc161d77de8
[10533.826587] x25: ffffffc1c4860768 x24: ffffffc1e08e1018
[10533.831935] x23: 0000000000000001 x22: ffffffc1e08ae018
[10533.837099] x21: ffffffc1f5e12a30 x20: 0000000000000000
[10533.842174] x19: ffffffc1f5e12a00 x18: 0000000000000000
[10533.848200] x17: 0000000000031626 x16: 0000000000000000
[10533.853722] x15: 00000000000003a5 x14: 00000000000c3692
[10533.859664] x13: 0000000000000387 x12: 071c71c71c71c71c
[10533.864924] x11: 000000000000000b x10: 0000000000000a10
[10533.870700] x9 : ffffffc161d77860 x8 : ffffffc1988ede70
[10533.876472] x7 : fefefeff646c606d x6 : 0000004cbac20005
[10533.882237] x5 : 0000000000000800 x4 : 0000000000000000
[10533.887322] x3 : 00000000000000b4 x2 : 0000000000000000
[10533.892663] x1 : 0000000000000000 x0 : 00000000ffffffff
[10533.899405] Process v4l2-ctl (pid: 12040, stack limit = 0xffffffc161d74000)
[10533.906302] Call trace:
[10533.908670] [<ffffff80080deefc>] exit_creds+0x2c/0x78
[10533.913221] [<ffffff80080b012c>] __put_task_struct+0x4c/0x140
[10533.918560] [<ffffff80080dc9bc>] kthread_stop+0x1e4/0x1e8
[10533.923638] [<ffffff8008b4c310>] vi5_channel_stop_kthreads+0x40/0x58
[10533.929760] [<ffffff8008b4c3b4>] vi5_channel_stop_streaming+0x8c/0xa8
[10533.935885] [<ffffff8008b3ed1c>] tegra_channel_stop_streaming+0x34/0x48
[10533.942354] [<ffffff8008b3702c>] __vb2_queue_cancel+0x34/0x188
[10533.947697] [<ffffff8008b38554>] vb2_core_queue_release+0x2c/0x58
[10533.953818] [<ffffff8008b3abd4>] _vb2_fop_release+0x84/0xa0
[10533.959155] [<ffffff8008b40694>] tegra_channel_close+0x64/0x140
[10533.964846] [<ffffff8008b14188>] v4l2_release+0x48/0xa0
[10533.970008] [<ffffff800825ebd0>] __fput+0x90/0x1d0
[10533.974560] [<ffffff800825ed88>] ____fput+0x20/0x30
[10533.979633] [<ffffff80080d9b74>] task_work_run+0xbc/0xd8
[10533.984886] [<ffffff80080b95f4>] do_exit+0x2c4/0xa08
[10533.990041] [<ffffff80080b9dc8>] do_group_exit+0x40/0xa8
[10533.995122] [<ffffff80080c76c4>] get_signal+0x26c/0x578
[10534.000545] [<ffffff800808b150>] do_signal+0x130/0x500
[10534.005792] [<ffffff800808b698>] do_notify_resume+0x90/0xb0
[10534.011394] [<ffffff800808379c>] work_pending+0x8/0x10
[10534.016213] ---[ end trace 5ae24e4af72168a3 ]---
[10534.035435] Fixing recursive fault but reboot is needed!
Thank you so much for your help!
hello jdluckyday,
you may dig into the root cause,
BTW, please also refer to Topic 187824 to apply the fix of NULL pointer dereference in kernel.
thanks
Thanks for checking!
I searched around and found my dmesg is very similar to topic 126439. But those patches are already applied in R32.4.3.
Could this due to some changes from VI4 to VI5? Is there a guide on what needs to be done when migrating driver from TX2 to Xavier? Thanks!
hello jdluckyday,
please check developer guide, Verifying the V4L2 Sensor Driver. you may check your sensor driver by running a v4l2-compliance test.
in addition, please review your sensor device tree, you may also compare it with Xavier series device trees.
thanks
BTW, please see-also V4L2 Sensor Driver Development Tutorial.
this video will dive deep into the steps of writing a complete V4L2 compliant driver for an image sensor to connect to the NVIDIA Jetson platform over MIPI CSI-2.
Hi Jerry,
Thanks for the Tutorial! I found that I made a mistake in the Port Binding session (thanks sudo media-ctl -p -d /dev/media0).
After fixing the error, v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=360 -d /dev/video1 shows some frames.
However, dmesg still shows some error
[ 59.123928] >>>>> imx385_power_on
[ 59.123940] >>>>> imx385_power_on reset_gpio 0
[ 59.124012] >>>>> imx385_power_on reset_gpio 1
[ 59.142235] >>>>> imx385_set_mode
[ 59.142244] >>>>> imx385_write_table
[ 59.147822] [RCE] vi5_hwinit: firmware CL2018101701 protocol version 2.2
[ 59.162789] >>>> imx385_start_streaming
[ 59.162795] >>>>> imx385_write_table
[ 59.297095] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 32, err_data 512
[ 62.039749] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 62.039932] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 62.040100] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 62.055466] tegra-capture-ivc ivc-bc00000.rtcpu:ivccontrol@3: No callback found for msg id: 0x39
[ 62.055656] tegra-capture-ivc ivc-bc00000.rtcpu:ivccontrol@3: No callback found for msg id: 0x41
[ 62.055869] tegra-capture-ivc ivc-bc00000.rtcpu:ivccontrol@3: No callback found for msg id: 0x37
[ 62.056041] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 62.056369] tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 32, err_data 1060
[ 65.080332] >>>> imx385_stop_streaming
[ 65.080340] >>>>> imx385_write_table
[ 65.089958] >>>>> imx385_power_off
[ 66.977875] >>>>> imx385_power_on
[ 66.977886] >>>>> imx385_power_on reset_gpio 0
[ 66.977952] >>>>> imx385_power_on reset_gpio 1
[ 66.991118] >>>>> imx385_set_mode
[ 66.991127] >>>>> imx385_write_table
[ 67.010237] >>>> imx385_start_streaming
[ 67.010265] >>>>> imx385_write_table
[ 67.102872] tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 32, err_data 512
[ 69.344500] tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 32, err_data 1188
[ 70.627808] tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 112, err_data 14681700
[ 71.811105] tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 112, err_data 14681700
[ 74.328091] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 74.328276] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
[ 74.328418] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 74.344565] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel
[ 77.361036] >>>> imx385_stop_streaming
[ 77.361044] >>>>> imx385_write_table
[ 77.372846] >>>>> imx385_power_off
I think I saw this error in the forum before.
hello jdluckyday,
did those kernel failure reported when you running v4l2-ctl utility?
according to the logs…
[ 59.162789] >>>> imx385_start_streaming
[ 59.162795] >>>>> imx385_write_table
[ 59.297095] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 32, err_data 512
[ 62.039749] tegra194-vi5 15c10000.vi: no reply from camera processor
the error flags=32, it means CAPTURE_STATUS_FLAG_ERROR_CSIMUX_FRAME. and, the err_data shows there’s FE_FRAME_ID_FAULT
since the failure is due to frame-end, could you please examine your signals to ensure that.
please also examine the sensor format dumps, i.e. $ v4l2-ctl -d /dev/video0 --list-formats-ext
you should assign the exactly same width, height, pixel formats into the v4l command-line.
Hi Jerry,
There is no error when doing v4l2-ctl -d /dev/video1 --list-formats-extand the replay is correct.
“Could you please examine your signals to ensure that?” Means to check the signal from camera hardware? or register table for camera driver?
This seems only happen for the first two frames.
hello jdluckyday,
as you can see… tegra194-vi5 15c10000.vi: corr_err: discarding frame 0, flags: 32, err_data 512. VI driver will discard invalid capture frames.
please check this error due to register programming timing, please check whether you still seeing the same failure by programming few registers.
besides,
there’s device tree property to tune the hardware configuration,
such as… set_mode_delay_ms, please try adding this into sensor mode to configure the maximum wait time for the first frame after capture starts, the unit is in milliseconds. or, please try the other options by using post_crop_frame_drop, to drop the frames after applying sensor crop settings.
see-also developer guide, Device Properties which describes the device tree node properties for the V4L2 sensor device.
thanks
Hi Jerry,
Thanks for the info! I have already tried to add set_mode_delay_ms=30000 to the device tree and there is no effect at all. Didn’t feel any delay and still saw the error message.
This post seems show no effect by adding set_mode_delay_ms as well. I’m currently testing on # R32 (release), REVISION: 4.3, GCID: 21589087, BOARD: t186ref, EABI: aarch64, DATE: Fri Jun 26 04:34:27 UTC 2020. Do I need to upgrade to Jetpack4.6 and try? Thanks!
hello jdluckyday,
this looks like sensor bring-up issue, I would suspect you’ll see the same failure by upgrading to Jetpack-4.6 release version.
is this always happened in the coming 1st, 2nd camera frames? if yes, you may consider dropping those two for verification, thanks
Hi Jerry,
Yes, this always happened in the 1st and 2nd frames. And argus_camera doesn’t work because of this. Is there a way to skip 1st, 2nd frames in the camera driver?
Hi Jerry,
I did a little bit more tests and found boosting the clock removed all the errors during 4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=720 -d /dev/video1 test.
However argus_camera still fails with tegra194-vi5 15c10000.vi: no reply from camera processor and tegra194-vi5 15c10000.vi: vi capture get status failed message.
[ 493.379834] >>>>> imx385_write_reg
[ 494.870234] fence timeout on [ffffffc1662643c0] after 1500ms
[ 494.870246] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 494.870251] name=[nvhost_sync:36], current value=13 waiting value=14
[ 494.870266] ---- mlocks ----
[ 494.870311] ---- syncpts ----
[ 494.870324] id 2 (disp_a) min 1052 max 1052 refs 1 (previous client : )
[ 494.870329] id 3 (disp_b) min 3 max 3 refs 1 (previous client : )
[ 494.870334] id 4 (disp_c) min 3 max 3 refs 1 (previous client : )
[ 494.870344] id 8 (vblank0) min 8478 max -6 refs 1 (previous client : )
[ 494.870361] id 18 (gv11b_511) min 13705 max 13705 refs 1 (previous client : )
[ 494.870366] id 19 (gv11b_510) min 14 max 14 refs 1 (previous client : )
[ 494.870371] id 20 (gv11b_509) min 2758 max 2758 refs 1 (previous client : gv11b_509)
[ 494.870410] id 29 (gv11b_507_user) min 23 max 0 refs 1 (previous client : )
[ 494.870413] tegra194-vi5 15c10000.vi: vi capture get status failed
[ 494.870539] id 36 (progress) min 13 max 13 refs 1 (previous client : progress)
[ 494.870546] id 37 (embdata) min 6 max 6 refs 1 (previous client : embdata)
[ 494.870553] id 38 (15340000.vic_nvargus-daemon_0) min 6 max 6 refs 1 (previous client : gv11b_501)
[ 494.870560] id 39 (gv11b_502) min 3 max 3 refs 1 (previous client : 15340000.vic_nvargus-daemon_0)
[ 494.870567] id 40 (gv11b_503) min 9 max 9 refs 1 (previous client : gv11b_500)
[ 494.870574] id 42 (gv11b_500) min 3 max 3 refs 1 (previous client : )
[ 494.870677] id 43 (gv11b_501) min 3 max 3 refs 1 (previous client : )
[ 494.870688] id 44 (gv11b_499) min 3 max 3 refs 1 (previous client : )
[ 494.870695] id 45 (gv11b_498) min 3 max 3 refs 1 (previous client : )
[ 494.871512] ---- channels ----
[ 494.871545]
channel 2 - 15820000.se
[ 494.871550] NvHost basic channel registers:
[ 494.871557] CMDFIFO_STAT_0: 00002040
[ 494.871563] CMDFIFO_RDATA_0: 10495831
[ 494.871571] CMDP_OFFSET_0: 00000000
[ 494.871577] CMDP_CLASS_0: 00000000
[ 494.871583] CHANNELSTAT_0: 00000000
[ 494.871587] The CDMA sync queue is empty.
Thank you!
hello jdluckyday,
it might be the pixel clock configuration issue, please review your device tree settings, since Argus looking for it to enable the clocks.
please see-also Sensor Pixel Clock session for the formulas to examine your sensor pixel clock rate.
thanks
Hi Jerry,
Thanks for getting back to me! The Pixel_clk_hz is correct. 2200 x 1125 and 120 FPS so the pixel_clk_hz = 2200x1125x120.
The sensor was working good on TX2 with the same device tree parameters. I’m using mclk_khz=“37125” and the sensor use an external clk.
Please take a look at the attached device tree. Thanks!
imx385_cam1: imx385_e@1a {
compatible = "nvidia,imx385";
reg = <0x1a>;
devnode = "video1";
/* Physical dimensions of sensor */
physical_w = "15.0";
physical_h = "12.5";
sensor_model ="imx385";
/* Define any required hw resources needed by driver */
/* ie. clocks, io pins, power sources */
// avdd-reg = "vana";
// iovdd-reg = "vif";
// dvdd-reg = "vdig";
/* Defines number of frames to be dropped by driver internally after applying */
/* sensor crop settings. Some sensors send corrupt frames after applying */
/* crop co-ordinates */
post_crop_frame_drop = "0";
/* if true, delay gain setting by one frame to be in sync with exposure */
delayed_gain = "true";
use_sensor_mode_id = "true";
mode0 {/*mode IMX385_MODE_1920X1080_CROP_120FPS*/
mclk_khz = "37125";
num_lanes = "4";
tegra_sinterface = "serial_e";
phy_mode = "DPHY";
discontinuous_clk = "no";
dpcm_enable = "false";
cil_settletime = "0";
dynamic_pixel_bit_depth = "10";
csi_pixel_bit_depth = "10";
mode_type = "bayer";
pixel_phase = "rggb";
active_w = "1920";
active_h = "1080";
readout_orientation = "0";
line_length = "2200";
inherent_gain = "1";
// mclk_multiplier = "80";
pix_clk_hz = "297000000";
set_mode_delay_ms = "30000";
gain_factor = "1000000";
min_gain_val = "1000000";
max_gain_val = "31000000";
step_gain_val = "1";
default_gain = "1000000";
min_hdr_ratio = "1";
max_hdr_ratio = "64";
framerate_factor = "1000000";
min_framerate = "6000000"; /* 12 */
max_framerate = "120000000"; /* 120 */
step_framerate = "1";
default_framerate = "120000000";
exposure_factor = "1000000";
min_exp_time = "37"; /* us */
max_exp_time = "166667"; /* us */
step_exp_time = "1";
default_exp_time = "8333";/* us */
embedded_metadata_height = "1";
};
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
liimx385_imx385_out1: endpoint {
port-index = <4>;
bus-width = <4>;
remote-endpoint = <&liimx385_csi_in1>;
};
};
};
hello jdluckyday,
could you please have a try with Infinite Timeout Support to make Camera service wait indefinitely for incoming frames.
Hi Jerry,
Thanks for the suggestions! I just tested it.
What does those NvPclHwGetModuleList: No module data found mean? I have only /dev/video1 connected during the test. Please see the log from nvargus-daemon. Thank you!
nvidia@localhost:~$ sudo enableCamInfiniteTimeout=1 nvargus-daemon
=== NVIDIA Libargus Camera Service (0.97.3)=== Listening for connections...===
argus_camera[7988]: Connection established (7FA15271D0)
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module0
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module1
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module2
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module3
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module4
OFParserListModules: module list: /proc/device-tree/tegra-camera-platform/modules/module5
NvPclHwGetModuleList: No module data found
NvPclHwGetModuleList: No module data found
NvPclHwGetModuleList: No module data found
NvPclHwGetModuleList: No module data found
NvPclHwGetModuleList: No module data found
NvPclHwGetModuleList: No module data found
OFParserGetVirtualDevice: NVIDIA Camera virtual enumerator not found in proc device-tree
---- imager: No override file found. ----
LSC: LSC surface is not based on full res!
---- imager: No override file found. ----
LSC: LSC surface is not based on full res!
---- imager: No override file found. ----
(NvOdmDevice) Error SymbolNotFound: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function loadModeProperties(), line 680)
(NvOdmDevice) Error SymbolNotFound: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function loadModeList(), line 535)
(NvOdmDevice) Error SymbolNotFound: (propagating from dvs/git/dirty/git-master_linux/camera-partner/imager/src/devices/V4L2SensorViCsi.cpp, function initialize(), line 123)
NvPclDriverInitializeData: Unable to initialize driver v4l2_sensor
NvPclInitializeDrivers: error: Failed to init camera sub module v4l2_sensor
NvPclStartPlatformDrivers: Failed to start module drivers
NvPclStateControllerOpen: Failed ImagerGUID 2. (error 0x30009)
NvPclOpen: PCL Open Failed. Error: 0xf
SCF: Error BadParameter: Sensor could not be opened. (in src/services/capture/CaptureServiceDeviceSensor.cpp, function getSourceFromGuid(), line 582)
SCF: Error BadParameter: (propagating from src/services/capture/CaptureService.cpp, function addSourceByGuid(), line 437)
SCF: Error BadParameter: (propagating from src/api/CameraDriver.cpp, function addSourceByIndex(), line 295)
SCF: Error BadParameter: (propagating from src/api/CameraDriver.cpp, function getSource(), line 458)
Acquiring SCF Camera device source via index 2 has failed. ---- imager: No override file found. ----
LSC: LSC surface is not based on full res!
---- imager: No override file found. ----
LSC: LSC surface is not based on full res!
---- imager: No override file found. ----
LSC: LSC surface is not based on full res!
=== argus_camera[7988]: CameraProvider initialized (0x7f9cc3e510)LSC: LSC surface is not based on full res!
LSC: LSC surface is not based on full res!
PowerServiceCore:handleRequests: timePassed = 1419
hello jdluckyday,
those Argus daemon logs said it cannot register camera devices,
did you mean you have single camera connected to the platform and it’s a front facing camera sensor?
Hi Jerry,
I have only one camera connected to the device but there are 6 cameras in the device tree.
The camera is connect to /dev/video1 and v4l2-ctl --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=360 -d /dev/video1 works ok after boosting the clock.
I ran argus_camera using argus_camera --device=1.
Does the direction/position/badge of the camera sensor matter? It’s not a front facing camera sensor.
hello jdluckyday,
it’s by default parsing rear sensor as first camera sensor. you may have a try to modify device tree to keep only single camera enabled.
also, please revise the properties as rear camera sensor for confirmation.
thanks