reComputer_Industrial_R22xx_configure_system

Overview

Learn how to configure and test hardware components on the reComputer Industrial R22xx series after installing devices. This wiki covers GPIO mapping, USER LED testing, SPI communication, Wi-Fi and Bluetooth scanning, LoRa®, 4G, 5G，Zigbee over Mini-PCIe, RS485, RS232, CAN,DI/DO testing, UPS for safe shutdown and more.

Get One Now 🖱️

Query GPIO Mappings and Offsets

To query GPIO mappings and offsets, follow these steps:

1. Copy and paste the following command to query GPIO mappings:

cat /sys/kernel/debug/gpio

This command will display GPIO mappings and offsets, providing essential information for debugging or configuring GPIO pins.

USER LED Testing

We provide LEDs in three colors of red, blue and green for users to use. You can enter the /sys/class/leds/ directory to view：

1. Navigate to the LED directory

cd /sys/class/leds/
ls

Use the following command to light up the LED of the corresponding color.

sudo su
echo 1 > /sys/class/leds/led-red//brightness
echo 1 > /sys/class/leds/led-blue/brightness
echo 1 > /sys/class/leds/led-green/brightness

This will light up the corresponding LED.

3. Turn off LEDs (optional)
To turn off a specific LED, use:

sudo su
echo 0 > /sys/class/leds/led-red/brightness
echo 0 > /sys/class/leds/led-blue/brightness
echo 0 > /sys/class/leds/led-green/brightness

Testing SPI Communication

To test SPI communication by shorting the TPM module's MISO and MOSI pins, follow these steps:

1. Clone the spidev-test repository:

# Don't forget to connect to network before running command
git clone https://github.com/rm-hull/spidev-test.git

2. Navigate into the spidev-test directory:

cd spidev-test

3. Compile the spidev_test.c file:

gcc spidev_test.c -o spidev_test

4. Run the spidev_test program with the following command:

./spidev_test -D /dev/spidev10.0 -v -p hello

This command tests SPI communication on the specified SPI device (/dev/spidev10.0) with verbose output ( -v ) and sends the message "hello" (-p hello). By shorting the TPM module's MISO and MOSI pins, you're effectively creating a loopback scenario, where data sent on MOSI is received on MISO. This setup allows you to test SPI communication without an actual device connected.

Wi-Fi Scanning

To list available Wi-Fi networks and their details, run:

sudo iwlist wlan0 scan

• This command scans for all nearby Wi-Fi networks and displays their SSIDs, signal strength, and encryption type.

Bluetooth Scanning

To scan for Bluetooth devices, follow these steps:

Open the Bluetooth control interface:

sudo bluetoothctl

This command will open the Bluetooth control interface. From there, you can run additional commands to scan for nearby Bluetooth devices.

Enable scanning:

scan on

This command will start scanning for nearby Bluetooth devices. You can then use other commands within the bluetoothctl interface to interact with Bluetooth devices, such as pairing or connecting to them.

LoRa® over Mini-PCIe

LoRa® SPI Configuration

After install the LoRa® SPI to Mini-PCIe slot 2, can configure LoRa® SPI, follow these steps:

1. Clone the SX1302_HAL repository:

cd ~/
git clone https://github.com/Lora-net/sx1302_hal

2. Navigate to the cloned directory:

cd sx1302_hal

3. Modify the configuration file:

Open the I2C device configuration file:

sudo nano ./libloragw/inc/loragw_i2c.h

Change this line:

#define I2C_DEVICE "/dev/i2c-1"

To:

#define I2C_DEVICE "/dev/i2c-2"

Change #define I2C_DEVICE "/dev/i2c-1" to #define I2C_DEVICE "/dev/i2c-2". Press ctrl+x to exit, press y to save changes, and then press Enter to return to the command line page.

4. 4.Add the packet_forwarder/reset_lgw.sh file:

sudo nano packet_forwarder/reset_lgw.sh

Add the execution code:

