Table of Contents

• 1. Introduction

• 2. What You Need

• 3. Flash the SD Card

• 4. Hardware Setup

• 5. First Boot

• 6. Network Access

• 7. Camera Preview (IMX219)

• 8. 40-Pin Expansion Header

• 9. Common Issues & Tips

1. Introduction

1.1 About MO-62A

MO-62A is a single-board computer designed for edge AI inference, machine vision, and industrial control applications. It is powered by the TI AM62A7 processor — a quad-core Arm Cortex-A53 SoC with a dedicated MMA (Matrix Multiplication Accelerator) delivering up to 2 TOPS of AI inference performance.

1.2 Key Specifications

1.3 Board Layout

2. What You Need

The following items are required to get started:

The following items are optional but useful:

3. Flash the SD Card

3.1 Download the Image

Download the latest pre-built SD card image from the release page, The image is distributed as a .img.zip file.

The full SDK source code (kernel, device tree, filesystem customisation) is available at:

GitHub: https://github.com/inhandnet/mo-62a

3.2 Flash with balenaEtcher (Windows)

1. Download and install balenaEtcher.
   

2. Click Flash from file.
   

3. Select the downloaded .img.zip file.
   

4. Click Select target.

5. Choose the Micro SD card from the device list.

6. Click Flash! to start writing.

7. Wait until Flash Complete! is shown, then safely remove the SD card.

Warning: All existing data on the SD card will be erased.

4. Hardware Setup

1. Insert the SD card — push the flashed Micro SD card into the card slot on the underside of the board until it clicks.

2. Connect the display — plug a Micro HDMI cable into the board and connect the other end to your monitor.

3. Connect Ethernet — plug an RJ45 cable into the Gigabit Ethernet port for network access.

4. Connect peripherals — attach a USB keyboard and mouse to any of the four USB 2.0 Type-A ports (optional).

5. Connect the camera — if using an IMX219, connect the FPC ribbon cable to the 22-pin CSI connector (see Section 7).

6. Apply power — connect the USB Type-C power supply last. The red Power LED will illuminate immediately.

5. First Boot

5.1 Boot Sequence

After power is applied, the board boots from the Micro SD card. A normal boot takes approximately 30–45 seconds. The green Activity LED will blink during boot.

Note — First Boot: On the very first boot, the system automatically expands the root filesystem to fill the SD card. This takes an additional 1–2 minutes, after which the board reboots automatically. The desktop will appear after the second boot completes. Subsequent boots are normal speed.

Expected sequence:

1. U-Boot SPL (R5) → U-Boot (A53) — brief console output

2. Linux kernel decompresses and loads device tree

3. systemd brings up services — on first boot, filesystem expansion runs here and triggers an automatic reboot

4. XFCE desktop appears on the HDMI display

5.2 Desktop Login

The XFCE desktop loads automatically. Default credentials:

First login only: The default password is valid for one login. You will be prompted to set a new password immediately after logging in. The new password takes effect right away.

5.3 Serial Console (UART0 Debug Port)

If no display is available, the board can be accessed via the 3-pin UART0 debug connector (SH1.0, 1.0 mm pitch).

Serial settings: 115200 baud, 8N1, no flow control

# Linux host example (replace /dev/ttyUSB0 with your adapter's device node)
minicom -D /dev/ttyUSB0 -b 115200

6. Network Access

6.1 Wired Ethernet

The board obtains an IP address via DHCP automatically on boot.

6.2 Find the Board's IP Address

From the XFCE desktop terminal:

ip addr show eth0

From a host on the same network (if mDNS is enabled):

ping mo-62a.local

6.3 SSH Login

ssh debian@<board-ip>
# or
ssh debian@mo-62a.local

6.4 Wi-Fi Setup

Connect to a Wi-Fi network using nmcli:

# List available networks
nmcli device wifi list

# Connect to a network
nmcli device wifi connect "SSID" password "password"

Alternatively, use the XFCE network manager applet in the system tray.

Note: A U.FL antenna connector is provided on the board. Attaching an external antenna significantly improves wireless range.

7. Camera Preview (IMX219)

The MO-62A supports the IMX219 CSI camera module (Sony IMX219) via the 22-pin FPC CSI connector.

7.1 Connect the Camera

1. Gently lift the FPC connector latch on the CSI port.

2. Insert the ribbon cable with the contacts facing the board (metal contacts down).

3. Press the latch down to lock the cable.

7.2 Run the Preview

The imx219-preview.sh script is pre-installed at /usr/local/bin/imx219-preview.sh.

