Skip to main content
In this section ROS 2 Jazzy is installed directly on T3 Gemstone O1 and the UGV workspace is built on the board. Then the Deneyap Mini v2 that reads the line sensor is programmed, and the overlays required for the motor PWM lines are enabled. Requirements:
  • A microSD card of at least 32 GB, or the board’s internal eMMC
  • An internet connection (Ethernet or Wi-Fi)
  • A user with sudo privileges
The commands on this page assume that gemstone was chosen as the user name in Gem Imager. If you chose a different user name, replace /home/gemstone with your own home directory.

1. Operating System Installation

1

Write the image

Install Gem Imager on your computer and insert the microSD card using a card reader. In Gem Imager, select the T3-GEM-O1 model, the Ubuntu 24.04 (Noble) Minimal image and the microSD card as the target. On the customization screen, set the user password, enable SSH if you will connect remotely, and optionally enter your Wi-Fi credentials. Then write the image.For details, refer to the Quickstart and Image Writer pages.
2

Boot the board

With T3 Gemstone O1 powered off, insert the microSD card and set the boot switches to the SD card position. Then power on the board. If you will use the internal eMMC, follow the writing an image to eMMC steps.
3

Connect to the board

Connect T3 Gemstone O1 to the internet over Ethernet or Wi-Fi. Log in via SSH from a computer on the same network, or with a monitor and keyboard attached to T3 Gemstone O1. If the board is connected to your computer with a USB Type-C cable, you can use the following command.
For adding a Wi-Fi network and finding the robot’s IP address, refer to the Network Connection page.

2. Installing the UGV Software

Run the following commands in order on T3 Gemstone O1 as your regular user with sudo privileges (not as root). Commands that require sudo will ask for your password.

2.1. Download the repository

The repository’s scripts/install-native.sh script runs steps 2.2–2.6 in one go. To use it, run cd ~/ugv-ros && bash scripts/install-native.sh after downloading the repository and continue with Uploading the Deneyap Mini v2 Firmware.

2.2. Add the ROS 2 apt source

ROS 2 packages are installed from ROS’s own apt repository. Download and install the latest version of the ros2-apt-source package, which registers the repository.

2.3. Install ROS 2 Jazzy and development tools

2.4. Install the USB lidar driver (CP210x)

The lidar’s USB adapter uses the CP210x USB-serial driver. This module may be missing from the minimal image; in that case the adapter shows up in the lsusb output but /dev/ttyUSB0 is not created. First check whether the module is available.
If the command prints the module information, you can move on to the next step. If you get a Module cp210x not found error, install the driver from the T3 apt repository. This package only adds the driver module; it does not change the kernel.
Finally, load the module.
If no kernel-module-cp210x package matching the running kernel version can be found, the USB lidar connection will not work. You can still use the lidar by connecting it directly to T3 Gemstone O1’s GPIO pins. Lidar connection

2.5. Create the libgpiod v2 Python environment

The libgpiod v2 Python binding is required to read the encoders at high speed without missing counts. Since the Ubuntu 24.04 apt repository only provides version 1.6, v2 is installed into a separate virtual environment without touching the system Python.

2.6. Install dependencies and build the workspace

Download the lidar driver (sllidar_ros2), which is built from source.
Initialize the rosdep tool and update its package list. rosdep init is only needed on the first installation; if you get a default sources list file already exists error, you can skip this command.
Install all ROS dependencies (slam_toolbox, Nav2, robot_localization, rosbridge, etc.).
Build the workspace. To avoid running out of memory on the board, it is recommended to build the packages sequentially with at most two jobs.
Installing the dependencies and building may take 20–40 minutes depending on your internet speed.

3. Uploading the Deneyap Mini v2 Firmware

The deneyap_line.ino firmware reads the eight analog outputs of the line sensor through A0–A7 and sends the millivolt values to T3 Gemstone O1 over UART about 50 times per second. The same JSON lines are also visible on the USB serial monitor. It does not control the motors; the black/white calibration is stored on T3 Gemstone O1.
The Mini v2’s 5V pin is connected to the USB supply line. Before connecting the Mini v2 to a computer over USB, always disconnect the 5 V, TX and RX wires coming from T3 Gemstone O1.
1

Install Deneyap Kart IDE

Install Deneyap Kart IDE on your computer. On first launch, wait for the downloads on the Geliştirme Ortamı Hazırlanıyor (preparing the development environment) screen to finish. Deneyap Kart IDE setup guide
2

Connect the board to your computer

Turn off the power and disconnect the 5 V, TX and RX wires coming from T3 Gemstone O1. Connect the Mini v2 to your computer with a USB cable that supports data transfer.
3

Open the firmware and select the board

Open the firmware/deneyap_line/deneyap_line.ino file from the repository using Ayarlar → Dosya Aç (Settings → Open File). Select the Deneyap Mini v2 board in the top toolbar.
4

Compile and upload

In the Araçlar (Tools) menu, set Upload Mode to Internal USB and USB CDC On Boot to Enabled. Select the Mini v2’s port and click Derle ve Yükle (compile and upload). Deneyap Kart IDE interface guideIf the port does not appear, hold the BUT button, press and release the RES button, then release BUT. Click the Portları Yenile (refresh ports) button, select the port that appears in upload mode and try again. Deneyap Mini v2 troubleshooting guide
5

Check the output

When the upload is complete, open the Seri Monitör (serial monitor) tab, select the board’s port and a baud rate of 115200, and click Bağlan (connect). You should see JSON lines similar to the one below. If the firmware does not start after uploading, press the RES button once.
The values in the example are illustrative; they should change when the sensor is moved over black and white surfaces.
The verified build target for the Mini v2 is shown below. Run the command in the repository directory.
The same source code can also be used for the Deneyap Kart 1A v2. In that case, recompile it with Deneyap Kart 1A v2 selected and wire it according to that board’s A0–A7/TX/RX labels. The pin definitions come from the board package; do not change the GPIO numbers in the source code manually.

4. PWM and UART Settings (Overlay)

The PWM channels used for the motor driver’s ENA/ENB lines are enabled with overlays added to the overlays= line in the /boot/uEnv.txt file. For detailed information about overlays, refer to the PWM and Device Tree pages. Follow the steps in the tab that matches how your lidar is connected. The connection options are explained in the Lidar connection section.
Open the /boot/uEnv.txt file.
On the overlays= line, replace spidev0-2cs with spidev0-1cs and, without removing the other overlays, add the PWM overlays for ENA and ENB to the end of the line separated by spaces. The line should look similar to the following.
Save the file and reboot the board.
After the board boots, check that the PWM chips and UART devices have been created.
/dev/ttyS3 is the Deneyap Mini v2’s UART and /dev/ttyS0 is the GPIO lidar’s UART. If you are using the USB lidar, it is normal that /dev/ttyS0 does not exist. If you are using the GPIO lidar, the dmesg | grep ttyS0 output should contain the line 2b300000.serial: ttyS0.
pwmchipN numbers change depending on how many overlays are loaded. For this reason, the UGV configuration specifies PWM channels by module name (ecap0, epwm1:1) rather than by number. Which chip corresponds to which module is listed by the hw_check pins command during the Field Test.

Overlays that must not be enabled

The following overlays must not be enabled because they assign GPIO pins used by UGV to other functions.
The two channels of the same epwm module (GPIO6 and GPIO13) must share the same period. Since GPIO6 is not enabled as PWM, ENB can use any period it needs. If a conflict occurs, the driver adopts the sibling channel’s period and writes a warning to the log.
After the installation is complete, make the connections described on the Hardware and Wiring page.