Skip to main content

Getting Started with the Latest RealSense SDK

  • Updated

This article provides instructions on how to get started with RealSense GMSL cameras and the latest release of the RealSense Viewer SDK (v2.56.5). 

First, ensure you have flashed your device with the latest CTI BSP release for Intel RealSense Cameras (L4T r36.4.4). This BSP uses the latest RealSense driver which accounts for the seventh video node introduced by RealSense in their SDK v2.56.5. (Our earlier BSPs use an earlier RealSense driver and have shown camera enumeration issues when using the latest RealSense SDK).

Before beginning with the installation process, dependencies need to be installed:

$ sudo su
 $ apt update 
 $ apt-get install -y --no-install-recommends build-essential git libssl-dev libusb-1.0-0-dev libudev-dev pkg-config libgtk-3-dev libglfw3-dev libgl1-mesa-dev libglu1-mesa-dev v4l-utils curl cmake git

Note, after the first line is performed you should have root privileges. The rest of the process should continue to be executed as root user.

The next step is now to clone the librealsense repository and checkout the correct branch:

$ git clone https://github.com/IntelRealSense/librealsense.git && cd librealsense
 $ git fetch origin && git checkout v2.56.5 
 $ git checkout v2.56.5

Now, build the RealSense SDK:

$ mkdir build && cd build
 $ cmake ../
 $ make -j8
 $ make install
 $ sync
 $ reboot

You should now be up and running with the latest RealSense SDK. You can open the RealSense viewer with the command, $ realsense-viewer. Note, you may receive a message indicating no udev rules found upon opening the viewer, this message can be ignored. 

Additionally, the latest RealSense SDK was released with a new firmware update (Version-5.17.0.10). If you would like to update your cameras firmware, the process is as follows:

  1. After the RealSense SDK has been successfully installed, download the firmware signed image binary (.bin file) and move it to the Jetson device.

  2. Determine the camera device file with rs-enumerate-devices -S. The information needed is "Dfu Device Path" which should be the last entry on the table populated. 

    If the Dfu Device Path isn’t populated through rs-enumerate-devices, the path can be found with ls /dev/*dfu*. If there are multiple cameras connected and you only want to update specific ones, shutdown the device and unplug the cameras not being updated. This ensures that the only paths to appear are those of cameras to be updated.

  3. Next, apply the firmware update from the directory where the signed image binary was downloaded as root user: sudo cat [signed-image-binary-file] > [dfu-device-path]. 
    For example, sudo cat Signed_Image_UVC_5_17_0_10.bin > /dev/d4xx-dfu-0

    The terminal may appear to hang as if the device has frozen – this is normal. If you would like to view the progress of the update, open a second terminal and run sudo dmesg -w. You will know the firmware update is complete once user control is returned to the terminal where the cat command was run.

  4. The firmware update can be confirmed by running rs-enumerate-devices -s. The firmware version should display the newly updated version.
     

This process should provide everything needed to get started. For information on performing a hardware sync test, please see our article, RealSense Synchronization. 

Related articles