HummingBoard EU205 & RZ/G2L/G2LC SoM Quick Start Guide
Revision and Notes
Date
Owner
Revision
Notes
04/04/2025
Josua Mayer
0
draft
22/05/2025
Josua Mayer
1
Release (updated photos)
Purpose
This guide provides basic instructions for operating the SolidRun HummingBoard-EU205 with RZ-G2L SoM and booting into Linux. Advanced usage scenarios are covered by separate technical documentation.
Hardware Setup
Connections
12V DC Power Adapter (12V recommended, supports up to 48V)
Type-C USB Cable for serial console
microSD Card
Ethernet
Configuration Jumpers
for G2L SoM: J5016 (4 pieces), J5026, J5027
for G2LC SoM: J5017, J5015, J5024, J5018, J5026, J5027
Boot Select
Configure the boot-mode for microSD using onboard DIP switches S3 & S4:
G2L SoM
S3-1 (MD0)
S3-2 (MD1)
S4-1 (MD2)
S4-2 (SD_DEV_SEL)
microSD
0
0
0
0
eMMC
1
0
0
1
Serial Download
1
0
1
X
G2LC SoM
S3-1 (MD0)
S3-2 (MD1)
S4-1 (MD2)
S4-2 (SD_DEV_SEL)
microSD
0
0
0
1
eMMC
1
0
0
0
Serial Download
1
0
1
X
Note: 0 = OFF, 1 = ON, X = don't care.
Console
Start an application for serial console - such as PuTTY or tio. Configure it for baud rate 115200 and the COMx or ttyUSBy interface representing the micro-USB console connection. For details also see Serial Connection.
Note that the serial device only appears after powering up the board. On first use it is recommended to follow below procedure:
connect console cable
connect power
find and connect to COMx / ttyUSBy interface with terminal application
push in microSD
press reset button
Software Setup
Prepare bootable microSD Card
uncompress downloaded image file
write image file to microSD card to create a byte-for-byte copy. https://etcher.io/ is recommended, professionals may use unix “dd” command.
Attention: The SoM modules and carrier boards are programmed with critical identifying information, including the product name and SKU, stored in an EEPROMs at I2C bus 0, addresses 0x50 and 0x57. This data is structured according to the ONIE TLV standard and is essential for initializing the product and aligning the software accordingly. The tlv_eeprom command in U-Boot can be used to read this data. Important: If this information is deleted or becomes corrupted, it will impact the correct initialization and functionality of the product. In such cases, please contact SolidRun support for assistance.
First Steps with Buildroot reference system
Log-In
On power-on with valid software on microSD the system should automatically boot to a login prompt displayed on the serial console:
Log in with user-name “root”, password “root”.
Networking
Network interfaces are set to configure automatically using DHCP as soon as an ethernet link has been established.
ping, curl and wget are functional out of the box when connecting to a standard home network.
Show assigned IP:
Log-In via SSH
SSH Log-In is active by default using the same insecure username and password.
First Steps with Debian reference system
Log-In
On power-on with valid software on microSD the system should automatically boot to a login prompt displayed on the serial console:
Log in with user-name “root”, no password.
Networking
By default networking is not configured. For advanced or persistent configurations please refer to the Debian Documentation.
For connecting the first RJ45 port (next to power connector) using automatic configuration, execute:
Log-In via SSH
To log in via SSH, an ssh key must be installed first. Copy your favourite public key, e.g. from ~/.ssh/id_ed25519.pub, into a new file in the root users home directory at ~/.ssh/authorized_keys:
Advanced Steps with Debian/Buildroot reference system
Expand Root Filesystem
After flashing the root filesystem is smaller than the eMMC. To utilize all space, resize both the rootfs partition - and then the filesystem:
inspect partitions:Using fdisk, view the current partitions. Take note of the start sector for partition 2!
resize partition 2:Drop and re-create partition 2 at the same starting sector noted before, keeping the ext4 signature when prompted and re-adding the bootable flag:
resize root filesystem:Linux supports online-resizing for the ext4 filesystem. Invoke
resize2fson partition 1 to do so:
Install to eMMC
eMMC and microSD are not usable at the same time but selected first by boot-select switches and then by software during boot.
Installation of software to the eMMC requires a special procedure:
Download a prebuilt sdcard image based on either Buildroot and create a bootable microSD card.
Format a USB flash drive with FAT32 (or ext4), and place on it the images that are to be installed to the eMMC, both Bootloader and OS - e.g.: -
rzg2l-solidrun-sd-debian-<hash>.img.xz-rzg2l-solidrun-mmc-bootloader-<hash>.imgInsert microSD, set boot-select switches for microSD, then power-on the board and stop in u-boot at the timeout prompt by pressing any key:
Select eMMC and boot into a small rootfs in initramfs:
Quickly type the number “2”, then press return:
Log-in with user “root”, password “root”
Confirm eMMC is available:
When the list includes “mmcblk0boot0” eMMC has been selected successfully. 7. Connect USB flash drive, then find the images and install them to eMMC:
power-off the board, remove microSD and change boot select switches for eMMC.
On next power-on the system will boot from eMMC.
Accessing Sensors, Ports and Peripherals
See below some minimal examples making use of various board features:
RGB LED
The 3-colour LED D7 is controlled using the Linux LED Framework. Each colour is controlled separately supporting On, Off and triggers. E.g.:
Accelerometer
The accelerometer is using the Linux IIO Framework. Sensor data can be accessed using libIIO.
Temperature / Humidity Sensor
The temperature and humidity sensor has no Linux driver at this time. Sensor data can be read out from userspace 2ith i2c cli utilities:
For further information see HS4003 product page.
Ambient Light Sensor
The light sensor has no Linux driver at this time. Sensor data can be read out from userspace with i2c cli utilities:
For further information see ISL76683 product page.
Air Quality Sensor
The ZMOD4410 has no Linux driver at this time. See ZMOD4410 and ZMOD4410 Evaluation Kit product pages for further information. The device responds on I2C Bus 0 at chip address 0x32.
GPS
UART
Note: Available only with G2L SoM
Raw NMEA records can be accessed directly via /dev/gnss0 device:
Alternatively for a more friendly UI the gpsd package and its utilities may be used after configuring it to use /dev/gnss0 at 38400 baud (see e.g. /etc/default/gpsd).
I2C
Note: Available only with G2LC SoM
There is no Linux driver for I2C interface of U-Blox MIA-M10Q. Data may be polled at bus 1 chip 0x42 address 0xFD-0xFE (length) and 0xFF (data). The access protocol should be implemented in a kernel driver as a single transaction must read 0xFD-0xFE plus N additional bytes or abort with a NAK.
For details see MIA-M10Q Integration Manual.
RS485
A Half-Duplex (2-wire) RS485 is available on J26-2 (A), J26-1 (B).
Normally the host should automatically switch the transceiver between RX and TX as needed, i.e. RX normally and TX while transmitting data. This is not (currently) supported by the Renesas G2L/C Linux uart driver, users must switch manually from userspace:
Acquire TX/RX control GPIO:
Set UART speed as needed:
Transmit a message:
Receive messages:
CAN
Note: Available only with G2L SoM
Two full-duplex CAN interfaces are available on J26: J26-12 (CAN0H), J26-14 (CAN0L), J26-11 (CAN1L), J26-13 (CAN1H)
configure interface:
Transmit a message:
Receive messages:
For second interface substitute can0 with can1.
Digital IO
Two digital inputs and two digital outputs operating at externally supplied voltage are available on J26: J26-5 (DIG_IN1), J26-7 (DIG_IN2), J26-6 (DIG_OUT1), J26-8 (DIG_OUT2)
The signals can be accessed using libgpiod example utilities:
Note: The inputs are inverting, i.e. reading a 1 means logical 0 on the line.
WiFi
The Linux driver for DA16200 WiFi does not load automatically, but must be loaded manually after boot:
After unblocking with rfkill the new wlan0 interface is operated like any standard Linux wifi device, see e.g. the Debian WiFi/HowToUse page.
Bluetooth
The DA14531 Bluetooth module is available by default as hci0 and may be used after unblocking using the standard bluez stack, e.g.:
LTE NB-IoT/M1 Cellular Modem
The LTE Module is not currently supported by ModemManager. Instead it should be operated manually or scripted using AT commands.
Access AT Interface
The AT interface is available at /dev/ttySC2 with hardware flow-control at 1843200 baudrate. It can be accessed using any serial terminal, for example picocom:
By default commands are not echoed but the terminal can be configured into a nicer mode with echo, auto-complete and history by executing AT+SMART=1.
To leave picocom press ctrl+a, then ctrl+x.
SIM Select
The Board supports either physical SIM via connector J3, and a soldered-on eSIM. The modem can switch between them using AT commands:
Cat-M1 / NB-IoT Select
The LTE module supports both Cat-M1 and NB-IoT. The choice is made in modem power-off state (AT+CFUN=0) using AT command AT+SQNMODEACTIVE (value 1 = LTE-M, value 2 = NB-IoT) followed with reset:
Automatic Power-On
Normally the modem radio stays off after boot (CFUN=0). It can be reconfigured for connecting to a network automatically (CFUN=1) using AT commands:
DATA Connection
Create file /etc/ppp/options:
Create file /etc/chatscripts/connect:
Create file /etc/chatscripts/disconnect:
Ensure the modem is registering to a network, i.e. AT+CFUN=1 or automatic power-on above.
Finally execute ppp application to connect:
Note: pppd version 2.5.2 or later is required, older versions can' t cope with the non-standard
1843200baudrate (“speed 1843200 not supported“).
CLPD Motor Driver (SLG47115)
Note: I2C Interface available only with G2LC SoM
The SLG47115 has no Linux driver at this time and comes unprogrammed. It responds on I2C Bus 1 at chip address 0x00.
For further information see SLG47115 product page.
Last updated