How to see dev_dbg logs on dmesg

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hi all, I want to know how to see the logs that are send by deb_dbg function. For now, I can only see the dev_err levels log.

3

Enable it by like below command.

sudo su
echo file ov5693.c +p > /sys/kernel/debug/dynamic_debug/control
4

Hi ShaneCCC
I have followed your instructions, the results listed below
(I am using the imx219 sensor right now. )

sudo su echo file imx219.c +p >/sys/kernel/debug/dynamic_debug/control

bash: /sys/kernel/debug/dynamic_debug/control: Permission denied
5

sudo su input the enter key then do the echo command.

6

I have already done this. But when I type “dmesg -l7 | grep imx219”, the results are still dev_err’s, If I want to track the flow of the camera module’s probe function, what should I do ?

I have seen the video you provided for developers, in which after typing the dmesg | grep -i imx185 commands, “probing v4l2 sensor at addr 0x1a …” appears

however my console shows me that after I type dmesg | grep -i imx219:

[    2.093201] imx219 9-0010: tegracam sensor driver:imx219_v2.0.6
[    2.116810] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[    2.116851] imx219 9-0010: board setup failed
[    2.116973] imx219: probe of 9-0010 failed with error -121
[    2.117448] imx219 10-0010: tegracam sensor driver:imx219_v2.0.6
[    3.132969] tegra194-vi5 15c10000.vi: subdev imx219 10-0010 bound
7

Your sensor board have problem that didn’t fun to the register video node to show some message.
Looks like HW problem cause i2c failed access the sensor.

[ 2.116810] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 2.116851] imx219 9-0010: board setup failed

8

Error it is, but it can still capture pictures using nvgstcapture or run the Jetson Linux Multimedia API Reference: 09_camera_jpeg_capture you provided.

So back to the problems before. Is it possible for me to track the flow of camera module probe with the errors you mentioned above? If not, what’s your suggestions?

9

That’s impossible not working. If you don’t see any message that could be the function didn’t be called.
If you can rebuild the driver you can add #define DEBUG in the file header to enable the dev_dbg().

10

Understand, I will try what you said.

Thank you for your kind explainations!