SX1302_RESET_PIN=632     # SX1302 reset
SX1302_POWER_EN_PIN=633  # SX1302 power enable
SX1261_RESET_PIN=634     # SX1261 reset (LBT / Spectral Scan)
# AD5338R_RESET_PIN=13    # AD5338R reset (full-duplex CN490 reference design)

The firmware natively supports the SPI model WM1302-SPI-US915-M. If you wish to use other models, you can query the definition of the corresponding RESET_PIN and modify the RESET_PIN by referring to the following commands.

cat /sys/kernel/debug/gpio

Press ctrl+x to exit, press y to save changes, and then press Enter to return to the command line page.

5. Modify the configuration code:

cp ./tools/reset_lgw.sh ./packet_forwarder

6. Comment out lines 18, 29, 35, 42, 53, and 54 respectively:

nano ./packet_forwarder/global_conf.json.sx1250.US915

Change "com_path": "/dev/spidev0.0" to "com_path": "/dev/spidev2.0".

 cd ./packet_forwarder
sudo ./lora_pkt_fwd -c global_conf.json.sx1250.US915

LoRa® USB Configuration

For LoRa® USB, the previous commands remain the same as for LoRa® SPI. However, the final command needs to be changed to:

cho  632  >  /sys/class/gpio/export
echo  "out"  >  /sys/class/gpio/gpio632/direction
echo  "1"  >  /sys/class/gpio/gpio632/value

sudo  ./lora_pkt_fwd  -c  global_conf.json.sx1250.EU868.USB

This command specifies the configuration file to be used for LoRa® USB.

5G Cellular over M.2 B-KEY

To interact with a 5G/4G module using AT commands via minicom, follow these steps:

1. Create a new power_5g.sh file：

nano power_5g.sh

Open with sudo nano and enter the following command, then press ctrl+x to save and exit.

#!/bin/bash

RESET_PIN=655
POWER_PIN=660

if [ ! -d "/sys/class/gpio/gpio$RESET_PIN" ]; then
    echo $RESET_PIN > /sys/class/gpio/export
fi

if [ ! -d "/sys/class/gpio/gpio$POWER_PIN" ]; then
    echo $POWER_PIN > /sys/class/gpio/export
fi

echo "out" > /sys/class/gpio/gpio$RESET_PIN/direction
echo "out" > /sys/class/gpio/gpio$POWER_PIN/direction

echo 1 > /sys/class/gpio/gpio$RESET_PIN/value
echo 1 > /sys/class/gpio/gpio$POWER_PIN/value

echo "Start to reboot 5g module"

echo 0 > /sys/class/gpio/gpio$RESET_PIN/value
sleep 0.05
echo 0 > /sys/class/gpio/gpio$POWER_PIN/value

echo "5g module reboot completed"

2. Execute the file:

sudo ./power_5g.sh

After 10-15 seconds (it takes a while for the module to power on and enumerate USB), check whether the device node appears:

ls /dev/ttyUSB*

Output /dev/ttyUSB0, etc.:

Open minicom with the appropriate serial port and baud rate:

sudo apt update
sudo apt install minicom
sudo minicom -D /dev/ttyUSB2 -b 115200

This command opens minicom with the specified serial port (/dev/ttyUSB2) at a baud rate of 115200.

1. Once minicom is open, you can start sending AT commands to the 4G module. For example:

AT

This command checks if the module is responsive. You should receive an "OK" response if the module is working properly.

2. To dial a phone number using the 4G module, you can use the ATD command followed by the phone number:

ATD<phone_number>;

Replace phone_number with the desired phone number you want to dial. Make sure to include a semicolon ; at the end of the command to indicate the end of the phone number.

4G Cellular over Mini-PCIe

Create a new power_4g.sh file:

sudo nano power_4g.sh

Open with sudo nano and enter the following command, then press ctrl+x to save and exit.