# Basic preview at 15 fps (default)
sudo imx219-preview.sh

# Preview at 30 fps
sudo imx219-preview.sh 30

# Low-light mode (maximum gain and exposure at 5 fps)
sudo GAIN=232 imx219-preview.sh 5

The preview displays live video on the HDMI output. Press Ctrl+C to exit.

Note: The script requires root (sudo) because kmssink needs DRM master access. Any running desktop session (lightdm) is stopped automatically while the preview is running and restarted on exit.

7.3 Tuning Options

Example — warmer white balance at 10 fps:

sudo WB_R=0.4 WB_B=0.5 imx219-preview.sh 10

8. 40-Pin Expansion Header

The 40-pin expansion header provides GPIO signals at 3.3 V logic levels. All user-accessible signal pins default to GPIO mode. Optional peripheral functions (I2C, SPI, UART, PWM) can be enabled via device tree overlay.

Note: Pins 27/28 (I2C2) are permanently assigned to the internal I2C bus used by the camera module and cannot be used as general GPIO.

8.1 Pin Map

See the complete 40-pin table in Section 8.2 below.

8.2 Linux GPIO Reference

All 40 pins are listed below. Use gpioset / gpioget from the gpiod package for GPIO-mode pins.

gpiochip0 = mcu_gpio0 (MCU domain). gpiochip1 = main_gpio0 (GPIO0_x). gpiochip2 = main_gpio1 (GPIO1_x).

8.3 Voltage Levels

All expansion header I/O pins operate at 3.3 V. Do not connect 5 V signals directly to GPIO pins.

8.4 Quick Examples

The board ships with libgpiod v2.x. The -c flag is required to specify the chip.

List all GPIO chips:

gpiodetect

Read a GPIO input (example: Pin 11 / BCM GPIO23 → gpiochip2 line 23):

gpioget -c gpiochip2 23
# Output: "23"=active  (active = high, inactive = low)

Read multiple pins at once:

gpioget -c gpiochip1 39 42
gpioget -c gpiochip2 23
# Output: "39"=active "42"=active

Drive a pin high and hold (example: Pin 7 / BCM GPIO4 → gpiochip1 line 39):

# Run in the background — the pin stays driven until the process is killed
gpioset -c gpiochip1 39=1 &

# Release the pin (restores to input)
pkill gpioset

Drive a pin for a fixed duration, then release:

# Hold high for 2 seconds, then exit automatically
gpioset --hold-period=2s -c gpiochip1 39=1

Toggle a pin repeatedly (example: 500 ms high → 500 ms low → exit):

gpioset -t 500ms,500ms,0 -c gpiochip1 39=1

Monitor pin edges (example: Pin 11 → gpiochip2 line 23):

gpiomon -c gpiochip2 23           # both edges
gpiomon --edges=rising -c gpiochip2 23

Scan I2C2 bus (pins 27/28, /dev/i2c-2):

i2cdetect -y 2

PWM on pin 32 (BCM GPIO12 → pwmchip0 channel 0), 1 kHz, 50% duty cycle:

# Export channel 0
echo 0 | sudo tee /sys/class/pwm/pwmchip0/export

# Set period 1 ms = 1000000 ns
echo 1000000 | sudo tee /sys/class/pwm/pwmchip0/pwm0/period

# Set duty cycle 500 µs = 500000 ns
echo 500000 | sudo tee /sys/class/pwm/pwmchip0/pwm0/duty_cycle

# Enable
echo 1 | sudo tee /sys/class/pwm/pwmchip0/pwm0/enable

9. Common Issues & Tips

Screen Stays Blank After Boot

The image ships with DPMS (display power management) disabled by default. If the screen goes blank, press any key or move the mouse to check whether the display manager is still running. If the issue persists, verify:

cat /etc/X11/xorg.conf.d/10-no-dpms.conf
grep xserver-command /etc/lightdm/lightdm.conf

Camera Not Detected

# Check that the CSI capture device is present
v4l2-ctl --list-devices

# Check media pipeline topology
media-ctl -d /dev/media0 --print-topology

If the camera is not listed, verify that the FPC cable is fully seated in the connector and the latch is locked.

SD Card Not Found at Boot

• Ensure the SD card is fully inserted (it should click into place).

• Try a different card. Cards smaller than 16 GB or slower than Class 10 may not work reliably.

• Re-flash the image and verify the write completed without errors.

Wi-Fi Antenna

The on-board U.FL connector requires an external antenna for reliable Wi-Fi performance. Without an antenna, range will be very limited.