Skip to main content

ArmSoM-CM1 and CM1-IO Development Kit

Product Introduction​

ArmSoM-CM1 is a computer-on-module (COM) based on the Rockchip RK3506J (tri-core Cortex-A7 + single-core Cortex-M0). It features a rich set of peripheral interfaces such as SAI, USB2 OTG, RMII, and CAN. This module meets minimum system requirements and includes an onboard Type-C power & programming port, MIPI DSI display interface, and an SD card expansion slot.

The ArmSoM-CM1 Kit consists of the CM1 module paired with the CM1-IO carrier board, offering even richer peripheral resources: dual 10/100 Ethernet ports, dual USB2.0 Host ports, onboard WiFi, MIPI DSI display interface, headphone jack, microphone input, and 72 GPIOs routed from the core module.

CM1 module and development kit
CM1 module and development kit · Click to view image

The ArmSoM-CM1 Kit development suite provides full-stack Linux system development documentation and open-source software resources. Enterprise customers can directly purchase the core module for end-product development. ArmSoM delivers complete system source code (including kernel customization patches, peripheral drivers, and toolchains) as open-source hardware, significantly accelerating customer product development cycles.

To maximize enterprise development efficiency and shorten R&D cycles, we systematically integrate the following full lifecycle development resources for core module users:

​1. Hardware Design Assets

  • Core Module / Carrier Board Reference Schematics (including high-speed signal integrity design guidelines)
  • Mechanical Structure 3D Models (STEP format)
  • Key Component Footprint Libraries
  • Industrial Connector Specifications and Interface Definition Manuals

​2. Software Delivery Suite

  • Pre-validated Factory System Images (Built with Buildroot)
  • Cross-compilation Toolchain
  • Board Support Package (BSP) & Device Tree Configuration Templates
  • Modular Peripheral Driver Development Framework

Application Areas​

The RK3506J finds wide application across various fields, including industrial control, smart appliance display control, HMI (Human-Machine Interface), and industrial information & data processing.

Hardware Information​

CM1 Hardware Interfaces​

CM1 module interfaces
CM1 module interfaces · Click to view image

CM1 Hardware Specifications​