# SIM_MUX_SEL
echo 655 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio655/direction
echo 0 > /sys/class/gpio/gpio655/value
echo 660 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio660/direction
echo 1 > /sys/class/gpio/gpio660/value

Execute the file:

sudo ./power_4g.sh

Enter minicom to send commands:

sudo apt install minicom -y
sudo minicom -D /dev/ttyUSB2 -b 115200

Press Ctrl+A, Z , E in sequence. First send AT to test whether it is connected. If OK appears, the connection is successful.

After executing the following command, the module will automatically restart. If you do not exit minicom, you can see the corresponding configuration information. ECM Dial-up Internet Access:

AT+QCFG="usbnet",1

Until the last line shows OK, it will be successful.

Note The device needs to wait for a while, and then you can view the ip address of usb0 in ifconfig.

Test network status and communication：

# Check network status
ifconfig
# Test communication
ping www.baidu.com -I usb0

Zigbee over Mini-PCIe

To test Zigbee communication between two Zigbee modules, follow these steps:

1. Check Available Serial Ports

Use the following command to check available serial ports:

cat /dev/ttyUSB*

Install a Serial Communication Tool

2. Install Serial Communication Tool:

sudo apt-get install cutecom

3. Open Serial Port for Coordinator (First Zigbee Module):

• Open the cutecom tool and configure it for the first serial port:
• Baud rate: 115200
• Check the "Hex output" option at the bottom of the interface.
• Follow these steps to configure the first Zigbee module:
• Set as coordinator: Send command ‘55 04 00 05 00 05’, expect response ‘55 04 00 05 00 05’.
• Reset device: Press reset button or send command ‘55 07 00 04 00 FF FF 00 04’.
• Network formation: Send command ‘55 03 00 02 02’.

4. Open Serial Port for Router (Second Zigbee Module): Open another instance of cutecom and configure it for the second serial port with the same settings as before. Follow these steps to configure the second Zigbee module:

• Set as router: Send command ‘55 04 00 05 01 04’, expect response ‘55 04 00 05 00 05’.
• Reset device: Press reset button or send command ‘55 07 00 04 00 FF FF 00 04’.
• Network formation: Send command ‘55 03 00 02 02’.

5. Check Device Status: Send command ‘55 03 00 00 00’ to check the device status. Expect a response similar to ‘55 2a 00 00 00 01 XX XX XX XX’, where ‘XX’ represents device information.
6. Enter Transparent Mode: If network formation is successful, enter transparent mode by sending command 55 07 00 11 00 03 00 01 13. Both modules should be in transparent mode for direct communication. To exit transparent mode, send "+++".
7. Additional Notes:

• If router configuration fails, the device may already be a coordinator. Leave the network using command '55 07 00 04 02 xx xx xx'.
• Test transmission power using commands '55 04 0D 00 00 0D' (query) and '55 04 0D 01 XX XX' (set). Ensure you replace /dev/ttyUSB with the correct serial port for each Zigbee module. Follow these steps carefully to test Zigbee communication between the two modules successfully.

RS485 Testing

The reComputer Industrial R21xx includes 2x RS485 ports. Below are their corresponding COM ports and device files:

Number of RS485 Ports	COM Port	Silkscreen Label	Device File
RS485-2	COM2	A2/B2/GND3	/dev/ttyACM1
RS485-3	COM3	A3/B3/GND4	/dev/ttyACM2

To test the RS485 function, you can follow the steps below (take RS485_1 and RS485_2 as examples):

1. Please connect RS485_1 and RS485_2's A and B.
2. Open minicom in two terminal windows respectively:

sudo minicom -D /dev/ttyACM1
sudo minicom -D /dev/ttyACM2

note

If there is an expansion board, the number needs to be moved back one place, for example /dev/ttyAcM2, /dev/ttyAcM3.

3. The following operations need to be performed on both opened ACMs:

• Press Ctrl+A, then press Z, and the Minicom Command Summary interface will appear:

  

