Video output is not getting from Video node

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello,

I am using the jetpack 5.1.2 and bsp version of L4T 35.4.1.

After successfully creating the video node, I am facing issue where the video sometimes works(clearly video is coming), but other times it does not.

It is giving NULL VI error in dmesg. I have attached the dmesg and the debug logs below.

kworker/3:3-520 [003] … 922.826162: rtcpu_vinotify_event: tstamp:29561718191 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:945965440160 data:0x379e300010000000
kworker/3:3-520 [003] … 922.826163: rtcpu_vinotify_event: tstamp:29561718466 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:945965446624 data:0x0000000031000001
kworker/3:3-520 [003] … 922.826164: rtcpu_vinotify_event: tstamp:29561718802 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:945965522144 data:0x379e2d0010000000
kworker/3:3-520 [003] … 922.826164: rtcpu_vinotify_event: tstamp:29561719069 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:945965528672 data:0x0000000031000002

debug_no_video.txt (753 Bytes)
dmesg_no_video.txt (718 Bytes)

Could you please tell me why we are facing these errors?

Regards,
Kamalesh

2

Hi @kamalesh1

From your VI trace, it seems no video is detected on the Jetson system. Can you make sure your sensor is sending video? I suggest if the sensor has status registers about streaming or a frame-counter.

Just to make sure, when you say “sometimes works”, are you getting a correct image?
Which command are you using to stream?

Regards,

Enrique Ramirez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

3

Hi,

Just to make sure, when you say “sometimes works”, are you getting a correct image?
Yes after multiple rebooting, I have getting proper video output.

Which command are you using to stream?
I am using gstreamer ordinary video command:-
gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=UYVY ! videoconvert ! xvimagesink.

If there is no signal receive from sensor means, how i am receiving video. I am bit confused.

What may be the reason for this?

Regards,
Kamalesh.

5

Hi,
It may be an issue in the camera sensor. It does not generate valid frame data in each launch. If the camera is stable, the command should be run successfully for each time.

6

DaneLLL is right, if you are able to capture correct images the driver seems to be configured correctly. However, it looks to be that the camera is not stable when you can’t get video. That’s why you should check camera registers or check the signals when you are not able to capture. According to your VI trace, when that happens, the system is not detecting any data from the camera.

7

Hi DaneLLL,

Earlier I tried with L4T 32.7.5 version, here camera is working for all attempt( I tried multiple times, It is working without any intermediate issues).

In this jetpack 5 only, it is behaving like this. what may be the reason?

We can’t point this camera sensor right?

Regards,
Kamalesh

8

Hi,

Is there any updates? Please let me know.

Regards,
Kamalesh

9

Hi,
Would suggest try Jetpack 5.1.4. The rtcpu fw is updated in later versions and may help this use-case.

10

Hi DaneLLL,

I have identified the condition under which the camera works correctly. The camera functions properly when the temperature exceeds 70°C. However, it does not work before reaching 70°C (typically, the camera starts working after the module heats up).
Would you still like me to check with JetPack 5.1.4?

Regards,
Kamalesh

11

hello kamalesh1,

please follow below steps to enable VI tracing logs for gathering more details.
for instance,

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

besides, there’re camera bug fixes according to Jetson Linux 35.6.0 Release Notes.
if that’s possible, please moving to the latest JP-5 (i.e. JetPack 5.1.4) release version to verify this issue again,
thanks

12

Hi Chang,

I have tried this trace enabling and given the response at my first comment.

I will try the latest JP-5 version and let you know.

Regards,
Kamalesh

13

Hi,

Update: I have tested with the latest JetPack 5.1.4 and observed the following behavior:

The camera starts working after the temperature exceeds 44°C. However, when I cooled the module down to 38°C and checked the camera, it continued to work. But, once the temperature dropped below 36°C, the camera stopped working. From this point, I turned off the cooling fan, and as the temperature increased back to 44°C, I tried using the camera between 36°C and 44°C, but it didn’t work. Only when the temperature exceeded 44°C did the camera start functioning again.

What may be the reason for this behaviour?

Regards,
Kamalesh