CategorySpecificationCategorySpecification
SOC
  • RockChip RK3506j
  • CPU
  • RK3506 Tri-core Cortex-A7 Processor & single-core Cortex-M0
  • GPU
  • 2D Graphic Engine
  • Integrated High-Performance 2D Acceleration Hardware
  • Memory
  • 256/512MB DDR3L
  • Storage
  • 256/512MB NAND Flash
  • Supports MicroSD Card Expansion
  • Video Output
  • 1 x MIPI DSI (2Lane, 1.5Gbps)
  • 40-PIN & 44-PIN
  • Exposes all remaining functions of the RK3506J chip
  • Buttons
  • 1x Maskrom Key (for entering maskrom programming mode)
  • Power Supply
  • Type-C 5V
  • OS Support
  • Officially supported by Rockchip: Buildroot
  • Dimensions
  • 70 mm x 42mm
  • Operating Temperature
  • -40°C ~ 85°C
  • CM1-IO Hardware Interface​

    ArmSoM CM1-IO

    ArmSoM CM1-IO

    CM1-IO Hardware Specifications​

    CategorySpecificationCategorySpecification
    40-PIN & 44-PIN Female Header
  • Expands remaining core module functions
  • 40-PIN Header
  • Partially pin-compatible with Raspberry Pi 40pin for connecting rich accessory peripherals
  • Supports UART/SPI/I2C/I2S/PWM/5V Power/3.3V Power
  • USB Interfaces
  • 1 × Type C (Power & Programming Only)
  • 2 × USB2.0 HOST
  • Networking
  • 2 × 10/100 Ethernet Ports
  • 1 × WiFi5/BT4.2
  • Audio
  • 1 × Audio Jack (Headphone/Mic)
  • 12-PIN Header
  • Supports RS485/CAN/MICIN/SPK
  • Power Supply
  • Type-C 5V
  • DC 12V Jack
  • OS Support
  • Officially supported by Rockchip: Buildroot
  • Dimensions
  • 100 mm x 70mm
  • Operating Temperature
  • -40°C ~ 85°C
  • RK3506j Block Diagram​

    RK3506j Block Diagram
    rk3506j block diagram

    Pin Definitions​

    40-PIN Header
    GPIO NumberFunctionPinPinFunctionGPIO Number
    +3.3V
    1
    2
    +5.0V
    4RM_IO4/SAI0_SDI0/GPIO0_A4_d
    3
    4
    +5.0V
    5RM_IO5/SAI0_SDI1/GPIO0_A5_d
    5
    6
    GND
    59DSMC_SLV_RDYN/RM_IO31/UART5_RX_M1
    FLEXBUS0_D0/DSMC_CSN3/VO_LCDC_D0
    GPIO1_D3_d
    7
    8
    UART0_TX
    RM_IO22/JTAG_TCK_M1/GPIO0_C6_u
    22
    GND
    9
    10
    UART0_RX
    RM_IO23/JTAG_TMS_M1/GPIO0_C7_u
    23
    58DSMC_SLV_CSN0/RM_IO30/UART5_TX_M1
    FLEXBUS0_D1/DSMC_CSN2/VO_LCDC_D1
    GPIO1_D2_d
    11
    12
    GPIO1_D1_d/DSMC_SLV_D7
    RM_IO29UART5_RTSN_M1/DSM_AUD_LP_M0
    FLEXBUS0_D2/DSMC_DQS1/VO_LCDC_D2
    57
    52DSMC_SLV_D2/FLEXBUS0_D7
    DSMC_D11/VO_LCDC_D7
    GPIO1_C4_d
    13
    14
    GPIO1_C5_d
    DSMC_SLV_D3/FLEXBUS0_D6
    DSMC_D12/VO_LCDC_D6
    53
    51DSMC_SLV_D1/RM_IO28/SAI2_SDO_M1
    FLEXBUS1_CSN_M5/FLEXBUS0_D8
    DSMC_D10/VO_LCDC_D8
    GPIO1_C3_d
    15
    16
    GPIO1_C2_d
    DSMC_SLV_D0/RM_IO27SAI2_SDI_M1
    FLEXBUS0_CSN_M5/DSM_AUD_RP_M0
    FLEXBUS0_D9/DSMC_D9/VO_LCDC_D9
    50
    +3.3V
    17
    18
    GPIO1_C1_d/DSMC_SLV_DQS0/SAI2_MCLK_M1
    FLEXBUS1_CSN_M4/DSM_AUD_RN_M0
    FLEXBUS0_CLK/DSMC_D8/VO_LCDC_D10
    49
    48DSMC_SLV_CLK/FLEXBUS0_CSN_M4
    DSMC_INT1/FLEXBUS1_CLK
    DSMC_RESETN/VO_LCDC_D11
    GPIO1_C0_d
    19
    20
    SARADC_IN2/GPIO4_B2_z138
    46FLEXBUS0_CSN_M3/FLEXBUS0_D11
    FLEXBUS1_D14/DSMC_CSN0
    VO_LCDC_D13/GPIO1_B6_d
    21
    22
    GPIO1_B7_d
    FLEXBUS1_CSN_M3/FLEXBUS0_D10
    FLEXBUS1_D15/DSMC_RDYN/VO_LCDC_D1
    47
    44FLEXBUS0_CSN_M2/FLEXBUS0_D13
    FLEXBUS1_D12/DSMC_D6
    VO_LCDC_D15GPIO1_B4_d
    23
    24
    GPIO1_B5_d
    FLEXBUS1_CSN_M2/FLEXBUS0_D12
    FLEXBUS1_D13/DSMC_D7/VO_LCDC_D14
    45
    GND
    25
    26
    GPIO1_B3_d
    RM_IO26/SAI2_LRCK_M1FLEXBUS1_CSN_M1
    FLEXBUS0_D14/FLEXBUS1_D11
    DSMC_INT3/VO_LCDC_D16
    43
    41RM_IO24/UART5_CTSN_M1
    FLEXBUS1_CSN_M0/FLEXBUS1_D9
    DSMC_CSN1/VO_LCDC_D184
    GPIO1_B1_d
    27
    28
    GPIO1_B2_d
    RM_IO25/SAI2_SCLK_M1FLEXBUS0_CSN_M1
    FLEXBUS0_D15/FLEXBUS1_D10
    DSMC_INT2/VO_LCDC_D17
    42
    40FLEXBUS0_CSN_M0/FLEXBUS1_D8
    DSMC_D5/VO_LCDC_D19
    GPIO1_B0_d
    29
    30
    GND
    38FLEXBUS1_D6/DSMC_D3
    VO_LCDC_D21/GPIO1_A6_d
    31
    32
    GPIO1_A7_d/FLEXBUS1_D7
    DSMC_D4/VO_LCDC_D20
    39
    37FLEXBUS1_D5/DSMC_D2VO_LCDC_D22
    GPIO1_A5_d
    33
    34
    GND
    35FLEXBUS1_D3/DSMC_D0/VO_LCDC_CLK
    GPIO1_A3_d
    35
    36
    GPIO1_A4_d/FLEXBUS1_D4
    DSMC_D1/VO_LCDC_D23
    36
    33DSMC_SLV_INT/DSMC_INT0
    FLEXBUS1_D1/DSMC_CLKN
    VO_LCDC_VSYNC/GPIO1_A1_d
    37
    38
    GPIO1_A2_d/FLEXBUS1_D2
    DSMC_DQS0/VO_LCDC_HSYNC
    34
    GND
    39
    40
    GPIO1_A0_d/FLEXBUS1_D0
    DSMC_CLKP/VO_LCDC_DEN
    32
    12-PIN Header
    PinAssignmentDescriptionPinAssignmentDescription
    1RS485_ARS485 Differential Signal (+)2RS485_BRS485 Differential Signal (-)
    3CAN_LCAN Bus Differential Signal (Low)4CAN_HCAN Bus Differential Signal (High)
    5GNDSystem Ground6VBAT_RTCRTC Real-time Clock Battery Input
    7MICIN_PMicrophone Input (+) (Differential)8MICIN_NMicrophone Input (-) (Differential)
    9MICIN_PMicrophone Input (+) (Alternate Channel)10MICIN_NMicrophone Input (-) (Alternate Channel)
    11SPK_PSpeaker Output (+) (Differential)12SPK_NSpeaker Output (-) (Differential)

    FLEXBUS​

    FLEXBUS Correspondence
    J8002 pinAssignmentGPIO numberFlexBUS0
    1~8DSMC_* / FLEXBUS1_D0~D7GPIO1_A0~A7Input only
    9DSMC_D5 / FLEXBUS1_D8GPIO1_B0FLEXBUS0_CSN_M0
    11CAN1_TX / FLEXBUS1_D10GPIO1_B2FLEXBUS0_D15
    12~16CAN1_RX … DSMC_RDYNGPIO1_B3~B7FLEXBUS0_D14~D10
    18DSM_AUD_RNGPIO1_C1FLEXBUS0_CLK
    19DSM_AUD_RPGPIO1_C2FLEXBUS0_D9
    20~24MIPI_DSI_TE ~ RMII1_RSTnGPIO1_C3~C7FLEXBUS0_D8~D4
    25USB20_OTG1_DRV_HGPIO1_D0FLEXBUS0_D3
    26UART4_RTSNGPIO1_D1FLEXBUS0_D2
    27UART4_RXGPIO1_D2FLEXBUS0_D1
    28UART4_TXGPIO1_D3FLEXBUS0_D0

    We’ve always believed that the best products come from deep conversations with users. Thanks to a practitioner in our open-source community who keenly spotted areas for improvement in our ArmSoM-CM1 documentation and proactively built the ArmSoM CM1 — Claude Code plugin for us, making it easier for users to clearly understand the FLEXBUS mapping in ArmSoM-CM1.

    Development Resources​

    SDK Source Code​

    Official Images​

    The ArmSoM team uses Buildroot as the foundation for the official CM1 operating system. How to flash the system image?📤

    The following systems have been tested and validated by ArmSoM:

    Cloud Drive Address:

    Google Drive link
    logoDescriptionDownload
    buildrootbuildroot for CM1:
    Linux Kernel 6.1, support RT-Thread 4.1,
    support bare metal programs, support multi-core heterogeneous AMP,
    Preempt-RT/Xenomai real-time patches,
    lightweight UI framework LVGL.
    Google Drive root folder

    Hardware Resources​

    Get CM1 Schematics, DXF files, and other hardware resources.

    Google Drive link

    User Manual​

    Before starting to use CM1-IO, please prepare the following items.

    tip

    The following text uses CM1 Kit to represent CM1+CM1-IO

    Tool preparation​

    • 5/12v power supply
    • system installation
      • Onboard NAND startup
        • USB Type-C data cable, write the image from the Type-C port to the CM1 kit, you need a Type-C data cable to connect the CM1 kit and PC.
      • MicroSD card/TF card startup

    Optional Options

    • USB to serial port conversion
    • Ethernet
    • LCD display screen
    • audio cable

    Selection of burning method​

    Interface usage​

    If you are using the CM1 Kit for the first time, please familiarize yourself with each product's hardware interface.

    Debug port​

    CM1-IO USB to TTL serial connection

    Connect the USB to TTL serial cable as shown below:

    CM1-IOconnectport
    GND (pin 6)--->GND
    TX (pin 8)--->RX
    RX (pin 10)--->TX

    PC can also connect to Type-C interface for adb debugging

    gmac​

    1. Firstly, insert one end of the Ethernet cable into the Ethernet interface of the CM1 Kit, connect the other end of the cable to the router, and ensure that the network is unobstructed
    2. After the system is started, it will automatically assign an IP address to the Ethernet card through DHCP, without any other configuration required
    3. The command to view IP addresses in the Linux system of CM1 Kit is as follows
    root@armsom:/# ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    2: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
    link/can
    3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 16:b1:42:f4:f6:69 brd ff:ff:ff:ff:ff:ff
    4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 32:81:2f:73:98:c8 brd ff:ff:ff:ff:ff:ff
    5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether cc:64:1a:61:e9:b5 brd ff:ff:ff:ff:ff:ff
    1. Use the ping tool to determine if the network is connected.

    The command to test network connectivity is as follows. The ping command can be interrupted by pressing Ctrl+C shortcut key

    root@armsom:~$ ping www.baidu.com
    PING www.a.shifen.com (183.2.172.185): 56 data bytes
    64 bytes from 183.2.172.185: icmp_seq=0 ttl=53 time=8.370 ms
    64 bytes from 183.2.172.185: icmp_seq=1 ttl=53 time=8.917 ms
    64 bytes from 183.2.172.185: icmp_seq=2 ttl=53 time=8.511 ms
    64 bytes from 183.2.172.185: icmp_seq=3 ttl=53 time=8.673 ms
    ^C
    --- www.a.shifen.com ping statistics ---
    4 packets transmitted, 4 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 8.370/8.618/8.917/0.203 ms

    WIFI​

    WIFI Station​

    Wi-Fi Station mode is an operating mode that enables a Wi-Fi device to connect to a Wi-Fi network and communicate with other devices.

    View full commands and terminal output
    root@armsom:/# ifconfig wlan0 up #Open wlan0
    root@armsom:/# ifconfig -a
    root@rk3506-buildroot:/# ifconfig -a
    can0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
    NOARP MTU:16 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:10
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:45

    eth0 Link encap:Ethernet HWaddr 9E:3C:0C:CC:4D:1D
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:54 Base address:0x2000

    eth1 Link encap:Ethernet HWaddr A2:3C:0C:CC:4D:1D
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:56 Base address:0x2000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:578 errors:0 dropped:0 overruns:0 frame:0
    TX packets:578 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:28940 (28.2 KiB) TX bytes:28940 (28.2 KiB)

    wlan0 Link encap:Ethernet HWaddr CC:64:1A:61:E8:19
    BROADCAST MULTICAST MTU:1500 Metric: 1
    RX packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
    TX packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0
    collisions: 0 txqueuelen: 1000
    RX bytes: 0 (0.0 B) TX bytes: 0 (0.0 B)
    root@armsom:/# connmanctl #Enter the Wi-Fi console
    connmanctl> enable wifi #Enable Wi-Fi, enabled by default
    connmanctl> agent on #Turn on the agent
    connmanctl> scan wifi #Turn on Wi-Fi scanning, supports multiple scans
    connmanctl> services #List scanned Wi-Fi networks
    connmanctl> services
    TP-Link_210A wifi_cc641a61e819_54502d4c696e6b5f32313041_managed_psk
    lulu wifi_cc641a61e819_6c756c75_managed_psk
    Triductor_5GAp wifi_cc641a61e819_547269647563746f725f35474170_managed_none
    OrayBox-2.4G-FD5C wifi_cc641a61e819_4f726179426f782d322e34472d46443543_managed_none
    R4R-2G wifi_cc641a61e819_5234522d3247_managed_psk
    wifi_cc641a61e819_hidden_managed_psk
    R3mini_Router2G wifi_cc641a61e819_52336d696e695f526f757465723247_managed_psk
    R4R-5G wifi_cc641a61e819_5234522d3547_managed_psk
    lulu_5G wifi_cc641a61e819_6c756c755f3547_managed_psk
    OrayBox-5G-FD5C wifi_cc641a61e819_4f726179426f782d35472d46443543_managed_none
    ydtx wifi_cc641a61e819_79647478_managed_psk
    Tri_Mesh_FH_ wifi_cc641a61e819_5472695f4d6573685f46485f_managed_psk
    Triductor_2GAp wifi_cc641a61e819_547269647563746f725f32474170_managed_none
    R3mini_Router5G wifi_cc641a61e819_52336d696e695f526f757465723547_managed_psk
    DIRECT-a4-HP M227f LaserJet wifi_cc641a61e819_4449524543542d61342d4850204d32323766204c617365724a6574_managed_psk
    CFG_2G wifi_cc641a61e819_4346475f3247_managed_psk
    wifi_cc641a61e819_hidden_managed_none
    Kingstar-Lo wifi_cc641a61e819_4b696e67737461722d4c6f_managed_psk
    jachunfree_5 wifi_cc641a61e819_6a616368756e667265655f35_managed_psk
    ChinaNet-mbCu-5G wifi_cc641a61e819_4368696e614e65742d6d6243752d3547_managed_psk
    HH-V-1 wifi_cc641a61e819_48482d562d31_managed_psk
    ChinaNet-2MNZ wifi_cc641a61e819_4368696e614e65742d324d4e5a_managed_psk
    ChinaNet-AtTi wifi_cc641a61e819_4368696e614e65742d41745469_managed_psk
    ChinaNet-mbCu wifi_cc641a61e819_4368696e614e65742d6d624375_managed_psk
    recynova wifi_cc641a61e819_726563796e6f7661_managed_psk
    DIRECT-sk-HUAWEI PixLab X1 wifi_cc641a61e819_4449524543542d736b2d485541574549205069784c6162205831_managed_psk
    ChinaNet-AtTi-5G wifi_cc641a61e819_4368696e614e65742d417454692d3547_managed_psk
    recynova-5G wifi_cc641a61e819_726563796e6f76612d3547_managed_psk
    Eureka-office wifi_cc641a61e819_457572656b612d6f6666696365_managed_psk
    BTWIFI6-042426 wifi_cc641a61e819_425457494649362d303432343236_managed_psk
    Eureka-guest wifi_cc641a61e819_457572656b612d6775657374_managed_psk
    ACCO-TEST wifi_cc641a61e819_4143434f2d54455354_managed_psk
    Kingstar-Lo-5G wifi_cc641a61e819_4b696e67737461722d4c6f2d3547_managed_psk
    jachun_link5g wifi_cc641a61e819_6a616368756e5f6c696e6b3567_managed_psk
    ChinaNet-Ns24 wifi_cc641a61e819_4368696e614e65742d4e733234_managed_psk
    CMCC-YM6M wifi_cc641a61e819_434d43432d594d364d_managed_none
    From the scanned Wi-Fi list, use connect XXXX to connect.
    connmanctl> connect wifi_cc641a61e819_79647478_managed_psk
    connmanctl> exit #Exit the terminal.

    After successfully connecting, use the ifconfig command to view the IP address obtained by wlan0.

    root@armsom:/# ping www.baidu.com

    BT​

    1. View Bluetooth

    root@armsom:/# hciconfig -a
    hci0: Type: Primary Bus: USB
    BD Address: CC:64:1A:61:E9:B6 ACL MTU: 1021:6 SCO MTU: 255:12
    UP RUNNING
    RX bytes:824 acl:0 sco:0 events:63 errors:0
    TX bytes:2289 acl:0 sco:0 commands:63 errors:0
    Features: 0xff 0xff 0xff 0xfa 0xdb 0xbf 0x7b 0x87
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
    Link policy: RSWITCH HOLD SNIFF PARK
    Link mode: PERIPHERAL ACCEPT
    Name: 'BlueZ 5.77'
    Class: 0x000414
    Service Classes: Unspecified
    Device Class: Audio/Video, Loudspeaker
    HCI Version: 5.2 (0xb) Revision: 0xddc8
    LMP Version: 5.2 (0xb) Subversion: 0x1141
    Manufacturer: Realtek Semiconductor Corporation (93)

    bluetoothctl

    root@armsom:/# bluetoothctl

    Enter the following command to connect

    root@armsom:/# power on
    root@armsom:/# agent on
    root@armsom:/# default-agent
    root@armsom:/# scan on
    root@armsom:/# pair yourDeviceMAC

    USB​

    USB storage

    1. First, insert the USB flash drive or USB portable hard drive into the USB interface of the CM1 Kit
    2. If you can see the output of sdX by executing the following command, it indicates that the USB drive recognition is successful
    root@armsom:/# cat /proc/partitions | grep "sd*"
    major minor #blocks name
    8 0 122880000 sda
    1. The mount command can be used to mount a USB drive to/mnt, and then the files on the USB drive can be viewed
    root@armsom:/# sudo mount /dev/sda1 /mnt
    1. After mounting, you can use the df - h command to view the capacity usage and mounting points of the USB flash drive
    root@armsom:/mnt# df -h | grep "sd"
    /dev/sda 4.7G 4.7G 0 100% /mnt

    audio​

    CM1-IO audio wiring
    CM1-IO audio wiring · Click to view image
    Check the sound card in the system.
    root@armsom:/# aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: rockchiprk730 [rockchip-rk730], device 0: dailink-multicodecs HiFi-0 [dailink-multicodecs HiFi-0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

    sound record

    arecord -D hw:0,0 -f S16_LE -t wav -c2 -r 16000 -d 5 /userdata/t.wav

    playback

    aplay /userdata/t.wav

    Product Longevity Statement​

    ArmSoM-CM1 will be produced until at least July 2035.

    Accessories​

    Our official accessories designed for the ArmSoM-CM1 Kit aim to help you achieve the best performance from your computer.

    Purchase Samples​

    ArmSoM Independent Site: https://item.taobao.com/item.htm?ft=t&id=965592864051

    ArmSoM AliExpress Official Store:

    ArmSoM Taobao Official Store: https://item.taobao.com/item.htm?ft=t&id=965592864051

    For OEM&ODM, please contact: sales@armsom.org

    Important Notes​

    [Electrostatic Discharge (ESD) Protection]
    1. Always wear an anti-static wrist strap or take ESD precautions before handling the device to prevent damage.
    2. Assembly should be performed in an ESD-controlled environment. Avoid operation under dry and low-humidity conditions.
    3. When not in use, store the device in an anti-static bag in a temperature-controlled, low-humidity environment.
    4. Avoid friction or collision when handling the device to prevent generating static electricity.
    5. Handle the device by its edges, avoiding direct contact with chips on the motherboard.
    6. Do not plug or unplug cables or other devices while the system is powered on to avoid damage from current surges.
    7. Before plugging/unplugging expansion GPIO/MIPI interfaces, power down the device and disconnect the power cable.
    [Thermal Management]

    Without effective cooling measures, the surface temperature of the main SoC can exceed 60°C. Avoid direct contact with the SoC and surrounding power inductors to prevent burns. Ensure adequate ventilation around the device during operation. Do not place the SBC in direct sunlight. It is recommended to use the official Cooling Fan & Heatsink Kit or DIY Case, or suitable third-party cooling solutions to ensure optimal thermal performance.

    Contact us