• Press O again to open configuration, select Serial port setup, and press Enter; Open all RS485 related interfaces, press H/I/J/K/L in sequence to open;

  

• After all "YES" are displayed, press Enter to return, and then select Exit to exit.

note

Take ACM2 and ACM3 as an example: If you want to send from ACM2 to ACM3, ACM2 needs to be set up again: ctrl+A , then press Z and then E , and then start the serial port write command. At this time, you can print strings in ACM2 at will, and you can see the contents of ACM2 in ACM3 at the same time; Conversely, if you want to send from ACM3 to ACM2, ACM3 needs to be set up again: ctrl+A, then press Z and then E , and then start the serial port write command. At this time, you can print strings in ACM3 at will, and you can see the contents of ACM3 in ACM2 at the same time. As shown in the figure.

RS232 Testing

reComputer Industrial R21xx includes 2x RS232 ports, and the corresponding COM ports and device files are as follows:

Number of RS232 Ports	COM Port	Silkscreen Label	Device File
RS232-1	COM1	RX1/TX1/GND1	/dev/ttyACM0
RS232-2	COM2	RX2/TX2/GND2	/dev/ttyACM1

Because RS232 is full-duplex communication, short-circuit the TX and RX of RS232 directly to perform a loopback test.

You need to open two terminals, ACM1 if the expansion board is connected, and ACM2 if the expansion board is not connected: Terminal 1:*

sudo minicom -D /dev/ttyACM1 -b 9600

If the expansion board is not connected, you need to change /dev/ttyACM1 to /dev/ttyACM0 .

Terminal 2:

printf "hello seeed\r\n" > /dev/ttyACM1

Terminal 1 will display the content requested by Terminal 2 to be printed.

DI (Digital Input) Testing

reComputer Industrial R21xx contains 4x DI ports, user can configure these ports according to actual needs.

Number of ports	DI ports	Corresponding extended GPIO
4	DI1	GPIO588
	DI2	GPIO589
	DI3	GPIO590
	DI4	GPIO595

The input type of the DI ports is PNP. It supports input voltage is 5VDC~24VDC,current - 1000mA. To test the functionality of DI, you can follow these steps to test it:

1. The connection between the DI port of reComputer Industrial R21xx and the external load has been completed.
2. Enter the following command to get the status of GPIO：

echo 588 > /sys/class/gpio/export
echo in > /sys/class/gpio/gpio588/direction
cat /sys/class/gpio/gpio588/value

3. When the external level is high, the value of /sys/class/gpio/gpio588/value is 0; when the external level is low, /sys/class/gpio/gpio588/value is 1.

DO (Digital Output)

reComputer Industrial R21xx contains 4x DO ports, user can configure these ports according to actual needs.

Number of ports	DI ports	Corresponding extended GPIO
4	DO1	GPIO638
	DO2	GPIO637
	DO3	GPIO590
	DO4	GPIO636
DO5	GPIO635

The output type of the DO ports is transistor. It supports output voltage - under 60 VDC, current capacity - 500 mA. To test the functionality of DO, you can follow these steps to test it:

1. The connection between the DO port of reComputer Industrial R21xx and the external load has been completed.
2. Enter the following command to set the output to high level or low level：

echo 638 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio638/direction
echo 1 > /sys/class/gpio/gpio638/value
echo 0 > /sys/class/gpio/gpio638/value

3. When the external level is high, the value of /sys/class/gpio/gpio638/value is 0; when the external level is low, /sys/class/gpio/gpio638/value is 1.

CAN Testing

Loopback test

Number of ports	DI ports	Corresponding extended GPIO
2	CAN_H/CAN_L	can0

Since the reComputer Industiral R22xx is equipped with only a single CAN interface, it cannot perform independent loopback testing. To verify its communication functionality, an external peer device or a USB-to-CAN adapter is required. For this test, the reComputer Industiral R21xx (featuring dual CAN interfaces) will serve as the peer node to establish a connection with the reComputer Industiral R22xx. Please refer to the following tutorial for specific connection schemes and configuration steps:

1. Use two DuPont wires to short-circuit the H-H and L-L of can0 and can1 to form a minimum loop test.

CAN_H─────●───── CAN-H
CAN_L─────●───── CAN-L
G_CAN_H─────●───── G_CAN

2. Confirm that the two network interfaces can0 and can1 do appear in the system to prevent the driver from not loading:

# should print can0 can1
ls /sys/class/net | grep can 
# should see "successfully initialized"
dmesg | grep -i can

3. Set the two CAN interfaces to 500 kbit/s and go online, ready to send and receive data (set them to low level for safety): R22xx:

sudo ip link set can0 down
sudo ip link set can0 up type can bitrate 500000

R21xx:

sudo ip link set can1 down
sudo ip link set can1 up type can bitrate 500000

4. Communication Test (One-Way) Use can-utils to send and receive data.

Step A: R21xx (CAN1) Sends → R22xx (CAN0) Receives

• R22xx: candump can0

• R21xx: cansend can1 123#DE.AD.BE.EF.CA.FE.00.11

Step B: R22xx (CAN0) Sends → R21xx (CAN1) Receives

• R21xx: candump can1

• R22xx: cansend can0 555#1122334455667788

USB Hub Testing

To test the USB hub, you can use the following steps:

1. Check if the USB hub is detected by running the lsusb command. This command lists all connected USB devices, including hubs.

lsusb

Running this command should display information about the USB devices connected to your system, including any USB hubs that are present. If the USB hub is functioning properly, you should see its details listed in the output of the lsusb command. If it's not listed, there may be an issue with the hub or its connection to the system. In such cases, you may need to troubleshoot the USB hub or its connections.

RTC (Real-Time Clock) Testing

To test the Real-Time Clock (RTC) functionality, follow these steps:

1. Disable automatic time synchronization:

sudo systemctl stop systemd-timesyncd
sudo systemctl disable systemd-timesyncd

2. Set the time: Set the RTC to a specific date and time:

sudo hwclock --set --date "2025-10-23 16:00:00"

3. Sync RTC Time to the System Update the system time to match the RTC time:

sudo hwclock --hctosys

4. Check the RTC time:

sudo hwclock -r

This command will read and display the time stored in the RTC.

5. Disconnect the power source from the RTC, wait a few minutes, then reconnect it and check the RTC time again to see if it retained the correct time.

Watchdog Timer Testing

To perform a watchdog test, follow these steps:

1. Install the watchdog software:

sudo apt install watchdog

2. Edit the watchdog configuration file:

# make sure you install vim already, if haven't, can install by the command below
sudo apt-get install vim
sudo vim /etc/watchdog.conf

Modify the configuration as follows:

watchdog-device = /dev/watchdog
# Uncomment and edit this line for hardware timeout values that differ
# from the default of one minute.
watchdog-timeout = 120
# If your watchdog trips by itself when the first timeout interval
# elapses then try uncommenting the line below and changing the
# value to 'yes'.
#watchdog-refresh-use-settimeout = auto
# If you have a buggy watchdog device (e.g. some IPMI implementations)
# try uncommenting this line and setting it to 'yes'.
#watchdog-refresh-ignore-errors = no
# ====================== Other system settings ========================
#
# Interval between tests. Should be a couple of seconds shorter than
# the hardware time-out value.
interval = 15
max-load-1 = 24
#max-load-5 = 18
#max-load-15 = 12
realtime = yes
priority = 1

You can adjust other settings as needed.

3. Ensure the watchdog service is running:

sudo systemctl start watchdog

4. To test the watchdog functionality, execute the following command to simulate a system hang:

sudo su

echo 1 > /proc/sys/kernel/sysrq
echo "c" > /proc/sysrq-trigger

This command triggers a kernel crash and should cause the watchdog to reboot the system.

5. Monitor the system to confirm that it reboots after the specified timeout period. These steps will help you test and ensure the functionality of the watchdog timer on your system.

