Skip to main content

aim-family-started

description: "Official ArmSoM technical documentation for AIM Family User Manual. Find product specifications, configuration steps, usage guidance, and embedded development references." image: /img/armsom-social-card.png

AIM Family User Manual

Here’s the translation:

AIM User Manual: This manual helps users understand the basic usage of the AIM development kit and the necessary preparations. Start using your AI Module 🚀

Getting Started​

Before you start using the AIM development kit, please prepare the following items:

Tools Preparation​

  • Power supply
  • System Installation (Choose one)
    • Onboard eMMC boot
      • USB Type-C data cable: Write the image to the AIM development kit from the Type-C port. You will need a Type-C data cable to connect the AIM development kit to a PC.
    • MicroSD/TF card boot
      • MicroSD/TF card: Class 10 or above, at least 8GB SDHC, and a card reader.
      • The following are high-speed TF cards tested and verified by the ArmSoM team:
        • SanDisk 32GB TF (MicroSD) (Recommended for developers)
        • SanDisk 32GB TF (MicroSD) Dashcam & Security Surveillance Card (Recommended for long-term operation)
        • SanDisk TF 8G Class10 microSD
        • SanDisk TF 128G Class10 microSD XC TF 128G 48MB/S

You can set up the AIM development kit as an interactive desktop computer or a headless computer that can only be accessed via the network. To set up the AIM development kit as a headless computer, configure the hostname, user account, network connection, and SSH when installing the OS for the first time. If you want to use the AIM development kit directly, you will need the following additional accessories:

Optional Items

  • Keyboard & Mouse
  • HDMI monitor and HDMI cable
  • DP monitor and DP cable
  • Ethernet cable
  • Camera module
  • LCD display

Power Supply​

The table below shows the power specifications required to power the AIM development kit. You can use any high-quality power supply that provides the correct power mode.

ModelRecommended Power (Voltage/Current)Power Mode
AIM7 + AIM-IO5V/3A, 9V/2A, 12V/2A, 15V/2ADC adapter, 2.5mm
AIM5 + AIM-IO5V/3A, 9V/2A, 12V/2A, 15V/2ADC adapter, 2.5mm

Interface Usage​

The AIM development kit supports multiple system images, and you can choose the appropriate image to download according to your needs.

info

A system image includes the Linux kernel, basic programs, etc., which are essential for running the AIM development kit, so you need to install the image before running the product.

1. Debug Serial Port​

Connect a USB-to-TTL serial adapter as follows:

armsom-aimio-debug

armsom-aimio-debug
AIM-IOConnectionSerial adapter
GND (pin 11)--->GND
RX (pin 3)--->TX
TX (pin 4)--->RX

2. Ethernet​

  1. Connect one end of an Ethernet cable to the ArmSoM-AIM Ethernet port and the other to a router with a working network connection.
  2. After startup, DHCP automatically assigns an IP address to the Ethernet interface; no additional configuration is required.
  3. Use the following command on the ArmSoM-AIM Linux system to view the IP address:
root@armsom-aim7:/# ip a

You can find the IP address by connecting an HDMI display and running ip a, using the debug serial port, or viewing the router's administration page. If the board does not appear in the router, verify that Linux has booted, check or replace the Ethernet cable, and try another router if possible.

tip

DHCP address assignment on ArmSoM-AIM requires no additional setup.

Use ping to check network connectivity. Press Ctrl+C to stop it.

armsom@armsom-aim7:~$ ping www.baidu.com

3. HDMI​

ModelAIM7AIM5
Resolution8Kp604Kp120
  1. Connect ArmSoM-AIM to an HDMI display with an HDMI cable.
  2. After Linux starts, image output on the display confirms that HDMI is working.
tip

Most laptop HDMI ports support output only, not HDMI input. Before connecting the board's HDMI output to a laptop, confirm that the laptop supports HDMI input. If no image is displayed, make sure you are using a desktop image; server images provide terminal output only.

4. DisplayPort​

ModelAIM7AIM5
Resolution4Kp604Kp60
  1. Connect ArmSoM-AIM to a DisplayPort display with a DP cable.
  2. After Linux starts, image output on the display confirms that the DP interface is working.

5. USB​

ModelAIM7
USB1 × Type-C 2.0, 4 × USB 3.0
info

You can connect a USB hub to expand the number of USB ports.

