Skip to main content

1. Google Drive resource introduction

ArmSoM organizes supporting resources by product on Google Drive, including hardware resources, software resources, system images and development tools, as well as read-before-use notes and quality inspection reports. Open your product's folder and read its instructions before downloading.

1.1 Resource overview​

These resources help you understand the hardware design, develop software, install an OS and debug the board. Start with the product's read-before-use notes, which cover power, connections and first-use precautions. Look in the corresponding folder for supporting files such as quality inspection reports.

Open ArmSoM Google Drive.

ArmSoM Google Drive product folders

Choose the folder for your product
Resource availability

Available resources, OS versions, desktop environments and tools vary by product. Refer to the files and notes in the corresponding product folder. The sections below describe resource categories; not every board provides every combination.

1.2 Hardware resources​

Hardware resources describe board interfaces, circuit connections and dimensions to help with peripheral connections, carrier board development and mechanical design.

ResourcePurpose
SchematicsCheck power circuits, interfaces and connections between components
Dimension drawings and DXF filesCheck board dimensions, mounting holes and connector positions
Hardware design filesReference product or development-kit designs; available formats depend on the folder contents
Datasheets for major componentsLook up chip functions, electrical specifications and interfaces

To view Allegro design files in Altium Designer, see Import Allegro PCB files.

1.3 Software resources​

Software resources primarily include development documentation and prebuilt system images for reference, OS installation and application deployment.

ResourcePurpose
Development documentationConsult chip vendor references, peripheral configuration instructions and software development guides for the product's platform
System imagesFlash to the board to run the system; see the next section for OS versions, desktop variants and filenames

1.4 System images​

System images contain a system built for a specific board. Confirm the product model before choosing an OS version and desktop variant.

1.4.1 OS versions​

SystemCommon versions or identifiersDescription
DebianDebian 11 / bullseye; Debian 12 / bookwormChoose from the versions available for your board according to application requirements; package versions differ
UbuntuUbuntu 22.04 LTS / jammyFor desktop or service applications using the Ubuntu software ecosystem
ArmbianArmbian and distribution details in the filename or notesBased on Debian or Ubuntu; see the product folder for versions and supported boards
AndroidAndroid and a version numberFor Android application and UI development; use a version provided for your board

For example, the Sige6 product documentation lists Debian 11, while CM5 and AIM7 list Debian 12 and Ubuntu 22.04. Download from your own product's folder.

1.4.2 Desktop and command-line variants​

The OS version and desktop environment are separate choices. For example, Debian 12 identifies the distribution, while XFCE identifies the desktop environment.

TypeCommon filename identifiersUse case
GNOME desktopgnomeUse graphical applications with a monitor, keyboard and mouse
XFCE desktopxfce / xfce4Use a lighter graphical desktop with lower resource requirements
Server / CLIserver / cliNo graphical desktop preinstalled; manage the board over serial or SSH and deploy services
Choosing a variant

For an HDMI desktop, graphical applications or video previews, choose a desktop image provided for your board. For services managed primarily over SSH, consider Server / CLI. Tutorials that use a desktop require a graphical environment, which a command-line image does not provide by default.

1.4.3 Identify image files​

Image filenames commonly include the product, OS version or codename, desktop environment, architecture and date. Naming varies by product; this historical filename illustrates the fields:

armsom-w3-debian-bullseye-xfce4-arm64-20231115
FieldMeaning
armsom-w3Target product: ArmSoM W3
debian-bullseyeDebian 11 (Bullseye)
xfce4XFCE graphical desktop
arm6464-bit ARM architecture
20231115Date in YYYYMMDD format: November 15, 2023

Extract archives as instructed in their accompanying notes. update.img is typically a firmware upgrade package, while rootfs.img is typically a root filesystem partition image. The .img extension alone does not identify the flashing method.

Match the image to the board

Check the product model, hardware revision and flashing instructions. Boards with the same SoC do not necessarily use interchangeable images. Do not flash a standalone rootfs.img as complete system firmware.

1.4.4 After downloading​

  1. Read the product folder's notes and confirm the board, OS version, desktop variant and target storage. If checksums are provided, verify the downloaded files.
  2. Use the appropriate flashing tools: see Flash a system image for Rockchip products, or the Sige6 product guide for Allwinner Sige6.
  3. Follow the product guide to connect, power on and log in to the board. See Check board system information to confirm the installed version.
  4. Before installing packages on Debian, Ubuntu or Armbian, see Update APT sources to check the network, system time and package sources.

1.5 Development tools​

Choose tools for your board's chip platform. These tools generally run on the computer connected to the board. Download only the tools needed for the operation you are performing.

1.5.1 Rockchip development tools​

ToolPurposeUse case
RKDevToolUpgrade partition images or complete firmwareFlash over USB from a Windows computer
RK Driver Assistant (DriverAssistant)Install Rockchip USB driversSet up a Windows computer for USB flashing
Linux_Upgrade_ToolUpgrade firmwareFlash over USB from a Linux computer
SD_Disk_ToolWrite compatible Rockchip firmware to SD cardsCreate boot or upgrade cards as described in the board's guide
FactoryToolFlash multiple USB devices for productionWrite firmware to boards in batches
Rockchip device identifier toolWrite identifiers such as serial numbers and MAC addressesConfigure device identities during production

1.5.2 Allwinner development tools​

The following list follows the Sige6 product documentation. Look for the tools in the Sige6 development-tools folder. The Phoenix flashing tools listed here run on Windows.

ToolPurposeUse case
PhoenixSuitUpgrade individual partitions or complete firmwareFlash Sige6 images to eMMC over USB
PhoenixCardCreate SD card firmwareCreate a Sige6 boot card, selecting the mode described in the product guide
PhoenixUSBproFlash multiple USB devices for productionWrite firmware to boards in batches
USB driver (InstallUSBDrv.bat)Allow Windows to recognize Allwinner USB flashing devicesInstall before using PhoenixSuit
Device identifier toolWrite device identification dataProduction configuration; follow the accompanying tool instructions

1.5.3 Common tools​

ToolPurposeUse case
ADB toolsRun debugging commands or transfer files on systems with ADB enabledAndroid or other images with an active ADB service
CH340 serial driverRecognize USB-to-serial adapters using a CH340 chipSerial debugging on Windows; other chips require their corresponding drivers
Serial terminal (such as MobaXterm)Read boot logs and access the command lineSerial debugging; MobaXterm also supports SSH connections
SDCardFormatterFormat SD cardsPrepare or reuse storage cards; it does not flash images
IP scannerFind device addresses on the local networkHelp locate a board whose IP address is unknown
Drivers and terminal software

USB flashing drivers and USB-to-serial drivers serve different purposes and are not interchangeable. A serial driver lets the computer recognize the adapter; a terminal application opens the serial port. Follow the board's documentation for wiring and baud rate.

Contact us