-
Notifications
You must be signed in to change notification settings - Fork 35
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: Ugo Pattacini <[email protected]>
- Loading branch information
1 parent
5656c96
commit 11de72b
Showing
13 changed files
with
230 additions
and
193 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# Install the latest CMake version (MANDATORY only for Ubuntu 20.04) | ||
|
||
!!! info | ||
|
||
This procedure should be performed after the [JetPack installation](./jetpack.md) has been completed. | ||
|
||
The latest YARP v3.10.0 requires CMake >= 3.19, but Ubuntu 20.04 only provides CMake 3.16, so it needs to be upgraded. | ||
|
||
To download the latest version, first remove CMake with: | ||
|
||
```bash | ||
sudo apt purge --auto-remove cmake | ||
``` | ||
|
||
Get a copy of the signing key: | ||
|
||
```bash | ||
wget -O - https://apt.kitware.com/keys/kitware-archive-latest.asc 2>/dev/null | gpg --dearmor - | sudo tee /etc/apt/trusted.gpg.d/kitware.gpg >/dev/null | ||
``` | ||
|
||
Add the repository: | ||
|
||
```bash | ||
sudo apt-add-repository "deb https://apt.kitware.com/ubuntu/ $(lsb_release -cs) main" | ||
``` | ||
|
||
Update the repo index and install CMake: | ||
|
||
```bash | ||
sudo apt update | ||
sudo apt install cmake | ||
``` |
21 changes: 21 additions & 0 deletions
21
docs/icub_operating_systems/icubos/install-cuda-libraries.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Install the CUDA libraries | ||
|
||
!!! info | ||
|
||
This procedure should be performed after the [JetPack installation](./jetpack.md) has been completed. | ||
|
||
Usually the Jetpack flashing procedure takes care of installing the Cuda toolkit and libraries. If running the command `nvcc --version` returns `Command not found`, then you need to install them manually though `apt`. | ||
|
||
For example **Jetpack 4.5.1**, which uses **Cuda 10.2** do: | ||
|
||
```bash | ||
sudo apt install cuda-libraries-dev-10-1 cuda-nvcc-10-2 | ||
``` | ||
|
||
Then, within the `.bashrc`: | ||
|
||
```bash | ||
export CUDA_HOME=/usr/local/cuda-10.2 | ||
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-10.2/lib64:/usr/local/cuda-10.2/extras/CUPTI/lib64 | ||
export PATH=$PATH:$CUDA_HOME/bin | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Install jtop | ||
|
||
!!! info | ||
|
||
This procedure should be performed after the [JetPack installation](./jetpack.md) has been completed. | ||
|
||
`jtop` (a.k.a [jetson-stats](https://github.com/rbonghi/jetson_stats)) is a package for monitoring and control your NVIDIA Jetson boards. | ||
|
||
![](../img/jtop.gif) | ||
|
||
For installing it: | ||
|
||
```bash | ||
sudo -H pip install -U jetson-stats | ||
``` |
39 changes: 39 additions & 0 deletions
39
docs/icub_operating_systems/icubos/install-librealsense.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Install `librealsense` with Cuda support | ||
|
||
!!! info | ||
|
||
This procedure should be performed after the [JetPack installation](./jetpack.md) has been completed. | ||
|
||
`librealsense` is a cross-platform library provided by Intel that can be used to take advantage of the features of the Intel Realsense cameras. | ||
After installing the [cuda libraries](./install-cuda-libraries.md), we can make the Realsense camera use also the gpu resources for better performances, enabling the cuda support. | ||
|
||
In a terminal, clone the official repo with: | ||
|
||
```bash | ||
git clone https://github.com/IntelRealSense/librealsense.git | ||
``` | ||
|
||
Install the librealsense required development packages: | ||
|
||
```bash | ||
sudo apt install libssl-dev freeglut3-dev libusb-1.0-0-dev pkg-config libgtk-3-dev unzip -y | ||
``` | ||
|
||
Install the `udev` rules (the librealsense kernel patching procedure does not work with recent Jetpack versions): | ||
|
||
```bash | ||
sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/ | ||
sudo udevadm control --reload-rules && sudo udevadm trigger | ||
``` | ||
|
||
Now you are ready to compile librealsense with Cuda support: | ||
|
||
```bash | ||
cd librealsense | ||
mkdir build && cd build | ||
cmake ../ -DFORCE_LIBUVC=BOOL:ON -DCMAKE_BUILD_TYPE=Release -DBUILD_WITH_CUDA=BOOL:ON -DBUILD_EXAMPLE=BOOL:OFF | ||
make -j2 | ||
sudo make install | ||
``` | ||
|
||
For more information, refer to the [official documentation](https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md) provided in the repository. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
# Setup Orin NX for using with FRAMOS-IMX415-C | ||
|
||
This guide aims to highlight the correct procedure to configure the setup for using the [`FRAMOS-IMX415`](https://www.framos.com/en/products/fsm-imx415-sensor-module-26361) cameras with the [`Orin NX`](https://www.nvidia.com/it-it/autonomous-machines/embedded-systems/jetson-orin/) from Nvidia + [`Boson for FRAMOS`](https://connecttech.com/product/boson-for-framos-carrier-board-for-nvidia-jetson-xavier-nx/) carrier from ConnectTech. | ||
|
||
!!! info | ||
|
||
Be sure that the [Jetpack installation](./jetpack.md) procedure up to the BSP installation on the setup has been completed. At this point we are ready to flash the image. | ||
|
||
### Flash the image | ||
|
||
In the host: | ||
|
||
1. Navigate into `/nvidia/nvidia_sdk_JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra` | ||
2. Run the flash script (as root or sudo): | ||
|
||
``` | ||
sudo ./cti-nvme-flash.sh cti/orin-nx/boson/fsm-imx415-2cam | ||
``` | ||
|
||
3. Once the flash has completed, the board will reboot. | ||
|
||
Check out the [ConnectTech tutorial](https://connecttech.com/resource-center/kdb373/) explaining the complete procedure. | ||
|
||
### Complete the OEM installation | ||
After booting into the OS, follow the OEM installation with the default options. | ||
|
||
Set the user name to `ergocub` with the hostname `ergocub-head`. Allow login without password and let the installation process finish. | ||
|
||
After rebooting into the graphical OS, run the following commands in a terminal to update the system: | ||
|
||
```bash | ||
sudo apt install -f | ||
sudo apt update && sudo apt upgrade | ||
reboot | ||
``` | ||
|
||
### Switch profile on Orin NX | ||
After the reboot process: | ||
|
||
1. Open a new terminal on the Orin NX and run `sudo cti-orin-nx-nano-fdt.sh` | ||
2. Follow the interactive procedure and select `Orin NX`, then `Boson NGX007` and finally the profile for the FRAMOS IMX415 cameras, i.e. `fsm-imx415-2cam` | ||
3. Once the script exits, run `sync` and `reboot` to finalize the changes. | ||
|
||
![post-flash](../img/post-flash.png) | ||
|
||
## Post-flashing operations | ||
|
||
### Install FRAMOS drivers | ||
|
||
From the [`FRAMOS Resource Center`](https://www.framos.com/en/fsm-startup), download the proper software by selecting the following entries: | ||
|
||
![framos-sw](../img/framos-sw.png) | ||
|
||
Unzip the file in the folder you prefer, then navigate into and run: | ||
|
||
``` | ||
sudo apt install ./framos-libsv_*_arm64.deb | ||
``` | ||
|
||
As soon as the installation procedure has finished, please power off the Orin NX. Then plug-in your cameras to the `CAM1` and `CAM2` connectors, and finally power on the board again. | ||
|
||
!!! warning | ||
During the flashing procedure, the profile `fsm-imx415-2cam` has been selected, which means that two cameras could be used with this configuration. For this reason, only `CAM1` and `CAM2` connectors are enabled to read the data from the FRAMOS-IMX415, while CAM3 and CAM4 are not. Please, be sure that they are properly connected. | ||
|
||
Check if the cameras are detected running `ls /dev/video*` from the command line. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.