Post Go back to editing

Can't open "aditof-demo 3.1.0"

Category: Software
Product Number: AD-FXTOF1-EBZ

Hello,

I try to use Raspberry Pi 4B to operate the LiDAR(AD-FXTOF1-EBZ). I have followed all the steps on the website called "Raspberry Pi User Guide". 

Unfortunately, I can't open it. When I pressed the play button, it would stop like the figure shown below.

When I used command window to open it, it showed some error message:

  • I20240919 15:54:57.865922 8189 system_impl.cpp:120] SDK version: 3.1.0 | branch: master | commit: 595409a
  • I20240919 15:54:57.865934 8189 system_impl.cpp:125] SDK built with websockets version:3.2.3
  • I20240919 15:54:57.981110 8189 sensor_enumerator_raspberrypi.cpp:53] looking for sensors on the target: Raspberry PI
  • I20240919 15:54:57.981846 8189 camera_fxtof1.cpp:137] Initializing camera
  • I20240919 15:54:57.982010 8189 addi9036_sensor.cpp:155] Opening device
  • I20240919 15:54:57.982040 8189 addi9036_sensor.cpp:173] Looking for the following cards:
  • I20240919 15:54:57.982061 8189 addi9036_sensor.cpp:175] unicam
  • I20240919 15:54:57.982617 8189 addi9036_sensor.cpp:191] Cannot identify /dev/video0 errno: 2error: No such file or directory
  • I20240919 15:54:57.982687 8189 addi9036_sensor.cpp:148] Failed to open device
  • I20240919 15:54:57.983664 8189 camera_fxtof1.cpp:881] Programming AFE error errno: 9 error: Bad file descriptor
  • I20240919 15:54:57.983736 8189 addi9036_sensor.cpp:392] VIDIOC_REQBUFS error errno: 9 error: Bad file descriptor
  • I20240919 15:54:57.983806 8189 camera_fxtof1.cpp:376] Failed to set frame type
  • I20240919 15:54:57.983773 8189 camera_fxtof1.cpp:226] Chosen mode: near
  • I20240919 15:54:57.983930 8189 camera_fxtof1.cpp:239] Camera range for mode: near is 250 mm and 800 mm
  • I20240919 15:54:57.984032 8189 camera_fxtof1.cpp:250] Found firmware for mode: near
  • I20240919 15:54:57.984077 8189 camera_fxtof1.cpp:253] Firmware size: 14404 bytes
  • I20240919 15:54:57.984107 8189 addi9036_sensor.cpp:527] Programming AFE error errno: 9 error: Bad file descriptor
  • I20240919 15:54:57.984166 8189 camera_fxtof1.cpp:258] Failed to program AFE

 I need some feedback to help me solve this problem. 

Tim

Parents
  • Hi  ,

    The error massage looks like that your ToF driver is not loading correctly by Raspberry Pi. Please check followings,

    1. Power Sequence: 

    Raspberry Pi will scan peripheral devices while booting up. ToF must be powered on earlier than Raspberry Pi. So, Raspberry Pi can detect ToF correctly and then load associated driver.

    2. Driver:

    When you get in Raspberry Pi Desktop. Open Terminal and enter "i2cdetect -y 10". If you see "UU" in address 0x56, 0x257, 0x64, 0x73. It means that the ToF driver is loaded correctly.

    If the driver is loading properly. You can launch the ToF UI and see the correct message on Terminal.

  • Hi Bruce,

    We tested according to the power sequence form you provided,

    but in the I2C dect table, the 0x64, 0x73 aren't UU (please see the picture below~)


    We also can't turn on the device (please see the picture below~)

    as following picture is our connection configuration.



    Please help me find out where is the problem? Thanks very much.

  • Hi Klex,

    Please make sure you flash the latest image from ADI website into your SD Card.
    GitHub - analogdevicesinc/aditof_sdk: Analog Devices 3D ToF software suite

    You I2C communication looks fine. But your RPI can't drive ToF module correctly. I think it is caused by the RPI OS. Please flash SD Card and try again.

  • Hi Bruce,

    I rebuilt the SD card using another tool and everything works fine.

    Let you know, thanks for your support.

Reply Children