Controlling the Buzzer via GPIO

The GPIO corresponding to the buzzer is gpio627. Enter the following script to turn the buzzer on/off :

1. Turn on the buzzer :

echo 627 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio627/direction
echo 1 > /sys/class/gpio/gpio627/value

2. Turn off the buzzer :Turn off the buzzer :

echo 627 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio627/direction 
echo 0 > /sys/class/gpio/gpio627/value

TPM 2.0

If you connect TPM 2.0 module to device, the following code can help check TPM connection.

ls /dev | grep tpm

Interpreting the Output:

If you see tpm0 and tpmrm0 in the output, it means that TPM (Trusted Platform Module) devices are detected and available on your system. This indicates that the TPM hardware is recognized and accessible, which is a good sign. You can proceed with using TPM-related functionalities or applications knowing that the devices are present and accessible.

ATECC608A

To interact with the ATECC608A device and generate a random serial number, follow these steps:

1. Clone the atecc-util Repository:

curl -LJO https://github.com/wirenboard/atecc-util/releases/download/v0.4.12/atecc-util_0.4.12_arm64.deb

2. Extract the contents of the .deb package to the current directory:

dpkg -x ./atecc-util_0.4.12_arm64.deb .

3. Navigate to the atecc Directory:

cd usr/bin

4. Generate a Random Serial Number:

./atecc -b 10 -s 192 -c 'serial'

This command instructs the ATECC utility to use slot 10 (-b 10), set the serial number size to 192 bits (-s 192), and generate a random serial number (-c 'serial'). The output will be the generated serial number, such as "01235595d3d621f0ee". This process allows you to interact with the ATECC608A device and perform various operations, such as generating random serial numbers.

Interacting with EEPROM

Here are the commands to interact with an EEPROM (Electrically Erasable Programmable Read-Only Memory):

1. Grant full permissions (read, write, and execute) to the EEPROM device file:

 sudo chmod 777 /sys/bus/i2c/devices/10-0050/eeprom

2. Write the string "This is a test string" to the EEPROM device:

echo "This is a test string" > /sys/bus/i2c/devices/10-0050/eeprom

3. Read the contents of the EEPROM device and displays it in hexadecimal format using the hexdump utility:

cat /sys/bus/i2c/devices/6-0050/eeprom | hexdump -C

Checking SSD Detection

To list the disks, including the SSD, you can use the fdisk -l command. Here's how:

sudo fdisk -l

This command will display a list of all disks connected to your system, including the SSD if it's properly detected. Look for entries that represent your SSD. They typically start with /dev/sd followed by a letter (e.g. /dev/sda, /dev/sdb, etc.). Once you identify the entry corresponding to your SSD, you can proceed with partitioning or formatting it as needed.

UPS for Safe Shut Down

A GPIO6 between CPU and DC power in is used to alarm CPU when the power supply is down. Then the CPU should do something urgent in a script before energy exhaustion of super capacitor and run a "$ shutdown". Another way to use this function is Initiate a shutdown when GPIO pin changes. The given GPIO pin is configured as an input key that generates KEY_POWER events. This event is handled by systemd-logind by initiating a shutdown.

1. Hardware connection.

Please make sure that the 'CM5_UPS_DET' pin of the UPS device is connected to the GPIO16 pin of the R21xx device.

2. Modify the configuration file.

• Open the terminal.
• Execute the following command to edit the configuration file:

sudo nano /boot/firmware/config.txt

3. Add the following content at the end of the file:

dtoverlay=gpio-shutdown,gpio_pin=GPIO16,active_low=1

Save and exit the editor (press Ctrl+O to save, Enter to confirm, and Ctrl+X to exit).

4. Prepare Python script

• Create a new Python script file:

cd ~
sudo nano ups_shutdown.py

• Copy and paste the following code into the file:

import RPi.GPIO as GPIO
import time, os

num = 0

GPIO.setmode(GPIO.BCM)