Test a USB Mouse or Keyboard​

  1. Connect a USB keyboard or mouse to an ArmSoM-AIM USB port.
  2. Connect ArmSoM-AIM to an HDMI display.
  3. If you can operate the system with the keyboard or mouse, the USB port is working. A mouse requires a desktop image.

Test a USB Storage Device​

  1. Connect a USB flash drive or external USB disk to an ArmSoM-AIM USB port.
  2. The following command should display an sdX device when the drive is recognized:
armsom@armsom-aim7:/# cat /proc/partitions | grep "sd*"
  1. Mount the drive to view its files:
armsom@armsom-aim7:/# sudo mount /dev/sda1 /test/
  1. Use df -h to check capacity and the mount point.

USB Camera​

  1. Connect a USB camera that supports UVC to an ArmSoM-AIM USB port.
  2. Use v4l2-ctl --list-devices to identify the camera device node, such as /dev/video0.
  3. On a desktop image, open the camera with Cheese or V4L2 Test Bench. You can also preview, capture an image, or record video with GStreamer:
gst-launch-1.0 v4l2src device=/dev/video0 io-mode=4 ! videoconvert ! video/x-raw,format=NV12,width=1920,height=1080 ! xvimagesink

sige-usb-cam

sige-usb-cam

System Image Burning​

1. Obtaining the System Image​

Visit the Baidu Cloud resource page to obtain the system image: Baidu Cloud Link

tip
  1. The default account/password for the official image is armsom/armsom, root/root.
  2. The Debian system is adapted and compiled using the SDK provided by RK, making it more suitable for users with ISP, GPU, codec, and NPU needs. It can be burned to eMMC using RKDevTool or to an SD card using SDDiskTool.
  3. Ubuntu, Armbian, and OpenWrt are additional options provided by ArmSoM for open-source enthusiasts.

2. Burning Ubuntu, Armbian, OpenWrt Systems​

2.1. Burning to microSD using a Card Reader​

Burning the OS image to microSD via Etcher

This method is suitable for burning the system to an SD card and is available on Windows, macOS, and Linux x64 operating systems.

Preparation
1. A microSD card
2. An SD card reader
3. Download the Ubuntu/Armbian/OpenWrt system image for the respective product.
4. Insert the SD card into the SD card reader, then insert the SD card reader into the computer's USB port.

Burning the OS image to microSD via Etcher

  1. Download balenaEtcher from the balena official website, and select the appropriate host system. The Linux version is in AppImage format.

  2. Insert the MicroSD card into the MicroSD card reader.

  3. Open the Etcher window, first select "Flash from file," find the location where you downloaded the image, and double-click to select it.

balenaEtcher-flash-from-file

balenaEtcher-flash-from-file
  1. Then click "Select target" and choose the MicroSD card you want to burn.
  2. Click "Flash" and wait for the burning process to complete. This will take some time.
  3. Once the burning is successful, it will show as pictured below:

balenaEtcher-flash-success

balenaEtcher-flash-success
Burning Failed
1. On Windows, burning the image requires running "as administrator," and some Linux users may need to use the chmod command to make it executable.
2. If there is an error during the burning process, please try again.

Burning the OS image to microSD via Win32DiskImager

  1. Download the Win32DiskImager tool.
  2. Open Win32DiskImager.
  3. Click the folder icon button and then select the image you want to burn.
  4. After completing the above steps, click the "Write" button to start burning the image, then wait for the burning process to complete.

2.2. Burning to eMMC via USB Cable (Windows)​

2.2.1. Tool Acquisition and Installation​

Burning an image to eMMC requires using the RKDevTool and the RK Driver Assistant (DriverAssistant).

Click to enter the link: Baidu Cloud Link

baidu-flash-tool

baidu-flash-tool
2.2.2. Installing DriverAssistant​

Unzip the DriverAssistant software package and double-click DriverInstall.exe to enter the driver installation interface.

Click "Install Driver" to start installing the driver. If you are unsure whether a previous version of the driver was installed, first click "Uninstall Driver" to remove the old version, then click "Install Driver."

install-driver-assitant

install-driver-assitant
2.2.3. Installing RKDevTool​

RKDevTool is a dedicated USB burning tool for Rockchip, available on the Windows platform, which can be used to download system images to the product via the USB interface.

After unzipping the package, you can use it without installation. Double-click RKDevTool.exe to enter the software interface.

The software mainly has three sections: Download Image (burn image by address), Upgrade Firmware, and Advanced Functions.

2.1.4. Burning Image in MASKROM/Loader Mode​

