Working with mikroBUS on the RZ/G2LC HummingBoard

Owned by Mikhail Anikin
Last updated: May 05, 2024 by Yazan Shhady
4 min read

This guide will show you how to control the mikroBUS GPIOs, SPI, I2C, and UART from the RZ/G2LC HummingBoard Linux userspace.

Here is a microBUS connector pinout:

Choosing the pin function

According to the SOC specification, most pins can be used as GPIO or alternative function pins.

  • The pin P45_2 can be used as GPIO.

  • The pins P44_3, P44_0, P44_2, and P44_1 can be used as GPIOs by default. Enable the spi1 node in the devise tree to use them as SPI.

  • By default, the pins P41_0, P41_1, P40_1, and P40_0 are used as uart ttySC1. Disable the scif1 node in the devise tree to use them as GPIOs.

  • The pins P40_1, and P40_0 Can be used as CANFD RX/TX. Disable the scif1 node and enable canfd node in the devise tree to use them as CANFD.

  • I2C0_SCL and I2C0_SDA can’t be used as GPIOs, only as I2C pins.

GPIO

To use GPIO in Linux, either gpiod or sysfs can be used.

Both methods need the GPIO number that Linux assigned during the enumeration. This number is dynamically assigned to the GPIO based on the number of pins, GPIO controllers, etc. Usually, this number is stable, but it might change during the BSP updates. The gpioinfo utility gives us information about the number of the GPIO we need to use according to its label:

$ gpioinfo | grep P45_2 line 362: "P45_2" unused input active-high

In this example, the GPIO P45_2 has the number 362.

Setting GPIO using gpiod:

gpioset -m wait gpiochip0 362=1

Note: after exit, the gpioset utility will reset GPIO to its default state (input hi-z); for more info, read about gpioset modes.

Reading GPIO using gpiod:

gpioget gpiochip0 362

Setting GPIO using sysfs:

The export number of the GPIO can be calculated as the GPIO controller base plus the GPIO number.

The GPIO controller base is 120, and the GPIO number is 362.

The export number is 120 + 362 = 482

The GPIO number can be calculated using the function below:
XX = Linux gpio number = <GPIO_controll_base> + <GPIO_Bank> * 8 + <GPIO_Bit>
→ XX = 120 + <GPIO_Bank> * 8 + <gpio_bit>

Example: To calculate the GPIO number of mikroBus J8 [pin 2] (RST)
Pad Name: P45_2 → {GPIO_Bank= 45; GPIO_Bit = 2}

XX = 120 + ( 45) * 8 + 2 = 120 + 362 = 482

UART

UART is available in Linux as a standard serial device /dev/ttySC1.

To use it, you can use the default utilities:

You can also use Picocom, minicom, screen, etc.

CANFD

The CANFD RX/TX pins are available on P40_1 and P40_0. These pins conflict with SCIF1 RX/TX. To enable CANFD, the scif1 node needs to be disabled, and the canfd node needs to be enabled in the dts.

The CANFD will be available with the /dev/can0 interface.

Basic CAN usage:

Note: this CANFD controller supports a nominal bit rate: max. 1Mbps, data bit rate: max. 4Mbps

I2C

The I2C0_SCL and I2C0_SDA pins can be utilized as an I2C0 connection and are available via /dev/i2c-0.

New devices can be detected via the i2cdetect utility:

Options to control the device:

  • i2c-tools utilities

  • Add device to i2c0 node in the dts

  • Also possible that the kernel will bind the driver automatically during the i2c bus scan

SPI

The mikroBUS connector's SPI pins are connected to the SOC's SPI1 interface. To use them, configure the spi1 node in the dts first.

Depending on the task, the spi1 node can be configured as a specific or dummy SPI device.

Here is an example of the dummy device configuration:

After this configuration, the SPI would be accessible via the /dev/spidev0.0 device and can be used with the spidev_test utility or tools that can work with spidev (for example, flashrom).

To fully use SPI, replace the spidev node with a specific device node and use a particular driver.

 

SolidRun Ltd.