# Set GPIO16 to input mode
# Add 500ms anti-shake time to stabilize the software
GPIO.setup(16, GPIO.IN, pull_up_down=GPIO.PUD_UP)
GPIO.add_event_detect(16, GPIO.FALLING, bouncetime=500)

while True:
    if GPIO.event_detected(16):
        print("...External power off...")
        print("")

        # Sync data to disk
        os.system('sync')
        print("...Data saving...")
        print("")

        # Sleep for 3 seconds
        time.sleep(3)

        # Synchronize data again
        os.system('sync')

        # Countdown 5 seconds
        while num < 5:
            print('----------')
            s = 5 - num
            print('---' + str(s) + '---')
            num = num + 1
            time.sleep(1)
            print('----------')

        # Execute shutdown command
        os.system('sudo shutdown -h now')

Save and exit the editor (press Ctrl+O to save, Enter to confirm, and Ctrl+X to exit).

5. Run the script.

• Open the terminal.
• Execute the following command to run the script:

sudo python3 ups_shutdown.py

note

Use sudo to ensure that the script has sufficient permissions to execute the shutdown command.

6. Simulate power failure test

• Cut off the external power supply.
• Observe whether the system automatically saves data and shuts down.

7. Verify the result

• Reconnect the power supply.
• Check whether the system data is complete and starts normally.

note

1. For UPS function please contact us for more information.
2. The alarm signal is active LOW.

AI Accelerator

The M.2 M-KEY 2280 slot on the reComputer Industrial R21xx is designed to accommodate PCIE M.2 AI Accelerator. And the R21xx-12 series has been pre-installed with a Hailo-8 M.2 AI Acceleration up to 26TOPS. If you purchased the R21xx-10 series product, you will need to purchase Hailo's NPU module to enable AI functionality. The device comes pre-installed with the Hailo accelerator driver, so you can use it directly and run the test case:

1. Navigate to the test case directory

cd /mnt/hailo-rpi5-examples/

2. Start the virtual environment

source ./setup_env.sh

3. Run the simple detection example

python basic_pipelines/detection_simple.py

To close the application, press Ctrl+C . This is lightweight version of the detection example, mainly focusing on demonstrating Hailo performance while minimizing CPU load. The internal GStreamer video processing pipeline is simplified by minimizing video processing tasks, and the YOLOv6 Nano model is used.

note