This mode is suitable for products that have not yet been burned with a system or where the burned system is damaged and cannot run (suitable for all situations).

Open the RKDevTool burning tool and set the product to burn mode.

Entering Loader Mode

1. Prepare a Type-C cable for burning the image.
2. Disconnect all cables that might power the product, such as the power cable, USB cable, etc.
3. Use a Type-C cable to connect the product's OTG interface to a USB port on the computer, then open the RKDevTool software.
4. Short pin 10 (FC REC) and pin 9 (GND) on the 12-pin connector, then power the product via DC.
5. Wait for the software to prompt "Loader device found" (as shown below), then release the buttons.
6. If unsuccessful, repeat steps 2-5.

Entering MASKROM Mode

1. Prepare a Type-C cable for burning the image.
2. Disconnect all cables that might power the product, such as the power cable, USB cable, etc.
3. Use a Type-C cable to connect the product's OTG interface to a USB port on the computer, then open the RKDevTool software.
4. Short the solder points on the core board, then power the product via DC.
5. Wait for the software to prompt "Loader device found" (as shown below), then release the buttons.
6. If unsuccessful, repeat steps 2-5.

aim7-maskrom

aim7-maskrom

Start burning the system:

rkdevtool-install-emmc

rkdevtool-install-emmc
  1. Select the "Download Image" option.
  2. Confirm that the board has entered MASKROM/Loader mode.
  3. Click the blank cells to select the MiniLoaderAll and Image files to use. The corresponding MiniLoaderAll and Image files are stored on Baidu Cloud.
  4. In the "Storage" option, select the target medium "EMMC

3. Burning Debian System​

3.1. Using a Card Reader to Burn to microSD​

Installing SDDiskTool​

To burn the image to eMMC, use the SDDiskTool_<version>.exe tool.

Click the following link to access it: Baidu Cloud Link

baidu-SDDiskTool

baidu-SDDiskTool

After extracting the compressed file, you can use the software without installation. Simply double-click the SD_Firmware_Tool.exe file to open the tool.

Burning the Image​

Open the SDDiskTool executable file (SD_Firmware_Tool.exe) and insert the SD card.

First, select the correct SD card you want to burn. Then, set the function mode to SD Boot and choose the image you want to burn. Finally, click the "Create" button to start creating the bootable SD card.

SDDiskTool

SDDiskTool

Please be patient as the SD card is being burned. The larger the image, the longer the burning process will take.

Note
  1. If you encounter an error saying it cannot burn the image after clicking "Create," try closing the error window and starting the creation process again. If that doesn’t work, try formatting the SD card.
  2. The firmware downloaded from Baidu Cloud must be extracted before it can be loaded. On a Windows PC, you need to run the tool with administrator privileges.

3.2. Using a USB Cable to Burn to eMMC​

We will use the RKDevTool to burn the image and put the product into burning mode.

1. Prepare a Type-C cable for burning the image.
2. Disconnect all cables that might power the product, such as the power cord and USB cables.
3. Connect one end of the Type-C cable to the OTG port on the product and the other end to the USB port on the computer, then open the RKDevTool software.
4. Hold down the Recovery button and power the product using the DC supply.
5. Wait for the software to indicate that a LOADER device has been detected (as shown below), then release the button.
6. If unsuccessful, repeat steps 2-5.

recovery-flash-tool

recovery-flash-tool

maskroom-flash-tool

maskroom-flash-tool

The burning progress will be shown on the right. Once completed, the tool will notify you:

rkdevtool-success

rkdevtool-success
Troubleshooting Burning Failures

If you encounter a "Download Boot Fail" error or other errors during the burning process (as shown below), it is usually due to a poor USB connection, low-quality cables, or insufficient power from the computer’s USB port. Try replacing the USB cable or using a different USB port on the computer to troubleshoot.

What is the Difference Between Maskrom Mode and Loader Mode?
  • Maskrom Mode: When the Flash is not yet burned with firmware, the chip will enter Maskrom mode for the initial firmware burning. During development, if the Loader mode fails to start properly, Maskrom mode can also be used to burn the firmware.
  • Loader Mode: This mode is triggered during the uboot startup when a specific pin is pressed. In Loader mode, firmware burning and upgrading can be performed. You can also burn individual partition images for easier debugging.
ArmSoM

Build the next embedded product, faster.

Open hardware · System on modules · Single-board computers · Embedded Linux

Contact ArmSoM sales@armsom.org