Camera Not working

Dear Nvidia Team

I am using 32.7.5 Kernel and BSP in our NX jestson board
Camera is connected to MIPI interface to the board …
i am getting below error

root@RAPSODO_V3PRO_5055:~# v4l2-ctl --stream-mmap --stream-count=100 --set-ctrl bypass_mode=0 -d /dev/video0
VIDIOC_STREAMON: failed: Invalid argument
root@RAPSODO_V3PRO_5055:~# v4l2-ctl --stream-count=100 --set-ctrl bypass_mode=0 -d /dev/video0
root@RAPSODO_V3PRO_5055:~#

Not sure how to take camera image

hello nitin.gupta981,

may I double check which Jetson platform you’re using?
this should not Orin NX platform since r32.7.5 release version do not support it.

besides, may I know which camera module you’re working with.
please check kernel init logs ($ dmesg > klogs.txt) to ensure it’s register to system /dev/video0 correctly.

Hi Jerry
Thank you for reply … We are using below FBGA code it is Jetson Xavier NX


klog.txt (92.6 KB)

attached is media-ctl -p -d /dev/media0 command output
media0-log.txt (2.3 KB)

hello nitin.gupta981,

is this your camera’s i2c address?
there’re i2c no acknowledge failures reported, which usually caused by regulator settings.
please check you’ve given power-supply to your device correctly.

[   54.522644] tegra-i2c 31e0000.i2c: no acknowledge from address 0x55
[   60.527535] tegra-i2c 31e0000.i2c: no acknowledge from address 0x55
[   66.532716] tegra-i2c 31e0000.i2c: no acknowledge from address 0x55
[   72.538151] tegra-i2c 31e0000.i2c: no acknowledge from address 0x55

hello Jerry

Thank you for checking the log. actually imx camera is not directly connected to NX . please find the below diagram

Note :- We recently got the D8CSC Card from our vendor which we say 302 card…

I Prepared the BSP 32.7.6 for 302 card since we can not flash our old BSP 32.4.4 in 302 card .
32.4.4 BSP we can flash 301 card which we are using now and camera is working there .

For Isolating I tried 301 + 32.7.6 in which camera is not working also.
So I can say that due to some package there is issue , Not due to Hardware or NX card.

While Moving to BSP I keep my kernel source same so basically, we are not using kernel from BSP source.
Please refer the below link where i described my process when we were moving from 300 to 301 but we did not faced any issue that time… since below error was coming so I am not chnging the kernel and do not want to increasing the Scope of QA Team.

Nvpmodel hang and Many ERROR in nvgpu - Jetson & Embedded Systems / Jetson Xavier NX - NVIDIA Developer Forums

Hi Jerry

Good Morning ,

I2c Address 0x55 does not belong to Camera .

After replacing the below 4 binary camera from 32.4.4 it is working …

but i am still not sure why V4l2 now its not giving error but hanging and printing this.
I need ti check how application is making it work not sure if they are using gstreamer.

If you have some command to confirm the capture mode it will be very helpful.

232.094526] tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
[ 232.097808] tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel

hello nitin.gupta981,

please running below to check the sensor support formats,$ v4l2-ctl -d /dev/video0 --list-formats-ext
after that, please try assign the sensor supported format into v4l pipeline for test camera stream,
for instance,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1080,pixelformat=RG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

Hi Jerry

Please find the attached command which i tried and still dont see any output

camera-debugging.txt (3.0 KB)

hello nitin.gupta981,

please also configured v4l2 pipeline to sensor supported resolution, 1472x1080
# v4l2-ctl -d /dev/video0 --set-fmt-video=width=1472,height=1080,pixelformat=BG10 --set-ctrl bypass_mode=0 --stream-mmap --stream-count=100

according to the logs…
[ 7352.087252] tegra194-vi5 15c10000.vi: no reply from camera processor
[ 7352.087453] tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
it’s timeout failure, which usually caused by VI did not receive frame packet.
please refer to Sensor Pixel Clock section to examine your clock rate settings, it must be set correctly to avoid potential issues.

BTW,
you may also test with below commands to boost all the clocks.
for instance,

sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.