• Recent
    • Docs
    • Github
    • 百度网盘
    • Onedrive
    • Official
    • Shop
    • Register
    • Login

    D435i相机内核支持

    Scheduled Pinned Locked Moved Pi 4B
    3 Posts 2 Posters 29 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tom-jerr
      last edited by tom-jerr

      We are currently trying to compile and use librealsense from source on a CoolPi 4B(RK3588) to support our Intel RealSense D435i camera.

      Our progress so far is as follows:

      • We have successfully compiled the library on our system.
      • The RGB Camera and Depth Camera functionalities are working correctly, and we can stream data from them without issues.

      However, we are facing a problem: we are unable to receive the dual infrared (grayscale) image streams from the stereo cameras.
      We understand that enabling these streams typically requires applying Intel's kernel patches to the system. The challenge is that our CoolPi 4B runs on a 5.10 kernel, and the official librealsense patches do not seem to support this version.

      Image

      According the document, we have now recompiled librealsense on our CoolPi 4B (Kernel 5.10) with the -DFORCE_RSUSB_BACKEND=ON flag in CMake, as recommended. The goal was to bypass the kernel's uvcvideo driver, which does not recognize the RealSense camera's custom video formats.
      However, after recompiling and attempting to run our application (or realsense-viewer), we can not read gray image from /camera/infra1 and /camera/infra2. Some useful messages list below.

      Image

      How can we solve this problem? Please give us some advice.
      Thank you for your help.

      T G 2 Replies Last reply Reply Quote 0
      • T
        tom-jerr @tom-jerr
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • G
          george @tom-jerr
          last edited by

          @tom-jerr
          The log has been correctly enumerated to USB 3.0 devices.
          415511f0-819b-4ff9-9160-85086f2e4afe-image.png

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post