If the reComputer you purchased does not include Hailo-8 and you are considering purchasing a Hailo device for integration, please refer to the official Hailo documentation (https://github.com/hailo-ai) to configure the firmware and environment, and run the examples to verify that the device can be used normally.

PoE IP Camera

note

• Four Ethernet ports must not be configured on the same network segment: Doing so will cause network conflicts and lead to communication failure.
• Ethernet ports do not support hot-swapping: You must power down both the development board and the cameras before connecting or disconnecting Ethernet cables; hot-swapping may result in permanent hardware damage to the ports.
• External power supply for IP cameras is strictly prohibited: Cameras should be powered solely via PoE through the Ethernet cable; providing additional external power may cause current backflow and damage the development board's Ethernet ports.

1. Connect the network cable and start the network port:

echo 652 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio652/direction
echo 1 > /sys/class/gpio/gpio652/value

2. Configure the network port:

It is recommended to use systemd-networkd for network management; the configuration will not be lost after a reboot, and there will be no conflicts with other network tools. The steps are divided into two parts: "Temporary testing and verification" and "Permanent configuration solidification."

sudo systemctl enable --now systemd-networkd
sudo systemctl status systemd-networkd | grep -E 'active|error'

:::Note: Physical network ports correspond to virtual network port addresses: ETH0-eth0 ETH1-eth4 ETH2-eth3 ETH3-eth2 ETH4-eth1 :::

3. Using eth1 as an example, where the IP camera's IP address is 10.0.3.200, the network port configuration method is as follows:

• Temporarily configure IP:

# Clear existing IP on eth1 to avoid conflicts
sudo ip addr flush dev eth1
 
# Shut down the port and reconfigure
sudo ip link set eth1 down
sudo ip addr add 10.0.3.10/24 dev eth1
sudo ip link set eth1 up

# Verify IP configuration (should display inet 10.0.3.10/24)
ip addr show eth1 | grep inet

# Test connectivity with the camera (0% packet loss indicates normal status)
ping 10.0.3.200 -I eth1 -c 3

• Permanently Configure IP:

# Create the eth1 configuration file
sudo nano /etc/systemd/network/eth1.network
 
[Match]
Name=eth1 # Matches the interface name; replace if the actual name differs (e.g., enx00e04c68xxxx)

[Network]
Address=10.0.3.10/24 # Static IP and subnet mask
DHCP=no # Disable DHCP auto-acquisition
IPv6AcceptRA=no # Disable IPv6 to reduce interference

#[Link]
NamePolicy=kernel database onboard slot path # Maintain stable interface naming

• Save and exit: Press Ctrl+O → Enter to confirm → Press Ctrl+X.

Other network ports are configured in the same way, supporting up to 4 IP cameras mounted simultaneously. Example of four IP camera configurations, using the relationships in the following table:

| Ethernet Port | Corresponding Camera IP | Development Board Static IP | Camera Username and Password| | eth1 | 10.0.3.200 | 10.0.3.10 | admin & c32bdc3e| | eth2 | 10.0.2.200 | 10.0.2.10 | admin & c32bdc3e| | eth3 | 10.1.4.200 | 10.1.4.10 | admin & 9c7d1f96| | eth4 | 10.1.1.200 | 10.1.1.1 | admin & c32bdc3e | Follow the steps above to configure each network segment :

# ========== Batch Temporary Configuration for eth1-eth4 and Connectivity Testing ==========

# eth1 (Corresponding to camera 10.0.3.200)
sudo ip addr flush dev eth1
sudo ip link set eth1 down
sudo ip addr add 10.0.3.10/24 dev eth1
sudo ip link set eth1 up

# eth2 (Corresponding to camera 10.0.2.200)
sudo ip addr flush dev eth2
sudo ip link set eth2 down
sudo ip addr add 10.0.2.10/24 dev eth2
sudo ip link set eth2 up

# eth3 (Corresponding to camera 10.1.4.200)
sudo ip addr flush dev eth3
sudo ip link set eth3 down
sudo ip addr add 10.1.4.10/24 dev eth3
sudo ip link set eth3 up

# eth4 (Corresponding to camera 10.1.1.200)
sudo ip addr flush dev eth4
sudo ip link set eth4 down
sudo ip addr add 10.1.1.1/24 dev eth4
sudo ip link set eth4 up

# Verify IP configuration for all ports (should display the static IP for each port)
echo -e "\n==== IP Configuration Status for Each Port ===="
ip addr show | grep -E 'eth[1-4]|inet '

# Test connectivity with all cameras (0% packet loss indicates normal status)
echo -e "\n==== Connectivity Test for Each Camera ===="
ping 10.0.3.200 -I eth1 -c 3
ping 10.0.2.200 -I eth2 -c 3
ping 10.1.4.200 -I eth3 -c 3
ping 10.1.1.200 -I eth4 -c 3

Then use VLC for access:

vlc rtsp://admin:[email protected]/h264/ch1/main/av_stream --no-one-instance &
vlc rtsp://admin:[email protected]/h264/ch1/main/av_stream --no-one-instance &
vlc rtsp://admin:[email protected]/h264/ch1/main/av_stream --no-one-instance &
vlc rtsp://admin:[email protected]/h264/ch1/main/av_stream --no-one-instance

If you need to close all camera windows, execute the following command:

Tech Support & Product Discussion

Thank you for choosing our products! We are here to provide you with different support to ensure that your experience with our products is as smooth as possible. We offer several communication channels to cater to different preferences and needs.