When we did stress testing, a kernel panic error occurred.
==Loop operation :
1,Using V4L2 API Open camera video stream(ioctl(camera_ctx.fd, VIDIOC_DQBUF, &bufferinfo),
and displayed via OpenCV API
2,reboot system
according to your description, it seems you’re using v4l2 API to fetch the camera stream.
since you’re working with Orin series, which has OEM firewall.
please check whether you’ve access to registers directly.
anyways, please see-also Topic 234321 for the approaches to disable firewall config.
I modified the two files above at the same time,then re-flash the image
BUT the error still exists, the log content is exactly the same. 0529_minicom.txt (1.4 MB)
I meet the same problem when try to access NVCSI register for debug purpose using devmem command. Jetpack 5.1.3 is used on AGX orin devkit. Could you please give some help for me to access NVCSI registers using busybox devmem tool ?
since you’re working with Orin NX.
it’s using tegra234-mb2-bct-scr-p3767-0000.dts as SCR config, and tegra234-mb2-bct-scr-p3701-0000-override.dts as override files.
so, you should only revise the override file for adding CBB_FIREWALL settings.
as you may know… it’s initrd to generate the image locally and then flashing the target.
you should re-generate the image again for flashing the target.
Are the modifications to the above two files correct?
I also have a question. Since these two dts files are in the bootloader directory,
they will not be compiled into dtb files, right? Why do we need to re-generate the image?
what’s your actual use-case?
you should only updating below three if you would like to configure OEM firewall to access NVCSI registers,
for instance, reg@4673 { /* CBB_CENTRAL_CBB_FIREWALL_NVCSI_ENGINE_BLF, READ_CTL */ reg@4674 { /* CBB_CENTRAL_CBB_FIREWALL_NVCSI_ENGINE_BLF, WRITE_CTL */ reg@4675 { /* CBB_CENTRAL_CBB_FIREWALL_NVCSI_ENGINE_BLF, CTL_SETTING */
since you’re working with initrd script.
it’s the image under… $OUT/Linux_for_Tegra/tools/kernel_flash/images/ that flash to your target actually.