In version R35.4.1, Jetson orin nx was used to fit the imx728-gmsl2 camera, and the argus_camera could not preview the image

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

After loading the driver, I used the v4l2 command to print the frame rate, which was fine. As shown in the picture below:

image
image759×284 6.89 KB

When I use argus_camera to preview the camera, I get a black screen. I looked at dmesg and nothing went wrong. View the tarce log as follows:

     kworker/2:0-25      [002] ....   722.739980: rtcpu_nvcsi_intr: tstamp:23096988950 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739980: rtcpu_nvcsi_intr: tstamp:23096988950 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739980: rtcpu_nvcsi_intr: tstamp:23096989758 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739980: rtcpu_nvcsi_intr: tstamp:23096989758 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739980: rtcpu_nvcsi_intr: tstamp:23096989758 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096989758 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096990567 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096990567 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096990567 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096990567 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739981: rtcpu_nvcsi_intr: tstamp:23096991374 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739982: rtcpu_nvcsi_intr: tstamp:23096991374 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739982: rtcpu_nvcsi_intr: tstamp:23096991374 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739983: rtcpu_nvcsi_intr: tstamp:23096991374 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739983: rtcpu_nvcsi_intr: tstamp:23096992184 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739983: rtcpu_nvcsi_intr: tstamp:23096992184 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739983: rtcpu_nvcsi_intr: tstamp:23096992184 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739984: rtcpu_nvcsi_intr: tstamp:23096992184 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739984: rtcpu_nvcsi_intr: tstamp:23096992993 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739984: rtcpu_nvcsi_intr: tstamp:23096992993 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739984: rtcpu_nvcsi_intr: tstamp:23096992993 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739985: rtcpu_nvcsi_intr: tstamp:23096992993 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739985: rtcpu_nvcsi_intr: tstamp:23096993797 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739985: rtcpu_nvcsi_intr: tstamp:23096993797 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739985: rtcpu_nvcsi_intr: tstamp:23096993797 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739985: rtcpu_nvcsi_intr: tstamp:23096993797 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739986: rtcpu_nvcsi_intr: tstamp:23096994626 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739986: rtcpu_nvcsi_intr: tstamp:23096994626 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739986: rtcpu_nvcsi_intr: tstamp:23096994626 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739986: rtcpu_nvcsi_intr: tstamp:23096994626 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739986: rtcpu_nvcsi_intr: tstamp:23096995429 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739987: rtcpu_nvcsi_intr: tstamp:23096995429 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739987: rtcpu_nvcsi_intr: tstamp:23096995429 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:0 st:0 vc:0 status:0x00000044
     kworker/2:0-25      [002] ....   722.739987: rtcpu_nvcsi_intr: tstamp:23096995429 class:CORRECTABLE_ERR type:PHY_INTR phy:1 cil:1 st:0 vc:0 status:0x00000044

trace.txt (37.5 KB)

hope I can get your help. Thank you.

3

Possible the CID function have incorrect REG write cause the problem.
Modify the sensor control function to dummy function to confirm.

Thanks

4

What am I supposed to do? How do I know where the problem is?

5

Modify the sensor control function in sensor driver to dummy function.

7

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