AD-96TOF1-EBZ Rev D Board with Jetson

Hello,

We have a AD-96TOF1-EBZ and are using the instructions from here to try and use a Jetson Nano. I'm trying to make the imshow-jetson example work.

The instructions are for rev B and rev C boards. We have a rev D board - can the rev D board work with a Jetson Nano?

Having followed the instructions the error I am getting is:

Cannot identify /dev/video0 errono:2error: No such file or directory

Are there other steps to help debug why the camera is not present?

thanks.

Parents Reply Children
  • Hi,

    same issue here, runing with latest image for Jetson Nano.

    The output of imshow-jetson is:

    I0326 16:01:44.780836 11455 sensor_enumerator_jetson.cpp:48] Looking for devices on the target: Jetson
    I0326 16:01:44.783318 11455 camera_96tof1.cpp:144] Initializing camera
    I0326 16:01:44.783391 11455 addi9036_sensor.cpp:139] Opening device
    I0326 16:01:44.783445 11455 addi9036_sensor.cpp:157] Looking for the following cards:
    I0326 16:01:44.783478 11455 addi9036_sensor.cpp:159] vi-output, addi9036 6-0064
    W0326 16:01:44.783551 11455 addi9036_sensor.cpp:173] Cannot identify /dev/video0errno: 2error: No such file or directory
    W0326 16:01:44.784117 11455 camera_96tof1.cpp:154] Failed to open device
    E0326 16:01:44.784184 11455 main.cpp:102] Could not initialize camera!
    W0326 16:01:44.785075 11455 addi9036_sensor.cpp:124] close m_implData->fd error errno: 9 error: Bad file descriptor
    W0326 16:01:44.785166 11455 addi9036_sensor.cpp:129] close m_implData->sfd error errno: 9 error: Bad file descriptor
    analog@analog-desktop:~$

    It seems the ADI module is not loaded, as in dmesg I see the IMX219?, e.g

    [    1.229890] i2c /dev entries driver
    [    1.231480] i2c i2c-6: Added multiplexed i2c bus 7
    [    1.231890] i2c i2c-6: Added multiplexed i2c bus 8
    [    1.231896] i2c-mux-gpio cam_i2cmux: 2 port mux on Tegra I2C adapter adapter
    [    1.232307] imx219 7-0010: camera_common_parse_ports: port 0 num of lanes 2
    [    1.232367] imx219 7-0010: parsing for mode0 props
    [    1.232415] imx219 7-0010: parsing for mode1 props
    [    1.232457] imx219 7-0010: parsing for mode2 props
    [    1.232499] imx219 7-0010: parsing for mode3 props
    [    1.232540] imx219 7-0010: parsing for mode4 props
    [    1.232581] imx219 7-0010: parsing for mode5 props
    [    1.232623] imx219 7-0010: imx219_probe: name imx219_a
    [    1.232628] imx219 7-0010: camera_common_create_debugfs imx219_a
    [    1.232641] imx219 7-0010: tegracam sensor driver:imx219_v2.0.6
    [    1.234593] tegradc tegradc.0: blank - powerdown
    [    1.255934] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x10
    [    1.256021] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
    [    1.256048] imx219 7-0010: board setup failed
    [    1.256110] imx219: probe of 7-0010 failed with error -121
    [    1.256251] imx219 8-0010: camera_common_parse_ports: port 4 num of lanes 2
    [    1.256309] imx219 8-0010: parsing for mode0 props
    [    1.256355] imx219 8-0010: parsing for mode1 props
    [    1.256394] imx219 8-0010: parsing for mode2 props
    [    1.256435] imx219 8-0010: parsing for mode3 props
    [    1.256474] imx219 8-0010: parsing for mode4 props
    [    1.256514] imx219 8-0010: parsing for mode5 props
    [    1.256552] imx219 8-0010: imx219_probe: name imx219_e
    [    1.256556] imx219 8-0010: camera_common_create_debugfs imx219_e
    [    1.256567] imx219 8-0010: tegracam sensor driver:imx219_v2.0.6
    [    1.272708] extcon-disp-state extcon:disp-state: cable 47 state 0
    [    1.272711] Extcon AUX1(HDMI) disable
    [    1.279844] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x10
    [    1.279928] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
    [    1.279959] imx219 8-0010: board setup failed
    [    1.280016] imx219: probe of 8-0010 failed with error -121

  • 0
    •  Analog Employees 
    on Feb 22, 2021 12:47 PM in reply to ykov

    Hi,

    It might be that you don`t have the proper image. Try using the pre-built image for jetson from here: https://github.com/analogdevicesinc/aditof_sdk .

    Please let me know the results.

  • I did use the pre-built image for Nano, but let me try to download again

  • Same results. The md5sums of the image I used is:

    22fe26268b8a4860cab3a72bb2372ba8  jetson_latest_image.tar.xz

    c55f58877559cce29673ee056ea63e04  jetson_latest_image/jetson_latest_ea8ffd5.img

    Boots fine, ADDI9036 seems to be included in the kernel Image (strings /boot/Image |grep ADDI9 gives "Detected ADDI9036 sensor") but no ADDI9036 is probed in dmesg (see above).

    Btw, I am getting the same results when I build the kernel  (that pre-built image seems still to be corrupt) for the Xavier NX, even if I configure out the IMX219

    So coming back to the first question, does Rev. D needs any different treatment? I don't think it is a cabling issue as i tried with 2, both working with a RPi Cam

  • 0
    •  Analog Employees 
    on Feb 22, 2021 3:06 PM in reply to ykov

    For Xavier NX please try to use the other connector as seen in the image on this page

  • Still the same, but with the Xavier NX the problem could be that I am using  L4T 32.5, will have to try with L4T 32.3.1

  • For Xavier NX I had to build also the SD card image based on NVIDIA's sample rootfs and their script. Now at least I can see the kernel probing the ADDI9036 sensor, which should be ok(?)

    [ 2.154288] addi9036 9-0064: probing addi9036 v4l2 sensor
    [ 2.154347] addi9036 9-0064: reset-gpios not found -2
    [ 2.154926] addi9036 9-0064: Detected ADDI9036 sensor
    [ 2.154964] addi9036 10-0064: probing addi9036 v4l2 sensor
    [ 2.155004] addi9036 10-0064: reset-gpios not found -2
    [ 2.155251] addi9036 10-0064: couldn't create debugfs
    [ 2.155536] addi9036 10-0064: Detected ADDI9036 sensor 

    If i use the NVIDIA's prebuild SD card image, as suggested in the doc, and update the kernel / devicetree or also modules it insists on probing the IMX219 sensor..

    Also this seems to be the case with R32.5  (the suggested R32.3.1 doesn't officially supports Xavier NX)

  • 0
    •  Analog Employees 
    on Feb 24, 2021 8:19 AM in reply to ykov

    HI

    Does the example work now?
    Have you also tried the pre-built image for NX from here?