ESS-WIKI - New pages [en]

Edge AI SDK/AI Framework/RK3576

2026-04-30T01:10:35Z

Zhihao.zhu:

= RKNN SDK =

RKNN SDK （[https://pan.baidu.com/s/1R0DhNJU56Uhp4Id7AzNfgQ Baidu] Password: a887）include two parts:

*rknpu2 (on the Board End)
*rknn-toolkit2 (on the PC)
<pre>├── rknpu2
│ ├── Driver
│ └── RKNPU2 Environment
└── rknn-toolkit2
</pre>

== RKNPU2 ==

RKNPU2 include driver and environment to help to fast develop AI applications using rknn model(*.rknn). More Info refer to [https://ess-wiki.advantech.com.tw/view/RK_Platform_NPU_SDK RK_Platform_NPU_SDK]

=== RKNPU2 Driver ===

The official firmware of boards all installs the RKNPU2 driver. You can execute the following command on the board end to query the RKNPU2 driver version: dmesg | grep -i rknpu.

=== RKNPU2 Environment ===

Here are two basic concepts in the RKNPU2 environment:

*'''RKNN Server''': A background proxy service running on the development board. The main function of this service is to call the interface corresponding to the board end Runtime to process the data transmitted by the computer through USB, and return the processing results to the computer.

*'''RKNPU2 Runtime library (librknnrt.so)''': The main responsibility is to load the RKNN model in the system and perform inference operations of the RKNN model by calling a dedicated neural processing unit (NPU)

== RKNN-TOOLKIT2 ==

RKNN-Toolkit2 is a development kit that provides users with model conversion, inference and performance evaluation on PC platforms. Users can easily complete the following functions through the Python interface provided by the tool:

#'''Model conversion''': support to convert Caffe / TensorFlow / TensorFlow Lite / ONNX / Darknet / PyTorch model to RKNN model, support RKNN model import/export, which can be used on Rockchip NPU platform later.
#'''Quantization''': support to convert float model to quantization model, currently support quantized methods including asymmetric quantization (asymmetric_quantized-8). and support hybrid quantization.
#'''Model inference''': Able to simulate NPU to run RKNN model on PC and get the inference result. This tool can also distribute the RKNN model to the specified NPU device to run, and get the inference results.
#'''Performance & Memory evaluation''': distribute the RKNN model to the specified NPU device to run, and evaluate the model performance and memory consumption in the actual device.
#'''Quantitative error analysis''': This function will give the Euclidean or cosine distance of each layer of inference results before and after the model is quantized. This can be used to analyze how quantitative error occurs, and provide ideas for improving the accuracy of quantitative models.
#'''Model encryption''': Use the specified encryption method to encrypt the RKNN model as a whole.

More Info refer to [https://github.com/airockchip/rknn-toolkit2 rknn-toolkit2]   More Info refer to [https://ess-wiki.advantech.com.tw/view/RK_Platform_NPU_SDK#rknn-toolkit2 RK_Platform_NPU_SDK]  

 

= Applications =

== Edge AI SDK / Vision Application ==

{| border="1" cellpadding="1" cellspacing="1" style="width: 900px;"
|-
| style="width: 154px;" | Application
| style="width: 179px;" | Model
| style="width: 179px;" | AOM-3841 FPS (video file)
| style="width: 179px;" | AOM-5841 FPS (video file)
|-
| style="width: 154px;" | Object Detection
| style="width: 154px;" | yolov10
| style="width: 154px;" | 25
| style="width: 154px;" | 25
|-
| style="width: 154px;" | Person Detection
| style="width: 154px;" | yolov5
| style="width: 154px;" | 25
| style="width: 154px;" | 25
|-
| style="width: 154px;" | Face Detection
| style="width: 154px;" | retinaface
| style="width: 154px;" | 25
| style="width: 154px;" | 25
|-
| style="width: 154px;" | Pose Estimation
| style="width: 154px;" | yolov8_pose
| style="width: 154px;" | 25
| style="width: 154px;" | 25
|}

 

= Benchmark =

RK3576 is used to deploy a wide range of popular DNN models and ML frameworks to the edge with high performance inferencing, for tasks like real-time classification and object detection, pose estimation, semantic segmentation, and natural language processing (NLP). More Info refer to [ [https://github.com/airockchip https://github.com/airockchip] ]

Advantech, based on the rknn_common_test command, has encapsulated the npu_stress_test.sh to be used for testing the NPU.

 

= Utility =

*'''sysstat''': This SDK provides the mpstat utility, which reports memory usage and processor usage for devices. You can find the utility in your package at the following location. More Info refer to [https://github.com/sysstat/sysstat Link]  
*'''OpenCV4.6''': OpenCV (Open Source Computer Vision Library: [http://opencv.org http://opencv.org]) is an open-source library that includes several hundreds of computer vision algorithms. More Info refer to [https://github.com/opencv/opencv/wiki/OpenCV-Change-Logs-v2.2‐v4.10 Link]

Edge AI SDK/AI System/AOM-3841

2026-04-28T09:28:34Z

Zhihao.zhu:

{{DISPLAYTITLE:AOM-A3841}}

{| border="0" cellpadding="5" cellspacing="0" style="width:100%;"
|-
| style="width: 30%; high: 200px; text-align: center;vertical-align: top;" | [[File:EAS-AOM-3841.jpg|AOM-3841]]
Rockchip RK3576 Cortex®-A72 and A53 4''SBC''

| style="vertical-align: top;" |  
| style="vertical-align: top;" |
{| class="wikitable" style="width:100%; margin:auto; border:2px solid #ffffff; border-collapse:separate; border-spacing:10px; text-align:center;"
|-
! style="background-color:#3664B1; color:white; width:150px; text-align:center; border:1px;" | AI Applications
| colspan="5" style="padding:0; border:1px solid black;" |
{| class="wikitable" style="width:100%; border-collapse:separate; border-spacing:5px; border:0px;"
|-
| style="border:1px solid gray; text-align:center; padding:10px; width:20%;" | Vision AI Apps
| style="background-color:#D3D3D3; border:1px solid gray; text-align:center; padding:10px; width:20%; color:white;" | Pre-trained Models
| style="border:1px solid gray; text-align:center; padding:10px; width:20%;" | Monitoring
| style="border:1px solid gray; text-align:center; padding:10px; width:20%;" | Benchmark
|}

|-
! style="background-color:#3664B1; color:white; text-align:center;" | Utility
| colspan="5" style="padding:0; border:1px solid black;" |
{| class="wikitable" style="width:100%; border-collapse:separate; border-spacing:5px; border:0px;"
|-
| colspan="2" style="background-color: #003366; border: 1px solid gray; text-align: center; padding: 10px; width: 195px;" | rknn_common_test
| colspan="2" style="background-color: #D3D3D3; border: 1px solid gray; text-align: center; padding: 10px; width: 208px;" | sysstat
|}

|-
! style="background-color:#3664B1; color:white; text-align:center;" | AI SDK
| colspan="5" style="padding:0; border:1px solid black;" |
{| class="wikitable" style="width:100%; border-collapse:separate; border-spacing:5px; border:0px;"
|-
| colspan="5" style="background-color:#003366; border:1px solid gray; text-align:center; padding:10px; width:50%;" | RKNN SDK
| colspan="5" style="background-color:#D3D3D3; border:1px solid gray; text-align:center; padding:10px; width:50%;" | OpenCV 4.6.0
|}

|-
! style="background-color:#3664B1; color:white; text-align:center;" | Driver
| colspan="5" style="padding:0; border:1px solid black;" |
{| class="wikitable" style="width:100%; border-collapse:separate; border-spacing:5px; border:0px;"
|-
| colspan="5" style="background-color:#003366; border:1px solid gray; text-align:center; padding:10px; width:100%;" | RKNPU2
|}

|-
! style="background-color:#3664B1; color:white; width:150px; text-align:center; border:1px;" | OS / Kernel
| colspan="5" style="border:1px solid black; text-align:center; padding:15px;" | Debian 12 ( kernel: 6.1 )
|}
<div style="font-size:large; color: rgb(77, 77, 77); line-height: 20px; text-align: center;">Edge AI SDK Software Stack on AOM-3841 ( v3.3.0 )</div> <div style="text-align: right; margin-top: 10px;">
{| style="border-collapse: separate; border-spacing: 10px; float: right; margin-right: 0"
|-
| style="width:20px; height:20px; background-color:#ffffff; border:1px solid black;" |  
| style="text-align: left;" | Advantech
| style="width:20px; height:20px; background-color:#003366; border:1px solid black;" |  
| style="text-align: left;" | Rockchip
| style="width:20px; height:20px; background-color:#D3D3D3; border:1px solid black;" |  
| style="text-align: left;" | Open Source
|}
</div>
|}

 

{| border="0" cellpadding="0" cellspacing="5" style="width:100%;"
|-
| style="vertical-align: top;" |
{| border="0" cellpadding="0" cellspacing="0" style="width:100%;"
|-
| style="width: 33%; vertical-align: top;padding-left: 5px;" |
{| border="0" cellpadding="5" cellspacing="0" style="width:100%;"
|-
| style="background-color: rgb(54, 100, 177);" | AI Accelerator
|-
| style="vertical-align: top;line-height:20px;" |
None

|}

| style="width: 33%; vertical-align: top;padding-left: 5px;" |
{| border="0" cellpadding="5" cellspacing="0" style="width:100%;"
|-
| style="background-color: rgb(54, 100, 177);" | AI Inference Run-time SDK
|-
| style="vertical-align: top;line-height:20px;" |
[[Edge_AI_SDK/AI_Framework/RK3576#RKNN_SDK|RKNN_SDK]]

[[Edge_AI_SDK/AI_Framework/RK3576#Applications|Applications]]

[https://github.com/ADVANTECH-Corp/EdgeAI_Workflow/tree/main/ai_system/ EdgeAI Workflow]

|}

| style="width: 33%; vertical-align: top;padding-left: 5px;" |
{| border="0" cellpadding="5" cellspacing="0" style="width:100%;"
|-
| style="background-color: rgb(54, 100, 177);" | AI Benchmark & Tools
|-
| style="vertical-align: top;line-height:20px;" |
[[Edge_AI_SDK/AI_Framework/RK3576#RKNN-TOOLKIT2|RKNN-TOOLKIT2]]

[[Edge_AI_SDK/AI_Framework/RK3576#Benchmark|benchmak]]

[[Edge_AI_SDK/AI_Framework/RK3576#Utility|utility]]

|}

 

|}

 

| style="width: 200px; vertical-align: top;" |
{| border="0" cellpadding="5" cellspacing="0" style="width:100%;"
|-
| style="background-color: rgb(56, 85, 114);" | Documentation
|-
| Datasheet 3D Model
|}

|}

AOM-5521-VH0016-Module

2026-04-07T02:47:21Z

Sean.chuang: Created page with " 4G Module : AIW-344 Test pass WIFI /BT Module : AIW-167 Test pass"

4G Module : AIW-344 Test pass

WIFI /BT Module : AIW-167 Test pass

AIM-Linux/BSP/NXP/Linux Yocto OS Release note/AOM-5521/VH0016

2026-04-07T02:45:46Z

Sean.chuang: Created page with " '''Release Note ''' {| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%" |- | '''Uboot version ''' | v2025.04_6.12.20_2.0.0 |- | '''Kernel..."

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%"
|-
| '''Uboot version '''
|
v2025.04_6.12.20_2.0.0

|-
| '''Kernel version '''
| 6.12.20_2.0.0
|}

'''Change Log'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" style="width: 301px;" width=""
|-
| '''Item'''
| style="width: 93px;" |
'''Change List'''

| style="width: 163px;" |
'''Description'''

|-
| '''1'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed HW reset issue
|-
| '''2'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed reboot cmd issue
|-
| '''3'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed HDMI interrupt issue
|-
| '''4'''
| style="width: 93px;" |  
| style="width: 163px;" |  
|}

 

AIR 075 Development

2026-03-27T02:10:17Z

Will.chen:

==Attention==
===Account & Password===
Account number
<pre>
ubuntu
</pre>
In device used "sudo" or "sudo su" to root.
Password required.
<pre>
ubuntu
</pre>

=== Power off and restart ===
Cold reboot the device.

== Bootloader Version ==
Check device boot up in debugport log
 
[[File:Aimb-294-uefi.jpg|800px|border]]

== Burnin ==
[[ASR_A702_Burnin|ASR-A702 Burnin]]
<pre>
$ cd /tool
$ sudo Burnin.sh
</pre>

== BootCount ==
=== BootCount tool install ===
In first time please install bootcount tool

<pre>
$ cd /home/ubuntu
$ sudo ./bootCount.sh
</pre>

Default enter the OS 20s will poweroff

=== Boot On Off ===

The boot count message will be printed before log-in. [[File:Air030 bootcount.jpg|200px]] Reset the boot count please remove '''bootCount.tt'''.
<pre>
$ rm bootCount.tt
</pre>

== Tools ==

=== Test Command ===

==== '''DIO 8bit''' ====
Hardware setting
 

 
* The TCA9555 is identical to the TCA9535, except for the inclusion of the internal I/O pull-up resistor, which pulls the I/O to a default high when configured as an input and undriven.
Pin table with DIO expander number
 
 Pin1-->704, Pin5-->712
 Pin2-->705, Pin6-->713
 Pin3-->706, Pin7-->714
 Pin4-->707, Pin8-->715
 
For example set Pin1 direction out, value high
<pre>
$ sudo su
# echo 704 > /sys/class/gpio/export
# echo out > /sys/class/gpio/gpio704/direction
# echo 1 > /sys/class/gpio/gpio704/value
</pre>
For example set Pin5 direction in
<pre>
$ sudo su
# echo 712 > /sys/class/gpio/export
# echo in > /sys/class/gpio/gpio712/direction
</pre>

== Type-C USB ==

Please run the following commands to enable the Type-C USB.

<pre>
$ cd /tools
$ sudo ./add-overlays.sh /boot/dtb/kernel_tegra264-p4071-0000+p3834-0008-nv.dtb /boot/tegra264-air075-a1-typec-host-overlay.dtbo
</pre>

== Reference ==
[[AIR-075|AIR-075]]

AIR-075

2026-03-27T02:04:16Z

Will.chen:

== Linux BSP Version ==

Ubuntu 24.04 Kernel 6.8.12

== Released Image ==

*[http://ess-wiki.advantech.com.tw/view/AIM-Linux/BSP/NV/Linux_Ubuntu_OS_Release_note/Ubuntu24/Internal OS Support List(based on Ubuntu24)]

== Build Environment on Host ==

Attention : Your host OS please use a version higher than ubuntu 20.04 Currently, we adopt [https://www.docker.com/ Docker] as build environment. You can get the latest version of advrisc/u20.04-nvlbv2:20240515 Docker image for developing nVidia jetson projects. Docker command:
<pre>$ sudo docker pull advrisc/u20.04-nvlbv2:20240515</pre>

== Run Docker example ==

Step1 Run docker container (example)
<pre>sudo docker run -it --name jetson_linux_risc -v /home/bsp/myLinux:/home/adv/BSP:rw --privileged advrisc/u20.04-nvlbv2:20240515 /bin/bash
</pre>

Step2 In container, change the user. (example)
<pre> adv@7cc0fa834366:~$ sudo chown adv:adv -R BSP
</pre>

== Dependncy Library ==

Please install library in the HOST outside of docker if you get Exec format error.
<pre>$ sudo apt-get install qemu-user-static
</pre>

== Getting Linux Source Code ==
<pre>$ export GIT_SSL_NO_VERIFY=1</pre>
<pre>$ cd ~/BSP
$ mkdir jetson_linux_risc
$ cd jetson_linux_risc
$ git config --global user.name "Your Name"
$ git config --global user.email "Your@example.com"
</pre>

AIR-075

Jetpack 7.0 / L4T 38.2.0
<pre>$ repo init -u https://AIM-Linux@dev.azure.com/AIM-Linux/risc_nvidia_jetson_38.2.0/_git/manifest -m air075a1_ubuntu24.04-jp7.0_v0.0.0_kernel-6.8.12_agx-thor.xml
$ repo sync
</pre>

Jetpack 7.1 / L4T 38.4.0
<pre>$ repo init -u https://AIM-Linux@dev.azure.com/AIM-Linux/meta-advantech-nvidia/_git/adv-manifest -b JP7.1-r38.4.0 -m default.xml
$ repo sync
$ cd adv-jetson-custom
$ ./generate_profile.py --project air075a1
$ ./apply_profile.py --project air075a1
</pre>

== Build Image  ==
<pre>$ sudo ./scripts/build_release.sh
</pre>

== Tar Image for Test unit  ==
<pre>$ sudo tar zcvf AIR-075_XXX.tar.gz Linux_for_Tegra
</pre>

== Flash Image ==

1. HW setting recover mode Change the RST_RECOVY "2" to ON and power on. [[File:Air075 flash image 01.jpg|border|450px|Air075 flash image.jpg]] 
 
Connect a linux OS host wired AIR-075 with Flash USB cable. In the Host PC, make sure the AIR-075 (NVidia Corp) has detectd.
<pre>[ubuntu@linux 11:55:43 ~]$ lsusb
Bus 001 Device 024: ID 0955:7223 NVidia Corp.
</pre>

2.Extracted tarball file
<pre>$ sudo tar -zxvf AIR-075_XXX.tar.gz
$ cd Linux_for_Tegra
</pre>

3.Flash image (Thor Module + eMMC)
<pre>$ sudo ./l4t_initrd_flash.sh -c tools/kernel_flash/flash_l4t_t264_nvme.xml --external-device nvme0n1p1 --showlogs jetson-agx-thor-air075-a1 internal
</pre>

== Reference ==

[[AIR_075_Development|AIR-075 Development]]

Linux BSP User Guide for AOM-3841 Series-Debian12

2026-03-24T01:29:53Z

Xingxing.li: Created page with " == Linux BSP Version == Debian 12.x Kernel 6.1.xx == Build Environment on Host == Currently, we adopt [https://www.docker.com/ Docker] as build environment. You can get..."

== Linux BSP Version ==

Debian 12.x

Kernel 6.1.xx

== Build Environment on Host ==

Currently, we adopt [https://www.docker.com/ Docker] as build environment.

You can get the latest version of advrisc/u20.04-rklbv1 Docker image for developing Rockchip RK3588 projects.

Docker command:
<pre>$ sudo apt-get update
$ sudo apt-get install -y qemu-user-static
$ sudo apt-get install -y live-build
$ sudo docker pull advrisc/u20.04-rklbv1
</pre>

== Run Docker example ==

Step1 Run docker container (example)
<pre>$ sudo docker run -it --name rk3576_linux_risc -v /home/bsp/myLinux:/home/adv/BSP:rw --privileged advrisc/u20.04-rklbv1:latest /bin/bash
</pre>

Step2 In container, change the user. (example)  
<pre>$ adv@7cc0fa834366:~$ sudo chown adv:adv -R BSP
</pre>

 

== Getting Linux Source Code ==

Debian 12.x

Please contact PM to get BSP.

If you have BSP tarball (eg. AOM3841A1AIM38DBV110020_2025-07-10.bsp.tgz), then you have to copy it into container.

Follow the steps below:

1.Exit container and back to local machine
<pre>$ exit
</pre>

2.Copy BSP tarball to ${WORKSPACE} , and change owner
<pre>$ cp AOM3841A1AIM38DBV110020_2025-07-10.bsp.tgz '''${WORKSPACE}'''
$ sudo chown adv:adv ${WORKSPACE}/AOM3841A1AIM38DBV110020_2025-07-10.bsp.tgz  
</pre>

3.Back to container
<pre>$ docker start '''${CONTAINER_NAME}'''
$ docker attach '''${CONTAINER_NAME}'''
</pre>

4.Unpack BSP tarball
<pre>$ tar zxvf AOM3841A1AIM38DBV110020_2025-07-10.bsp.tgz
</pre>

 

== Build Choose Project ==

=== Build Choose Project A0M-3841 ===
<pre>$ export TOP=`pwd`
$ cd $TOP
$ ./build.sh adv_rk3576_aom3841a1_defconfig
$
</pre>

 

== Build U-boot ==
<pre>
$ cd $TOP
$ ./build.sh uboot
</pre>

== Build Kernel ==
<pre>$ cd $TOP
$ ./build.sh kernel
</pre>

== Build Recovery ==
<pre>$ cd $TOP
$ rm buildroot/output/rockchip_rk3588_recovery -rf
$ ./build.sh recovery
</pre>

 

'''CAUTION'''

BSP tarball is for fast developping <code>uboot</code> and <code>kernel</code> .

BSP tarball DONOT support to build <code>recovery</code>.

== Build Debian 12.x ==
<pre>$ cd $TOP
$ sudo dpkg -i debian/ubuntu-build-service/packages/*
$ sudo apt-get install -f -y
$ ./build.sh debian
</pre>

 

'''CAUTION'''

BSP tarball is for fast developping <code>uboot</code> and <code>kernel</code> .

BSP tarball DONOT support to build <code>debian</code>.

 

== Push all image to rockdev folder ==

'''SDK V110 and after:'''
<pre>$ cd $TOP
$ ./build.sh firmware
</pre>

The common image files are listed below:

 
<pre># boot.img
# misc.img
# oem.img
# recovery.img
# rootfs.img
# uboot.img
# userdata.img
# MiniLoaderAll.bin
# parameter.txt
#
</pre>

== Make update.img ==
<pre>$ cd $TOP
$ sudo apt-get install bsdmainutils
$ ./build.sh updateimg
</pre>

You can get update.img in rockdev/

 

'''CAUTION'''

BSP tarball is for fast developping <code>uboot</code> and <code>kernel</code> .

BSP tarball DONOT support to build <code>updateimg</code>.

AOM-5521-VH0015-Module

2026-03-24T01:21:43Z

Sean.chuang: Created page with " 4G Module : AIW-344 Test pass WIFI /BT Module : AIW-167 Test pass"

4G Module : AIW-344 Test pass

WIFI /BT Module : AIW-167 Test pass

AIM-Linux/BSP/NXP/Linux Yocto OS Release note/AOM-5521/VH0015

2026-03-24T01:20:48Z

AOM-3841 CAN FD（CAN0/1）

2026-03-23T08:58:16Z

Xingxing.li: /* Check Network Ports */

=== '''CAN FD''' ===

AOM-3841 has two CAN ports. Use the “candump” and “cansend” tools directly to send and receive messages. The tools have been embedded into the system.

=== '''AOM-DB3500 CAN0_1 HW Pindefine''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| '''Pin'''
| '''Signal'''
| '''I/O'''
| '''Description'''
|-
| 1
| CAN0_D+
| I/O
| CAN0 Data+
|-
| 2
| CAN0_D-
| I/O
| CAN0 Data-
|-
| 3
| CAN1_D+
| I/O
| CAN1 Data+
|-
| 4
| CAN1_D-
| I/O
| CAN1 Data-
|-
| 5
| GND
|  
| Ground
|-
| 6
| GND
|  
| Ground
|-
| 7
| N/A
|  
| Not Applicable
|-
| 8
| N/A
|  
| Not Applicable
|}
[[File:AOM-DB3500 CAN0 1.jpg|RTENOTITLE]]  [[File:AOM-DB3500 CAN0 1 Pin define.jpg]]

=== '''Check Network Ports''' ===

Check network ports of can0 and can1: 
<pre># ifconfig -a
… …
can0: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

can1: flags=193<UP,RUNNING,NOARP> mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 10 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

… …
</pre>

==== '''Configure''' ====

Use “ip” command to configure can port. See details of the usage of “ip link”:
<pre># ip link help
… …
ip link set { DEVICE | dev DEVICE | group DEVGROUP }
[ { up | down } ]
[ type TYPE ARGS ]
… …
</pre>
<pre># ip link help can
… …
ip link set DEVICE type can
[ bitrate BITRATE [ sample-point SAMPLE-POINT] ] |
[ dbitrate BITRATE [ dsample-point SAMPLE-POINT] ] |
[ fd { on | off } ]
… …
</pre>

For example, set can0 "birate rate” to 1000000 “dbitrate rate” to 2000000 “fd” to on
<pre># #---- For can0 ----# #
# ip link set can0 down
# ip link set can0 type can bitrate 1000000 dbitrate 2000000 fd on
# ip link set can0 up
</pre>

=== '''Send and Reveive Data''' ===

*'''As receiver'''
<pre># #---- As receiver ----# #
# ip link set can0 down
# ip link set can0 type can bitrate 1000000 dbitrate 2000000 fd on
# ip link set can0 up
# candump can0 &
</pre>

*'''As sender'''
<pre># #---- As sender ----# #
# ip link set can1 down
# ip link set can1 type can bitrate 1000000 dbitrate 2000000 fd on
# ip link set can1 up
# cansend can1 123##155

# #----If no error, the receiver will receive the following data----# #
Can0 123 [01] 55</pre>

AOM-3841 GMAC0/1

2026-03-23T06:53:55Z

Xingxing.li:

=== '''Ethernet''' ===

AOM-3841 supports two Ethernet ports (via 9696EG6A000): eth0/eth1. All ports are using the “DHCP” mode by default. The following configurations and tests are taking eth0 as an example.

=== '''Configure to Static IP''' ===

1. Click “Applications” -> “Settings” -> “Advanced Network Configration”.

[[File:ROM-6881 Eethernet.png|500x400px|ROM-6881 Eethernet.png]]

2. Double-click “Wired Connection 1” to configure it.

[[File:ROM-6881 Ethernet wired connection.png|500x400px|ROM-6881 Ethernet wired connection.png]]

=== '''Configure to DHCP''' ===

1. Click “Applications” -> “Settings -> “Advanced Network Configration”.

[[File:ROM-6881 Network.png|500x400px]]

2. Double-click “Wired Connection 1” to configure it.

[[File:ROM-6881 Ethernet IPV4.png|500x400px]]

=== '''Ethernet Test''' ===

After connection, Ethernet will create a net point “eth0” and “eth1”.
<pre># #---- Test eth0 ----# #
# ping –I eth0 www.advantech.com
# #---- Test eth1 ----# #
# ping –I eth1 www.advantech.com</pre>

AOM-3841 SPI CN1&SPI)CN2&CN2 I2C——I2C/SPI

2026-03-19T02:24:47Z

Xingxing.li:

== '''I2C Pin Header''' ==

'''AOM-3841 has two I2C-PIN-Header channels.'''

=== '''CN2_I2C''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 409px;"
|-
| colspan="4" style="width: 399px;" | '''CN2 CN2 Connector Pin Definition'''
|-
| style="width: 60px;" | '''Pin'''
| style="width: 85px;" | '''Signal'''
| style="width: 38px;" | '''I/O'''
| style="width: 203px;" | '''Description'''
|-
| style="width: 60px;" | 1
| style="width: 85px;" | GND
| style="width: 38px;" |  
| style="width: 203px;" | Ground
|-
| style="width: 60px;" | 2
| style="width: 85px;" | I2C0_DATA
| style="width: 38px;" | I/O
| style="width: 203px;" | I2C0 Data
|-
| style="width: 60px;" | 3
| style="width: 85px;" | I2C0_CLK
| style="width: 38px;" | I
| style="width: 203px;" | I2C0 clock input from host.
|-
| style="width: 60px;" | 4
| style="width: 85px;" | +V1.8
| style="width: 38px;" |  
| style="width: 203px;" | 1.8V Source
|}

=== '''CN4_I2C''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 409px;"
|-
| colspan="4" style="width: 399px;" | '''CN4 CN4 Connector Pin Definition'''
|-
| style="width: 61px;" | '''Pin'''
| style="width: 92px;" | '''Signal'''
| style="width: 36px;" | '''I/O'''
| style="width: 197px;" | '''Description'''
|-
| style="width: 61px;" | 1
| style="width: 92px;" | GND
| style="width: 36px;" |  
| style="width: 197px;" | Ground
|-
| style="width: 61px;" | 2
| style="width: 92px;" | I2C1_DATA
| style="width: 36px;" | I/O
| style="width: 197px;" | I2C1 Data
|-
| style="width: 61px;" | 3
| style="width: 92px;" | I2C1_CLK
| style="width: 36px;" | I
| style="width: 197px;" | I2C0 clock input from host.
|-
| style="width: 61px;" | 4
| style="width: 92px;" | +V1.8
| style="width: 36px;" |  
| style="width: 197px;" | 1.8V Source
|}

=== '''Number''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="4" | '''I2C-PIN-Header'''
|-
| '''I2C Number'''
| '''Bus Number'''
| '''I2C Address'''
| '''AOM-DB3500 Number'''
|-
| I2C0
| 0
| 0x53
| CN2
|-
| I2C1
| 7
| 0x57
| CN4
|}
<pre># i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- 0c -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- 53 -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- 71 -- -- -- -- -- --
# i2cdetect -y 7
# i2ctransfer -y 7 w4@0x53 0x1f 0xf0 0x22 0x33
# i2ctransfer -y 7 w2@0x53 0x1f 0xf0 r2
0x22 0x33
</pre>

[[File:AOM-3841 I2C function.png|RTENOTITLE]]
<pre># i2cdetect -y 7
# i2ctransfer -y 7 w4@0x57 0x1f 0xf0 0x22 0x33
# i2ctransfer -y 7 w2@0x57 0x1f 0xf0 r2
0x22 0x33</pre>

[[File:AOM-3841 I2C function1.png|RTENOTITLE]]

== '''SPI PIN Header''' ==

AOM-3841 has two SPI-PIN-Header channels. SPIs on AOM-DB3500 have multifunctions, change to SPI PIN Header.

=== '''SPI_CN1''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="4" | '''SPI_CN1 Connector Pin Definition'''
|-
| '''Pin'''
| '''Signal'''
| '''I/O'''
| '''Description'''
|-
| 1
| +V1.8
|  
| Power Supply
|-
| 2
| GND
|  
| Ground
|-
| 3
| SPI1_CS0#
| I
| SPI1Chip Select Inpu
|-
| 4
| SPI1_CLK
| I
| SPI1 Serial Clock Input
|-
| 5
| SPI1_MISO
| I
| SPI1 Master Out Slave in
|-
| 6
| SPI1_MOSI
| O
| SPI1 Master In Slave Out
|-
| 7
| NA
|  
| Not Applicable
|-
| 8
| SPI1_CS1#
| I
| SPI Chip Select Input
|}

=== '''SPI_CN2''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="4" | '''SPI_CN2 Connector Pin Definition'''
|-
| '''Pin'''
| '''Signal'''
| '''I/O'''
| '''Description'''
|-
| 1
| +V1.8
|  
| Power Supply
|-
| 2
| GND
|  
| Ground
|-
| 3
| SPI0_CS0#
| I
| SPI0Chip Select Inpu
|-
| 4
| SPI0_CLK
| I
| SPI0 Serial Clock Input
|-
| 5
| SPI0_MISO
| I
| SPI0 Master Out Slave in
|-
| 6
| SPI0_MOSI
| O
| SPI0 Master In Slave Out
|-
| 7
| NA
|  
| Not Applicable
|-
| 8
| SPI0_CS1#
| I
| SPI Chip Select Input
|}

 

=== '''Jumper Setting：''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 472px;"
|-
| colspan="2" style="width: 462px;" | '''SPI Select'''
|-
| style="width: 102px;" | Pin
| style="width: 354px;" | Function
|-
| style="width: 102px;" | J6（1-2）
| style="width: 354px;" | Switch SPI0 to the SPI1 flash on the baseboard.
|-
| style="width: 102px;" | J6（2-3）
| style="width: 354px;" | SPI0 is switched to the baseboard SPI_CN2
|-
| style="width: 102px;" | J5（1-2）
| style="width: 354px;" | Switch from SPI1 to SPI2 flash
|-
| style="width: 102px;" | J5（2-3）
| style="width: 354px;" | SPI1 is switched to SPI_CN1
|}

=== '''Using EG70 Test Board to read SPI flash.''' ===

Test one SPI port alternatively:
<pre># cat /proc/mtd | grep –c mtd01</pre>

Test two SPI ports at the same time:
<pre># cat /proc/mtd | grep -c mtd11
</pre>

=== '''RK Tool  Test：''' ===
<pre># /tools/test/adv/spi/spi_test.sh 0
# /tools/test/adv/spi/spi_test.sh 1</pre>

[[File:AOM-3841 SPI function1.png|RTENOTITLE]]

AOM-3841 M2 E1 Key——WIFI/BT/SATA

2026-03-18T08:30:00Z

Xingxing.li:

=== '''WIFI/BT''' ===

AOM-3841 supports AIW-162BS-GI1.(Broadcom AP6275P, - 40°C~85°C PCIE+UART)

[[File:AIW-162BS-GI1.png|RTENOTITLE]] 

=== '''M2_E1 Key Pin define''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="4" | '''M2_E1 M2_E1 Connector Pin Definition'''
|-
| '''Pin'''
| '''Signal'''
| '''I/O'''
| '''Description'''
|-
| 1
| GND
|  
| Ground
|-
| 2
| +V3.3E_M.2
|  
| 3.3 V source
|-
| 3
| USB5_Z_D+
| I/O
| USB Data + Differential serial data
|-
| 4
| +V3.3E_M.2
|  
| 3.3 V source
|-
| 5
| USB5_Z_D-
| I/O
| USB Data - Differential serial data
|-
| 6
| LED1#_M2
| O
| The Adapters’ status indicators via LED devices.
|-
| 7
| GND
|  
| Ground
|-
| 8
| N/A
|  
| Not Applicable
|-
| 9
| N/A
|  
| Not Applicable
|-
| 10
| N/A
|  
| Not Applicable
|-
| 11
| N/A
|  
| Not Applicable
|-
| 12
| N/A
|  
| Not Applicable
|-
| 13
| N/A
|  
| Not Applicable
|-
| 14
| N/A
|  
| Not Applicable
|-
| 15
| N/A
|  
| Not Applicable
|-
| 16
| LED2#_M2
| O
| The Adapters’ status indicators via LED devices.
|-
| 17
| N/A
|  
| Not Applicable
|-
| 18
| GND
|  
| Ground
|-
| 19
| N/A
|  
| Not Applicable
|-
| 20
| UART1_E1_WAKE#
| O
| UART sideband used to Wake up Platform.
|-
| 21
| N/A
|  
| Not Applicable
|-
| 22
| SER1_RX_M2
| O
| UART Receive Data
|-
| 23
| N/A
|  
| Not Applicable
|-
| 24-31
| Module key
|  
| Module key
|-
| 32
| SER1_TX_M2
| I
| UART Transmit Data
|-
| 33
| GND
|  
| Ground
|-
| 34
| SER1_CTS#_M2
| O
| UART Clear to Send connected.
|-
| 35
| PCIE20_A_TX+
| I
| PCIe TX Differential signals.
|-
| 36
| SER1_RTS#_M2
| I
| UART Ready to Send connected.
|-
| 37
| PCIE20_A_TX-
| I
| PCIe TX Differential signals
|-
| 38
| N/A
|  
| Not Applicable
|-
| 39
| GND
|  
| Ground
|-
| 40
| N/A
|  
| Not Applicable
|-
| 41
| PCIE20_A_RX+
| O
| PCIe RX Differential signals
|-
| 42
| N/A
|  
| Not Applicable
|-
| 43
| PCIE20_A_RX-
| O
| PCIe RX Differential signals
|-
| 44
| N/A
|  
| Not Applicable
|-
| 45
| GND
|  
| Ground
|-
| 46
| N/A
|  
| Not Applicable
|-
| 47
| PCIE20_A_CLK+
| I
| PCIe Reference Clock signals (100 MHz)
|-
| 48
| N/A
|  
| Not Applicable
|-
| 49
| PCIE20_A_CLK-
| I
| PCIe Reference Clock signals (100 MHz)
|-
| 50
| CLKO_Z_WIFI
| I
| Suspend Clock is a 32.768 kHz clock
|-
| 51
| GND
|  
| Ground
|-
| 52
| PERST#
| I
| PCIe Reset is a functional reset to the Adapter
|-
| 53
| PCIE_Z_REQ#
| I/O
| PCIe Clock Request is a reference clock request signal.
|-
| 54
| NGFF_BT_DISABLE#
| O
| Aactive Low,when applied by the system it will disable radio operation on the Adapter that implement radio frequency applications.
|-
| 55
| PE_WAKE#
| I/O
| PCIe WAKE#. When the Adapter supports wakeup, this signal is used to request that the system return from asleep/suspend state to service a function wake initiated wake event.
|-
| 56
| NGFF_WIFI_DISABLE#
| O
| Aactive Low,when applied by the system it will disable radio operation on the Adapter that implement radio frequency applications.
|-
| 57
| GND
|  
| Ground
|-
| 58
| EKEY_SDA
| I/O
| I2C data.
|-
| 59
| N/A
|  
| Not Applicable
|-
| 60
| EKEY_SCL
| I
| I2C clock input from host.
|-
| 61
| N/A
|  
| Not Applicable
|-
| 62
| EKEY1_ALERT#
| O
| Active Low.IRQ line to host processor.
|-
| 63
| GND
|  
| Ground
|-
| 64
| N/A
|  
| Not Applicable
|-
| 65
| N/A
|  
| Not Applicable
|-
| 66
| N/A
|  
| Not Applicable
|-
| 67
| N/A
|  
| Not Applicable
|-
| 68
| N/A
|  
| Not Applicable
|-
| 69
| GND
|  
| Ground
|-
| 70
| N/A
|  
| Not Applicable
|-
| 71
| N/A
|  
| Not Applicable
|-
| 72
| +V3.3E_M.2
|  
| 3.3 V source
|-
| 73
| N/A
|  
| Not Applicable
|-
| 74
| +V3.3E_M.2
|  
| 3.3 V source
|-
| 75
| EKEY_CARD_PRSNT#
| I
| The Signal is to control TS3A44159PWR and TS3A27518ERTWR output.
|}

[[File:AOM-DB3500 M2 E1.png|700x600px|AOM-DB3500 M2 E1.png]][[File:AOM-DB3500 M2 E1 Pin.png|RTENOTITLE]]

=== '''J8 M2_E1 Power Setting''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| '''Pin'''
| '''Function'''
|-
| J8（1-2）
| M2_E1 power 3.3V (Default)
|-
| J8（2-3）
| M2_E1 power 3.8V
|}

=== '''J9 M.2_B Power Setting''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| '''Pin'''
| '''Function'''
|-
| J9（1-2）
| (B2B pin B76-B79) to M2_E1 (Default)
|-
| J9（2-3）
| UART1 (B2B pin B76-B79) to M2_E2
|}

=== '''Configure WIFI''' ===

1、Click the network icon in the top right corner of the screen and click the line of “Available networks” to select a Wi-Fi connection (for example: Advantech for guest)

[[File:ASR-A501 WIFI 1.png|RTENOTITLE]]

2、Enter the Wi-Fi password to connect to the device.

[[File:ASR-A501 WIFI 2.png|RTENOTITLE]]

3、If the password is correct, the device will connect quickly.

[[File:ASR-A501 WIFI 3.png|RTENOTITLE]]

After connection, Wi-Fi will create a net point “wlan0”.
<pre># ping -I wlan0 www.advantech.com
</pre>

=== '''BT（For example：“Mate 50 Pro”）''' ===

Step1：Click “Applications” -> “Settings”-> “Bluetooth manager”. Click the “Search” button to search for Bluetooth devices.

[[File:ROM-6881 BT1.png|500x300px|ROM-6881 BT1.png]]

Step2：Right-click to select a device, such as “Mate 50 Pro”, and Connect Bluetooth.

[[File:ROM-6881 BT2.png|500x300px|ROM-6881 BT2.png]]

Step3：AOM-3821 will start sending files when the receiver device, such as “Mate 50 Pro”, confirms bluetooth reception.

[[File:ROM-6881 BT3.png|500x300px|ROM-6881 BT3.png]] [[File:ROM-6881 BT3 1.png|500x300px|ROM-6881 BT3 1.png]]

Step4：View the location and information of the sent file.

[[File:AFE-E630 BT 162BS.png|RTENOTITLE]]

=== '''SATA（model:IM2S3334-512GCTB4）''' ===

M.2_E-KEY PCIE TEST:
<pre># fw_setenv combphy1 sata
# reboot
# fdisk -l /dev/sda</pre>

[[File:AOM-3841 SATA IM2S.png]]

AOM-3841 M.2 B Key——5G（PCIE型）

2026-03-18T06:12:58Z

Xingxing.li:

=== '''5G''' ===

AOM-3841 supports RM520NGLAA(PCIe ,Advantech PN: 968DD00342). First set M.2_B-KEY to PCIe Mode:
<pre># fw_setenv combphy1 pcie
# reboot</pre>

=== '''M.2_B Key Pin define''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="4" | '''M.2_B  M.2_B Connector Pin Definition'''
|-
| style="width: 42px;" | '''Pin'''
| style="width: 166px;" | '''Signal '''
| style="width: 40px;" | '''1/O'''
| style="width: 971px;" | '''Description'''
|-
| style="width: 42px;" | 1
| style="width: 166px;" | GND(Default NC)
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 2
| style="width: 166px;" | +V3.3B_M.2
| style="width: 40px;" |  
| style="width: 971px;" | 3.3V source
|-
| style="width: 42px;" | 3
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 4
| style="width: 166px;" | +V3.3B_M.2
| style="width: 40px;" |  
| style="width: 971px;" | 3.3V source
|-
| style="width: 42px;" | 5
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 6
| style="width: 166px;" | BKEY_PWR_Z_OFF
| style="width: 40px;" | I
| style="width: 971px;" | Active Low. A single control to turn Off WWAN solution
|-
| style="width: 42px;" | 7
| style="width: 166px;" | BKEY_USB_D+
| style="width: 40px;" | O
| style="width: 971px;" | USB Data + Differential Signal.
|-
| style="width: 42px;" | 8
| style="width: 166px;" | BKEY_W_DISABLE1#
| style="width: 40px;" | O
| style="width: 971px;" | Aactive Low,when applied by the system it will disable radio operation on the Adapter that implement radio frequency applications.
|-
| style="width: 42px;" | 9
| style="width: 166px;" | BKEY_USB_D-
| style="width: 40px;" | I/O
| style="width: 971px;" | USB Data - Differential Signal.
|-
| style="width: 42px;" | 10
| style="width: 166px;" | LED1#_M2_B
| style="width: 40px;" | O
| style="width: 971px;" | The Adapters’ status indicators via LED devices.
|-
| style="width: 42px;" | 11
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 12-19
| style="width: 166px;" | Moudle Key
| style="width: 40px;" |  
| style="width: 971px;" | Moudle Key
|-
| style="width: 42px;" | 20
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 21
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 22
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 23
| style="width: 166px;" | BKEY_WOWWAN#_GPIO
| style="width: 40px;" | O
| style="width: 971px;" | Used to wake the Platform by the WWAN device
|-
| style="width: 42px;" | 24
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 25
| style="width: 166px;" | BKEY_DPR_1.8
| style="width: 40px;" | O
| style="width: 971px;" | This signal is an input directly to the WWAN Adapter from a suitable SAR sensor.
|-
| style="width: 42px;" | 26
| style="width: 166px;" | BKEY_W_DISABLE2#
| style="width: 40px;" | O
| style="width: 971px;" | Aactive Low,when applied by the system it will disable radio operation on the Adapter that implement radio frequency applications.
|-
| style="width: 42px;" | 27
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 28
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 29
| style="width: 166px;" | BKEY_USB3.0_RX-
| style="width: 40px;" | I/O
| style="width: 971px;" | USB3.0 RX - Differential signal.
|-
| style="width: 42px;" | 30
| style="width: 166px;" | UIM_RESET
| style="width: 40px;" | I
| style="width: 971px;" | UIM reset signal.
|-
| style="width: 42px;" | 31
| style="width: 166px;" | BKEY_USB3.0_RX+
| style="width: 40px;" | I/O
| style="width: 971px;" | USB3.0 RX+ Differential signal.
|-
| style="width: 42px;" | 32
| style="width: 166px;" | UIM_CLK
| style="width: 40px;" | I
| style="width: 971px;" | UIM clock signal.
|-
| style="width: 42px;" | 33
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 34
| style="width: 166px;" | UIM_DATA
| style="width: 40px;" | I/O
| style="width: 971px;" | UIM data signal.
|-
| style="width: 42px;" | 35
| style="width: 166px;" | BKEY_USB3.0_TX-
| style="width: 40px;" | I/O
| style="width: 971px;" | USB3.0 TX - Differential signal.
|-
| style="width: 42px;" | 36
| style="width: 166px;" | UIM_VCC
| style="width: 40px;" | I
| style="width: 971px;" | Power source for the UIM.
|-
| style="width: 42px;" | 37
| style="width: 166px;" | BKEY_USB3.0_TX+
| style="width: 40px;" | I/O
| style="width: 971px;" | USB3.0 TX + Differential signal.
|-
| style="width: 42px;" | 38
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 39
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 40
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 41
| style="width: 166px;" | BKEY_PERN0
| style="width: 40px;" | O
| style="width: 971px;" | PCIe RX - Differential signal.
|-
| style="width: 42px;" | 42
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 43
| style="width: 166px;" | BKEY_PERP0
| style="width: 40px;" | O
| style="width: 971px;" | PCIe RX + Differential signal.
|-
| style="width: 42px;" | 44
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 45
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 46
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 47
| style="width: 166px;" | BKEY_PETN0
| style="width: 40px;" | I
| style="width: 971px;" | PCIe TX - Differential signal.
|-
| style="width: 42px;" | 48
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 49
| style="width: 166px;" | BKEY_PETP0
| style="width: 40px;" | I
| style="width: 971px;" | PCIe TX + Differential signal.
|-
| style="width: 42px;" | 50
| style="width: 166px;" | BKEY_PERST#
| style="width: 40px;" | I
| style="width: 971px;" | Active Low.PCIe Reset is a functional reset to the card.
|-
| style="width: 42px;" | 51
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 52
| style="width: 166px;" | BKEY_CLKREQ#
| style="width: 40px;" | I/O
| style="width: 971px;" | Active Low.PCIe Clock Request is a reference clock request signal.
|-
| style="width: 42px;" | 53
| style="width: 166px;" | BKEY_PCIE_CLK-
| style="width: 40px;" | I
| style="width: 971px;" | PCIe Reference Clock signals (100 MHz)
|-
| style="width: 42px;" | 54
| style="width: 166px;" | BKEY_PEWAKE#
| style="width: 40px;" | I/O
| style="width: 971px;" |
Active Low. When the Adapter supports wakeup, this signal is used to request that the system return from asleep/suspend state to service a  function-initiated wake event.

|-
| style="width: 42px;" | 55
| style="width: 166px;" | BKEY_PCIE_CLK+
| style="width: 40px;" | I
| style="width: 971px;" | PCIe Reference Clock signals (100 MHz)
|-
| style="width: 42px;" | 56
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 57
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 58
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 59
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 60
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 61
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 62
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 63
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 64
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 65
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 66
| style="width: 166px;" | N/A
| style="width: 40px;" |  
| style="width: 971px;" | Not Applicable
|-
| style="width: 42px;" | 67
| style="width: 166px;" | BKEY_RESET#
| style="width: 40px;" | I
| style="width: 971px;" | Active Low.The single control to Reset the WWAN solution.
|-
| style="width: 42px;" | 68
| style="width: 166px;" | BKEY_CLK
| style="width: 40px;" | I
| style="width: 971px;" | 32.768 kHz clock supply input that is provided by the Platform chipset to reduce power and cost for the Adapter.
|-
| style="width: 42px;" | 69
| style="width: 166px;" | GND(Default NC)
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 70
| style="width: 166px;" | +V3.3B_M.2
| style="width: 40px;" |  
| style="width: 971px;" | 3.3 V source
|-
| style="width: 42px;" | 71
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 72
| style="width: 166px;" | +V3.3B_M.2
| style="width: 40px;" |  
| style="width: 971px;" | 3.3 V source
|-
| style="width: 42px;" | 73
| style="width: 166px;" | GND
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|-
| style="width: 42px;" | 74
| style="width: 166px;" | +V3.3B_M.2
| style="width: 40px;" |  
| style="width: 971px;" | 3.3 V source
|-
| style="width: 42px;" | 75
| style="width: 166px;" | GND(Default NC)
| style="width: 40px;" |  
| style="width: 971px;" | Ground
|}

[[File:AOM-DB3500 M.2 B key.png|700x600px|AOM-DB3500 M.2 B key.png]][[File:AOM-DB3500 M.2 B key pin define.png|RTENOTITLE]]

=== '''Configure 5G''' ===

1、Power off the device, then insert 5G module and SIM card.

Note：Make sure the device is power off before insert 4G/5G module and SIM card, otherwise the device, 4G/5G module and/or SIM card may be damaged.

2、Power on the device, Click network connection icon 

[[File:AFE-E630 4G EC20 1.png|RTENOTITLE]]

Then choose “New Mobile Broadband connection”.

[[File:AFE-E630 4G EC20 2.png|RTENOTITLE]]

then you will see the following window, click "Next" button to the next step.

[[File:RK3288 Debian 4G setup.png|550px|RTENOTITLE]]

3、Choose Provider's country or region of the SIM card you insert in STEP0.

[[File:RK3288 Debian 4G Provider Country.png|550px|RTENOTITLE]]

4、Choose or Set the Provider's name.

[[File:ROM-6881 4G Providers name.png|550x300px|ROM-6881 4G Providers name.png]]

4、Choose or Set the Provider's name.

[[File:ROM-6881 4G APN.png|550x300px|ROM-6881 4G APN.png]]

5、Choose or Set APN.

[[File:ROM-6881 4G APN.png|550x300px|ROM-6881 4G APN.png]]

6、Confirm your config and finish.

[[File:ROM-6881 4G finish.png|550x300px|ROM-6881 4G finish.png]]

After connection, 4Gwill create a net point “wwan0”

[[File:AOM-3841 5G PCIE.png]]
<pre># ping -I wwan0 www.baidu.com</pre>

AOM-3841 Display（HDMI、DP、EDP）

2026-03-18T03:03:25Z

Xingxing.li:

=== '''HDMI/DP Screen''' ===

HDMI and DP support multi resolutions. They can be configured by GUI. HDMI and DP support 4K60Hz display.

=== '''Configure Resolution for HDMI/DP screen''' ===

1. Click “Applications” -> “Settings”->“Display”. 2. Choose “HDMI-1”or “DP-1”, then choose “Resolution”. 3. Click “Apply”.

[[File:ROM-6881 HDMI DP screen.png.jpg|RTENOTITLE]]

=== '''HW Setting：''' ===

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="2" | '''J15：EDP VDD Power Select'''
|-
| '''Pin'''
| '''Function'''
|-
| 3-5
| +V3.3（Default）
|-
| 1-3
| +V5
|-
| 3-4
| +V12
|-
| Other
|
No Function

Do Note Use

|}

'''[[File:AOM-DB3500 J15.png|700x500px|AOM-DB3500 J15.png]]'''

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="2" | '''J16：EDP Backlight Power Select'''
|-
| '''Pin'''
| '''Function'''
|-
| 1-2
| +V5
|-
| 3-4
| +V12（Default）
|}

[[File:AOM-DB3500 J16.png|700x500px|AOM-DB3500 J16.png]]

== '''SW setting：''' ==

=== '''Multi-Display''' ===

'''AOM-3841 supports three kinds of displays — HDMI, DSI, DP'''

'''1. DP physical interface is Type-C. 2. DP is always open and cannot be closed.'''

{| border="1" cellpadding="1" cellspacing="1"
|-
| colspan="2" | '''Support EDP Panel'''
|-
| Panel Model
| B156XTN07.1
|}

'''EDP HW Setting：'''

J12=>2-3 EDP HDP

J15=>3-5 （+VDD_EDP）+3.3V （B156XTN07.1）

J16=>2-3 （BKLT_VDD_LCD1）+12V

[[File:AOM-DB3500 EDP.png|RTENOTITLE]]

=== '''Dual-Display''' ===

"HDMI + DP” is the default configuration.

*HDMI + DP
<pre># fw_setenv display0 hdmi0-default
# fw_setenv display1
# reboot</pre>

*DSI + DP
<pre># fw_setenv display0
# fw_setenv display1 mipi0-gl0uan
# reboot</pre>

=== '''Triple-Display''' ===

*HDMI + DSI + DP
<pre># fw_setenv display0 hdmi0-default
# fw_setenv display1 mipi0-gl0uan
# reboot</pre>

AOM-3841 AUDIO MIC1/OUT1 & MIC2/OUT2

2026-03-17T07:53:04Z

Xingxing.li:

=== '''AOM-3841 supports three kinds of sound cards:''' ===

“1 rt5640-codec”(9696EG57001) “2 hdmi”, “3 dp0

'''Set the default audio output when playing media files.''' 1. Click “Applications” ->”Multimedia”->”PulseAudio Volume Control”. 2. Select “Build-in Audio stereo” for rt5640-codec output, or select “HDMI” for  HDMI output, or select “Build-in Audio Display Port 1 Stereo” for DP output.

[[File:AOM-3841 Audio.jpg|RTENOTITLE]]

'''Mute and Volume Control''' Mute and volume can be configured by GUI.

[[File:AOM-3841 Audio1.jpg|RTENOTITLE]]

 

=== '''AUDIO MIC1/OUT1（Compatible with ROM-EG57）''' ===

'''HW Pin Header'''

[[File:AOM-DB3500 AUDIO 1.png|700x600px|AOM-DB3500 AUDIO 1.png]][[File:AOM-DB3500 AUDIO PIn header.png|RTENOTITLE]]

{| border="1" cellpadding="1" cellspacing="1" style="width: 507px;"
|-
| colspan="4" style="width: 497px;" | '''I2S0 Connector Pin Definition'''
|-
| style="width: 55px;" | '''Pin'''
| style="width: 156px;" | '''Signal'''
| style="width: 54px;" | '''I/O'''
| style="width: 219px;" | '''Description'''
|-
| style="width: 55px;" | 1
| style="width: 156px;" | I2S0_VDDA
| style="width: 54px;" |  
| style="width: 219px;" | I2S0 3.3V source
|-
| style="width: 55px;" | 2
| style="width: 156px;" | GND
| style="width: 54px;" |  
| style="width: 219px;" | Ground
|-
| style="width: 55px;" | 3
| style="width: 156px;" | I2S0_VDDA
| style="width: 54px;" |  
| style="width: 219px;" | I2S0 3.3V source
|-
| style="width: 55px;" | 4
| style="width: 156px;" | I2S0_SDIN_3.3
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Serial Data IN 3.3V Level
|-
| style="width: 55px;" | 5
| style="width: 156px;" | I2S0_SDOUT_3.3
| style="width: 54px;" | O
| style="width: 219px;" | I2S0 Serial Data OUT 3.3V Level
|-
| style="width: 55px;" | 6
| style="width: 156px;" | I2S0_LRCK_3.3
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Left/Right Clock
|-
| style="width: 55px;" | 7
| style="width: 156px;" | I2S0_BCLK_3.3
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Bit Clock
|-
| style="width: 55px;" | 8
| style="width: 156px;" | AUD0_MCK
| style="width: 54px;" | I
| style="width: 219px;" | Audio0 Master Clock
|-
| style="width: 55px;" | 9
| style="width: 156px;" | N/A
| style="width: 54px;" |  
| style="width: 219px;" | Not Applicable
|-
| style="width: 55px;" | 10
| style="width: 156px;" | GND
| style="width: 54px;" |  
| style="width: 219px;" | Ground
|-
| style="width: 55px;" | 11
| style="width: 156px;" | I2S0_I2C_CLK
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 I2C clock input from host.
|-
| style="width: 55px;" | 12
| style="width: 156px;" | MIC_BIAS1
| style="width: 54px;" | I
| style="width: 219px;" | For I2S0 Microphone Bias Voltage
|-
| style="width: 55px;" | 13
| style="width: 156px;" | I2S0_I2C_DAT
| style="width: 54px;" | I/O
| style="width: 219px;" | I2S0 I2C Data
|-
| style="width: 55px;" | 14
| style="width: 156px;" | GND
| style="width: 54px;" |  
| style="width: 219px;" | Ground
|-
| style="width: 55px;" | 15
| style="width: 156px;" | N/A
| style="width: 54px;" |  
| style="width: 219px;" | Not Applicable
|-
| style="width: 55px;" | 16
| style="width: 156px;" | I2S0_HP_R
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Right Headphone
|-
| style="width: 55px;" | 17
| style="width: 156px;" | I2S0_MIC_IN
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Microphone IN
|-
| style="width: 55px;" | 18
| style="width: 156px;" | GND
| style="width: 54px;" |  
| style="width: 219px;" | Ground
|-
| style="width: 55px;" | 19
| style="width: 156px;" | GND
| style="width: 54px;" |  
| style="width: 219px;" | Ground
|-
| style="width: 55px;" | 20
| style="width: 156px;" | I2S0_HP_L
| style="width: 54px;" | I
| style="width: 219px;" | I2S0 Left Headphone
|}

=== '''AUDIO MIC2/OUT2（Compatible with ROM-EG57）''' ===

'''HW Pin Header'''

[[File:AOM-DB3500 AUDIO2.png|700x600px|AOM-DB3500 AUDIO2.png]][[File:AOM-DB3500 AUDIO PIn header.png|RTENOTITLE]]

{| border="1" cellpadding="1" cellspacing="1" style="width: 582px;"
|-
| colspan="4" style="width: 572px;" | '''I2S1 Connector Pin Definition'''
|-
| style="width: 52px;" | '''Pin'''
| style="width: 198px;" | '''Signal'''
| style="width: 49px;" | '''I/O'''
| style="width: 260px;" | '''Description'''
|-
| style="width: 52px;" | 1
| style="width: 198px;" | I2S1_VDDA
| style="width: 49px;" |  
| style="width: 260px;" | I2S1 3.3V source
|-
| style="width: 52px;" | 2
| style="width: 198px;" | GND
| style="width: 49px;" |  
| style="width: 260px;" | Ground
|-
| style="width: 52px;" | 3
| style="width: 198px;" | I2S1_VDDA
| style="width: 49px;" |  
| style="width: 260px;" | I2S1 3.3V source
|-
| style="width: 52px;" | 4
| style="width: 198px;" | I2S1_SDIN_3.3
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Serial Data IN 3.3V Level
|-
| style="width: 52px;" | 5
| style="width: 198px;" | I2S1_SDOUT_3.3
| style="width: 49px;" | O
| style="width: 260px;" | I2S1 Serial Data OUT 3.3V Level
|-
| style="width: 52px;" | 6
| style="width: 198px;" | I2S1_LRCK_3.3
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Left/Right Clock
|-
| style="width: 52px;" | 7
| style="width: 198px;" | I2S1_BCLK_3.3
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Bit Clock
|-
| style="width: 52px;" | 8
| style="width: 198px;" | AUD1_MCK
| style="width: 49px;" | I
| style="width: 260px;" | Audio1 Master Clock
|-
| style="width: 52px;" | 9
| style="width: 198px;" | N/A
| style="width: 49px;" |  
| style="width: 260px;" | Not Applicable
|-
| style="width: 52px;" | 10
| style="width: 198px;" | GND
| style="width: 49px;" |  
| style="width: 260px;" | Ground
|-
| style="width: 52px;" | 11
| style="width: 198px;" | I2S1_I2C_CLK
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 I2C clock input from host.
|-
| style="width: 52px;" | 12
| style="width: 198px;" | MIC_BIAS2
| style="width: 49px;" | I
| style="width: 260px;" | For I2S1 Microphone Bias Voltage
|-
| style="width: 52px;" | 13
| style="width: 198px;" | I2S1_I2C_DAT
| style="width: 49px;" | I/O
| style="width: 260px;" | I2S1 I2C Data
|-
| style="width: 52px;" | 14
| style="width: 198px;" | GND
| style="width: 49px;" |  
| style="width: 260px;" | Ground
|-
| style="width: 52px;" | 15
| style="width: 198px;" | N/A
| style="width: 49px;" |  
| style="width: 260px;" | Not Applicable
|-
| style="width: 52px;" | 16
| style="width: 198px;" | I2S1_HP_R
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Right Headphone
|-
| style="width: 52px;" | 17
| style="width: 198px;" | I2S1_MIC_IN
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Microphone IN
|-
| style="width: 52px;" | 18
| style="width: 198px;" | GND
| style="width: 49px;" |  
| style="width: 260px;" | Ground
|-
| style="width: 52px;" | 19
| style="width: 198px;" | GND
| style="width: 49px;" |  
| style="width: 260px;" | Ground
|-
| style="width: 52px;" | 20
| style="width: 198px;" | I2S1_HP_L
| style="width: 49px;" | I
| style="width: 260px;" | I2S1 Left Headphone
|}

=== '''Audio Test''' ===

=== '''Get sound card ID''' ===
<pre># cat /proc/asound/cards
0 [rockchiprt5640c]: simple-card - rockchip,rt5640-codec
 rockchip,rt5640-codec
1 [rockchipdp0 ]: rockchip-dp0 - rockchip-dp0
 rockchip-dp0
2 [rockchiphdmi ]: rockchip-hdmi - rockchip-hdmi
 rockchip-hdmi</pre>

=== '''Record''' ===

Take Card ID 0 for example:
<pre># CARD_ID=0
# arecord -c 2 -Dplughw:$CARD_ID,0 -f S16_LE -r 16000 -d 10 -t wav 
test.wav  
</pre>

=== '''Playback.''' ===

Take Card ID 0 for example:
<pre># CARD_ID=0
# arecord -c 2 -Dplughw:$CARD_ID,0 -f S16_LE -r 16000 -d 10 -t wav 
test.wav</pre>

See details of the usage of “aplay”: 
<pre># aplay --help
… …
-D, --device=NAME select PCM by name
-t, --file-type TYPE file type (voc, wav, raw or au)
… …
</pre>

=== '''RKTool指令：''' ===
<pre># cat /proc/asound/cards
# /tools/test/adv/audio/audio_record_test.sh 0
# /tools/test/adv/audio/audio_play_test.sh 0</pre>

[[File:AOM-3841 Audio test.png|RTENOTITLE]] [[File:AOM-3841 Audio test1.png|RTENOTITLE]]

AOM-3841 AUDIO MIC1/OUT1

2026-03-17T06:43:59Z

Xingxing.li:

AOM-3841 Button（RST、PWR）

2026-03-17T06:30:26Z

Xingxing.li: Created page with " 700x600px"

[[File:AOM-DB3500 Button.png|700x600px]]

AOM-3841 UART RS232（DEBUG、COM1、COM2、M.2 E1）

2026-03-17T03:19:12Z

Xingxing.li:

=== '''UART''' ===

User Debian/Linux UART/serial port access is through the tty-devices. The ttydevices have different names depending on UART drivers for different boards.

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| '''Device Node'''
| '''COM Port Name'''
|-
| /dev/ttyFIQ0
|  Debug
|-
| /dev/ttyS2
| COM2  (COM1_2 connector RS232 2-wire)
|-
| /dev/ttyS4
| COM1  (COM1_2 connector RS232 4-wire)
|-
| /dev/ttyS10
| M.2_E1(UART)
|}

=== '''DEBUG Port Connection''' ===

1.Connect the debug port cable on AOM-DB3500.

2.Connect it to your PC with a USB to COM Cable.

{| border="1" cellpadding="1" cellspacing="1" style="width: 254px;"
|-
| colspan="2" style="width: 244px;" | '''DEBUG Pin Connector'''
|-
| style="width: 72px;" | '''Pin'''
| style="width: 169px;" | '''Signal'''
|-
| style="width: 72px;" | 1
| style="width: 169px;" | NC
|-
| style="width: 72px;" | 2
| style="width: 169px;" | RX_DEBUG
|-
| style="width: 72px;" | 3
| style="width: 169px;" | TX_DEBUG
|-
| style="width: 72px;" | 4
| style="width: 169px;" | NC
|-
| style="width: 72px;" | 5
| style="width: 169px;" | GND
|-
| style="width: 72px;" | 6
| style="width: 169px;" | NC
|-
| style="width: 72px;" | 7
| style="width: 169px;" | RTS#
|-
| style="width: 72px;" | 8
| style="width: 169px;" | CTS#
|-
| style="width: 72px;" | 9
| style="width: 169px;" | NC
|}

=== '''Debug Port Settings''' ===

AOM-3841 can communicate with a host server using serial cables. Common serial communication programs such as HyperTerminal, Tera Term, or PuTTY can be used in this case. The example below describes the serial terminal setup using HyperTerminal on a Windows host: 1. Connect AOM-3841 with your PC using a serial cable. 2. Open HyperTerminal on your Windows PC, and select the settings demonstrated in the photo below. 3. Insert a power adapter into the DC jack and power up the board. The Debug console log will be displayed on the terminal screen.

[[File:AOM-3841 debug port.jpg|700x600px|AOM-3841 debug port.jpg]]

=== '''RS232——COM1_2''' ===

[[File:AOM-DB3500 COM1 2.png|700x600px|AOM-DB3500 COM1 2.png]][[File:AOM-DB3500 COM1 2 Pin header.png|RTENOTITLE]]

{| border="1" cellpadding="1" cellspacing="1" style="width: 476px;"
|-
| colspan="4" style="width: 466px;" | '''COM1_2 Connector, RS232 Mode Pin Definition'''
|-
| style="width: 43px;" | '''Pin'''
| style="width: 156px;" | '''Signal'''
| style="width: 37px;" | '''I/O'''
| style="width: 217px;" | '''Description'''
|-
| style="width: 43px;" | 1
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 2
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 3
| style="width: 156px;" | COM1_RX_485+
| style="width: 37px;" | O
| style="width: 217px;" | COM1 RS232 Receive Data
|-
| style="width: 43px;" | 4
| style="width: 156px;" | COM1_RTS#
| style="width: 37px;" | I
| style="width: 217px;" | COM1 Request to Send
|-
| style="width: 43px;" | 5
| style="width: 156px;" | COM1_TXD_422-
| style="width: 37px;" | I
| style="width: 217px;" | COM1 RS232 Transmit Data
|-
| style="width: 43px;" | 6
| style="width: 156px;" | COM1_CTS#
| style="width: 37px;" | O
| style="width: 217px;" | COM1 Clear to Send
|-
| style="width: 43px;" | 7
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 8
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 9
| style="width: 156px;" | GND
| style="width: 37px;" |  
| style="width: 217px;" | Ground
|-
| style="width: 43px;" | 10
| style="width: 156px;" | GND
| style="width: 37px;" |  
| style="width: 217px;" | Ground
|-
| style="width: 43px;" | 11
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 12
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 13
| style="width: 156px;" | COM2_RX_485+
| style="width: 37px;" | O
| style="width: 217px;" | COM2 RS232 Receive Data
|-
| style="width: 43px;" | 14
| style="width: 156px;" | COM2_RTS#
| style="width: 37px;" | I
| style="width: 217px;" | COM2 Request to Send
|-
| style="width: 43px;" | 15
| style="width: 156px;" | COM2_TXD_422-
| style="width: 37px;" | I
| style="width: 217px;" | COM2 RS232 Transmit Data
|-
| style="width: 43px;" | 16
| style="width: 156px;" | COM2_CTS#
| style="width: 37px;" | O
| style="width: 217px;" | COM2 Clear to Send
|-
| style="width: 43px;" | 17
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 18
| style="width: 156px;" | N/A
| style="width: 37px;" |  
| style="width: 217px;" | Not Applicable
|-
| style="width: 43px;" | 19
| style="width: 156px;" | GND
| style="width: 37px;" |  
| style="width: 217px;" | Ground
|-
| style="width: 43px;" | 20
| style="width: 156px;" | GND
| style="width: 37px;" |  
| style="width: 217px;" | Ground
|}

=== '''Configure Parameters''' ===

Use “stty” command to configure serial port parameters. The commonly used parameters include “Baud rate”, “Data bits”, “Stop bits”, “Parity”, “Flow control”.

See details of the usage of “stty”:
<pre># stty --help
… …
csN set character size to N bits, N in [5..8]
[-]cstopb use two stop bits per character (one with '-')
[-]parenb generate parity bit in output and expect parity bit in input
[-]crtscts enable RTS/CTS handshaking
…</pre>

For example, set COM1 “Baud rate” to 115200 “Data bits” to 8 “Stop bits” to 1 “Parity” to None “Flow control” to None
<pre># stty -F /dev/ttyS0 115200 cs8 -parenb -cstopb</pre>

=== '''Send and receive data''' ===

Taking COM1 as receiver or sender (An external COM is required to do the sending or receiving). For example, AOM-3841 is responsible for receiving and inputting instructions. The PC computer is connected via a cable and COM1. The PC computer uses the PuTTY serial port tool, opens the COM port, configures the baud rate to 115200, data bits to 8, stop bits to 1, parity to none, flow control to none, and sends “pass” to the serial port assistant. If no error, the external COM receiver will receive “pass”.
<pre># #---- COM1 as receiver ----# #
# stty -F /dev/ttyS4 115200 cs8 -cstopb -parenb
# cat /dev/ttyS4 &</pre>
<pre># #---- COM1 as sender ----# #
# stty -F /dev/ttyS4 115200 cs8 -cstopb -parenb
# echo pass > /dev/ttyS4
# #----If no error, the external COM receiver will receive “pass”----# #
pass</pre>

Note!

1.Receiver should run before sender. 2.The "serial port parameters" should be the same for sender and  receiver.

AOM-3841 DC IN

2026-03-17T02:10:18Z

Xingxing.li: Created page with " === '''DC_IN Pin Connector（VIN=24V）''' === {| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" |- | colspan="3" | '''DC_IN Pin Connector''' |- | '''Pin''..."

=== '''DC_IN Pin Connector（VIN=24V）''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| colspan="3" | '''DC_IN Pin Connector'''
|-
| '''Pin'''
| '''Signal'''
| '''Description'''
|-
| 1
| PGND
| Power Ground
|-
| 2
| DC_IN
| Direct Current Input
|-
| 3
| DC_IN
| Direct Current Input
|-
| 4
| PGND
| Power Ground
|}

[[File:AOM-DB3500 DC IN.png|500x500px|AOM-DB3500 DC IN.png]][[File:AOM-DB3500 DC Pin.png|500x500px|AOM-DB3500 DC Pin.png]]

AOM-3841 （Develop Board AOM-DB3500）Support List Desocroption

2026-03-17T02:02:53Z

Xingxing.li:

All test tools must be verified using the AOM-3841 evaluation kit (Develop. Board AOM-DB3500). Please prepare the required test fixtures before verifying each specified I/O. If you have any problems during testing, please contact Advantech for help.

{| border="1" cellpadding="1" cellspacing="1" style="width: 580px;"
|-
| style="width: 107px;" | '''Support List'''
| style="width: 248px;" | '''Description'''
| style="width: 205px;" | '''Advantech Part No.'''
|-
| style="width: 107px;" | Audio
| style="width: 248px;" | ALC5640-VB-CGT Audio Codec
| style="width: 205px;" | 9696EG57001
|-
| style="width: 107px;" | LAN
| style="width: 248px;" | RTL8211FS-CG LAN Board
| style="width: 205px;" | 9696EG6A000
|-
| style="width: 107px;" | 5G
| style="width: 248px;" |
RM520NGLAA-M20-SGASA (M.2 KeyB)  USB3.1/PCIE3.0

| style="width: 205px;" | 968DD00342
|-
| style="width: 107px;" | WIFI6
| style="width: 248px;" | Broadcom AP6275P, (M.2 E Key)- 40°C~85°C PCIE+UART
| style="width: 205px;" | AIW-162BS-GI1
|-
| style="width: 107px;" | Camera
| style="width: 248px;" | MIPI Camera IMX415
| style="width: 205px;" | ROM-EC50+ CRK8F4403-V1
|-
| style="width: 107px;" | SPI/I2C
| style="width: 248px;" | SPI/I2C Board
| style="width: 205px;" | 9696EG70000
|-
| style="width: 107px;" | MIPI Panel
| style="width: 248px;" | G101UAN02.0?1920 x 1200
| style="width: 205px;" | XMIT-G101UAN02.0
|}

AOM-3841 on AOM-DB3500 Usering bootup sd disk made by SDDiskTool.

2026-03-13T06:31:48Z

Xingxing.li:

== '''一、Create“update.img”''' ==

First, extract the image file, and then use the RKTool tool to generate the "update.img" .

'''Make an SD card (for example: A laptop with Windows 10 PC, system: 22H1)'''

[[File:PC specification.png|RTENOTITLE]]

 

=== '''File.Open the RKTool tool in the following link, as shown in the picture below.''' ===

[[File:AOM-3841 SD1.png|RTENOTITLE]]

'''Double'-click the folder "AOM3841A1AIM38DIV110025_2025-09-24 \ ro'ckdev" within "mkupdate. Bat" to run the program, to generate "update. Img" file.'''

'''[[File:AOM-3841 SD1.1.png|RTENOTITLE]]'''

[[File:AOM-3841 SD1.2.png|RTENOTITLE]]

[[File:AOM-3841 SD1.3.png|RTENOTITLE]]

'''Make an SD card (for example: A laptop with Windows 10 PC, system: 22H1)'''

For example, the PC used is a laptop. The specifications are as follows：

[[File:Windows OS.png|RTENOTITLE]]

'''Please install the DriverAssitant_v5.13 driver first.  Double-click the "DriverInstall.exe" program as shown in the following figure.'''

'''[[File:AOM-3841 SD1.4.png|RTENOTITLE]]'''

'''[[File:AOM-3821 SD3-1.png|RTENOTITLE]]'''

'''After successful installation, click "Confirm" and exit the program.'''

'''[[File:AOM-3821 SD3-2.png|RTENOTITLE]]'''

=== '''Change Tool language in config.ini, please change "Selected: to "2".''' ===

=== '''Prepare a Mirco SD card of 8GB (for example: 32GB) or more and insert it into the PC. Open the following path and double-click "SD_Firmware_Tool.exe".''' ===

'''[[File:AOM-3841 SDTool.png|RTENOTITLE]]'''

'''[[File:AOM-3841 SDTool1.1.png|RTENOTITLE]]  [[File:AOM-3821 SD Tool V1.78-2.png|RTENOTITLE]]'''

'''[[File:AOM-3841 SDTool1.2.png|RTENOTITLE]]'''

The Mirco SD card has been successfully produced. After clicking "Confirm", exit the program. Remove the Mirco SD card from the PC.

== '''二、Upgrade or Recovery AOM-3841''' ==

#'''Power off AOM-3841.'''
#'''Insert the upgrade SD card to AOM-3841.'''
#'''Power on AOM-3841. It will automatic enter recovery mode to upgrade system.'''
#'''If upgrade success, you will get the message “Please remove SD CARD!!!, wait'''
#'''for reboot” on screen and debug console.'''
#'''Remove SD card.'''

[[File:AOM-3841 SDTool finaly.png|RTENOTITLE]]

[[File:AOM-3841 SDTool uname.png]]

AOM-3841 on AOM-DB3500 Usering RKTool.

2026-03-02T07:00:19Z

Xingxing.li:

=== '''For example, the PC used is a laptop. The specifications are as follows：''' ===

[[File:PC specification.png|RTENOTITLE]]

Decompress the downloaded image on the PC.

=== '''List''' ===

'''1、Prepare a TYPE_C to USB cable.'''

[[File:ROM-5880 Type C cable.png|400x250px|ROM-5880 Type C cable.png]]

'''2、Prepare a DC_IN 24V 60W Adapter.（Advantech Part Number：96PSA-A60W24T2-3）'''

'''3、Prepare a USB to UART console cable.'''

'''4、Prepare an HDMI monitor and plug the HDMI cable into the HDMI port on the base plate.'''

=== '''The setup environment is as follows.''' ===

'''[[File:AOM-341 on AOM-DB3500 OTG Tool.png|RTENOTITLE]]'''

 

=== '''PC Install the driver''' ===

1、Extract Driver Assitant_v5.13.zip and follow these steps: Mounting driver.

[[File:AOM-3821 Driver Assitant v5.13.png|RTENOTITLE]]

2、Run the installer and wait for the installation to succeed.

[[File:ASR-A501 OTG RK v5.13.png|RTENOTITLE]][[File:ASR-A501 OTG v5.13.png|RTENOTITLE]]

3、Change Tool language in config.ini, please change "Selected: to "2"

选择工具语言:Selected=1(中文)<--Chinese ;Selected=2(英文)<-- English [Language] Kinds=2 Selected=2 LangPath=Language\

[[File:RSB-4810 set language method configini.PNG|RTENOTITLE]]

 

=== '''Enter into MASKROM mode''' ===

When the device boot up to android or debian, you can use ADB or Debug console, send command "reboot loader" . 

Or Press "ctrl + c" key when booting into uboot, until get the following information on debug console :

'''Android ：'''
<pre>Hit any key to stop autoboot: 0
rkboot # <INTERRUPT>
rkboot # loader</pre>

'''Debian ：'''
<pre>Hit any key to stop autoboot: 0
rkboot # <INTERRUPT>
rkboot # rbrom</pre>

'''Next:'''

SW1 setting: Switch all positions 1 to 6 to ON to force the device into "MASKROM" mode. After entering the MASKROM mode, switch positions 4 and 5 back to OFF.

[[File:AOM-3821 SW1 MASKROM.png|RTENOTITLE]]

 

=== '''Go to the RKDevTool_Release folder and run the RKDevTool.exe program.''' ===

1、Ensure that the path to the burned file is correct.

[[File:AOM-3841 OTG1.png|RTENOTITLE]]

2、After entering the "MASKROM" mode, click to execute and start the burning process.

Note：Suspend or shut down the virtual machine during this process; otherwise, the pop-up information may affect the burning results.

[[File:AOM-3841 OTG2.png|RTENOTITLE]]

[[File:AOM-3841 OTG3.png|RTENOTITLE]]

3、Please be patient. After the burning process is completed, the board will automatically restart once the burning is successful.

[[File:AOM-3841 OTG4.png]]

4、Check the system version.

[[File:AOM-3841 OTG5.png]]

AIM-Linux/BSP/NV/Linux Ubuntu OS Release note/AIR-021/air021a1 ubuntu22.04-jp6.2 v2.0.0 kernel-5.15.148 orin-nx orin-nano nx-16g nono 8g nvme

2026-03-02T05:51:23Z

Richard.chiang:

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" data-darkreader-inline-bgcolor="" style="--darkreader-inline-bgcolor: var(--darkreader-background-f8f8f8, #1c1e1f);" width="30%"
|-
| '''SOM '''
| AGX-ORIN
|-
| '''Jetpack version '''
| 6.2
|-
| '''L4T version '''
| 36.4.3
|-
| '''Kernel version '''
| 5.15.148
|-
| '''TensorRT'''
| 10.3.0.30 
|-
| '''DLA'''
|  
|-
| '''cuDNN'''
| 9.3.0.75 
|-
| '''CUDA'''
| 12.6.68 
|-
| '''VPI'''
| 3.2.4 
|-
| '''Docker '''
| NA 
|}

'''Change Log'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" data-darkreader-inline-bgcolor="" style="--darkreader-inline-bgcolor: var(--darkreader-background-f8f8f8, #1c1e1f);" width=""
|-
| '''Item'''
|
'''Change List'''

|
'''Description'''

|-
| '''1'''
| New Feature
| a. Edge AI SDK short link 
b. Prevent nvidia lt4 package auto update  
|-
| '''2'''
| Bug Fixed  
| a. Dns nameserver bug fixed 
|-
| '''3'''
| Known Issue 
| suspended error
|}

RK ALL EtherCAT

2026-03-02T03:34:08Z

Zhihao.zhu:

= Preface =

IgH EtherCAT is an open-source EtherCAT master station program running on the Linux system. The IgH EtherCAT master station communicates with the EtherCAT master module by constructing a Linux character device,  the application program achieves this communication through accessing the character device. The IgH EtherCAT development package comes with EtherCAT tools. These tools provide various commands that can run in the Linux user layer, enabling direct access and configuration of slave stations, such as setting slave station addresses, displaying bus configuration, displaying PDO data, reading and writing SDO parameters, etc.

= Install =

The customer downloads the customized version of the image (including EtherCAT)

= EtherCAT IgH Software Environment =

EtherCAT: Kernel space, User space, EtherCAT application.

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| style="text-align: center;" | Layer
| style="text-align: center;" | built-in
| style="text-align: center;" | purpose
|-
| style="text-align: center;" | KernelSpace
| style="text-align: center;" | Y
| Provide a real-time driven environment. RT-patch and ethercat driver
|-
| style="text-align: center;" | UserSpace
| style="text-align: center;" | Y
| ethercat, libethercat.so
|-
| style="text-align: center;" | Applicaton
| style="text-align: center;" | N
| Customer Application
|}

     

= EtherCAT IgH Test =

Using the "ethercat --help" command allows you to view the EtherCAT IgH tools. These tools can provide various information about the slaves connected to the master station, which can be helpful for writing the master station application programs. The following introduces the usage of several commonly used commands and parameters. The [] brackets indicate mandatory parameters, while the <> brackets represent optional parameters.

1. Set alias address

ethercat alias -p 0 0

2. Set alias address (The following example represents changing the alias of location 0 to 1)

ethercat alias -a 0 1

3. Output PDO information in C language format

ethercat cstruct

4. Output the identified slave stations

ethercat slaves 0 0(别名)):0（位置） PREOP + MADHT1505BA1

5. Output PDO information

ethercat pdos

6. Official document

[https://docs.etherlab.org/ethercat/1.5/doxygen/index.html https://docs.etherlab.org/ethercat/1.5/doxygen/index.html]  

= Application Development =

1. Power on the connection between the master station and the slave station of the board. 2. Check the slave device and verify the master-slave communication. 3. Reference for Application Development Flowchart.

[[File:EtherCAT App Dev Block.png|RTENOTITLE]]

= Performance Indicators and test =

During a one-millisecond period, the performance data of each supporting platform is as follows:

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| style="text-align: center;" | SoC
| style="text-align: center;" | Period
| style="text-align: center;" | Jitter delay
| style="text-align: center;" | Remark
|-
| style="text-align: center;" | RK3568
| style="text-align: center;" | 1ms
| style="text-align: center;" | 50us
| style="text-align: center;" | Not supported
|-
| style="text-align: center;" | RK3576
| style="text-align: center;" | 1ms
| style="text-align: center;" | 30us
| style="text-align: center;" | Not supported
|-
| style="text-align: center;" | RK3588
| style="text-align: center;" | 1ms
| style="text-align: center;" | 15us
| style="text-align: center;" | Supported
|}

EPC-R3220 Yocto 5.0 BSP User Guide

2026-02-27T02:59:10Z

Xingxing.li: Created page with " = {{DISPLAYTITLE:IoTGateway/BSP/Linux/TI/Yocto LBVC User Guide}} <!-- {| align="right" | <span class="fck_mw_magic" _fck_mw_customtag="true" _fck_mw_tagname="TOC" _fck_mw_ta..."

= {{DISPLAYTITLE:IoTGateway/BSP/Linux/TI/Yocto LBVC User Guide}} Introduction =

This page provides the steps to build the Processor SDK and individual components from source. The Processor SDK build is based on the Arago Project which provides a set of layers for OpenEmbedded and the Yocto Project targeting TI platforms.

This page will provide the basic steps required to recreate the Processor SDK along with a reference of Processor SDK specific configurations, build targets, and target devices. Also, tips and suggestions are provided along with links for more in-depth information.

= Getting Start =

== Prerequisites ==

=== Host Setup ===

Generally，for Linux development, you’ll need a host PC running Linux. In the development with the Advantech SDK, it is strongly recommend to use Ubuntu 22.04 LTS as the developing environment. This is because we have successfully tested our BSP on this OS version. Please install the Ubuntu 22.04 LTS on your PC/NB in advance.

=== Docker install and setting ===

If you don't have docker in your system, then you can follow the below steps to install docker and run it first.

To install Docker Engine on your platform please refer to Docker Installation Guide for details.

To pull ubuntu 22.04 image from Docker Hub
<div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ sudo docker pull advrisc/u22.04-amxxlbv1</div>
To create container
<div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ sudo docker run -it --name ${CONTAINER_NAME} -v ${WORKSPACE}:/home/adv/yocto_bsp:rw –privileged advrisc/u22.04-amxxlbv1 /bin/bash</div>
== Build Steps ==

The following example shows how to download the Advantech Yocto BSP from Azure.

For this example, a directory called yocto_bsp is created for the project.
<div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ git clone [https://AIM-Linux@dev.azure.com/AIM-Linux/RISC-TI-Linux/_git/adv-ti-yocto-bsp https://AIM-Linux@dev.azure.com/AIM-Linux/RISC-TI-Linux/_git/adv-ti-yocto-bsp] -b processor-sdk-am335x-11.02.05.02 tisdk-adv</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ cd tisdk-adv</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-scarthgap-11.02.05.02-config.txt</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ cd build</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ . conf/setenv</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ MACHINE=am335xepcr3220a1 bitbake -k tisdk-default-image</div>
Your tisdk-default-image tar.xz image will be generated in the deploy-ti directory. Use Processor SDK Linux Create SD Card to flash this image on the SD-Card.  

== Build Options ==

=== Images ===

In addition to individual components packages, the following table provides a list of build targets supported. These are the <target> used in the command:
<div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ MACHINE=<machine> bitbake <target></div>
The "Build Output" is given relative to the deploy-ti directory.

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="width: 121px;" |
'''Target'''

| style="width: 369px;" |
'''Build Output'''

| style="width: 122px;" |
'''Description'''

|-
| style="width: 121px;" |
tisdk-default-image

| style="width: 369px;" |
images/<machine>/tisdk-default-image-<machine>.tar.xz

| style="width: 122px;" |
Target Filesystem

|-
| style="width: 121px;" |
tisdk-base-image

| style="width: 369px;" |
images/<machine>/tisdk-base-image-<machine>.tar.xz

| style="width: 122px;" |
Minimal Target Filesytem

|-
| style="width: 121px;" | tisdk-thinlinux-image
| style="width: 369px;" | images/<machine>/tisdk-thinlinux-image-<machine>.tar.xz
| style="width: 122px;" | Minimal Target Filesytem with docker enabled
|-
| style="width: 121px;" | meta-toolchain-arago-tisdk
| style="width: 369px;" | sdk/arago-<arago-version>-<architecture>.sh
| style="width: 122px;" | Devkit
|-
| style="width: 121px;" |
u-boot-ti-staging

| style="width: 369px;" |
images/<machine>/u-boot-<machine>.img

images/<machine>/MLO-<machine>

| style="width: 122px;" |
u-boot

|-
| style="width: 121px;" |
linux-ti-staging

| style="width: 369px;" |
images/<machine>/zImage-<machine>.bin

images/<machine>/zImage-<machine>.dtb

| style="width: 122px;" |
kernel

|}

 

{| border="1" cellpadding="0" cellspacing="0"
|-
|
'''MACHINE'''

| style="width: 443px;" |
'''Supported Product'''

|-
| am335xepcr3220a1
| style="width: 443px;" |
EPC-R3220A1

|}

== Create SD Card using balenaEtcher ==

Download the default bootable SD card image (WIC file) available on the release page as

tisdk-default-image-<machine>-<version>.rootfs.wic.xz

Download and install the balenaEtcher tool :

Balena Etcher is an open-source utility that can be installed on both Linux and Windows. Download the tool from[https://www.balena.io/etcher/ this link]and install it.

Flash the WIC image to the SD card :

Insert a micro SD card into the USB SD card reader and start Etcher.Choose the default WIC image to be flashed, choose the USB SD card reader as the target, and then click “Flash”. Etcher will decompress the image and write it to the SD card, as shown below

[[File:Balena.png|RTENOTITLE]]

'''Danger'''

This operation '''WILL ERASE''' the contents of your SD card.

== Boot from Onboard Flash ==

If you have already get a Linux system SD card and the last step of make process selected "y", you can refer to the following steps to burn the system to the onboard flash.

Please insert the Linux system SD card to EPC-R3220, and then power up. It boot from the SD card.
<div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ umount /dev/mmcblk1p* 2 > /dev/null || true</div> <div style="background: rgb(238, 238, 238); padding: 5px 10px; border: 1px solid rgb(204, 204, 204);">$ sudo bmaptool copy /root/tisdk-thinlinux-image-am335xepcr3220a1.rootfs-*.wic /dev/mmcblk1</div>

EPC-R3220 Yocto5.0 User Guide

2026-02-27T02:11:57Z

Xingxing.li:

= '''產品介紹''' =

== '''資源特性(Features)''' ==

*TI Sitara™ AM3352 Cortex®-A8 800MHz processor
*1GB of DDR3-800 and 8 GB of eMMC NAND Flash onboard
*2 Gigabit Ethernet ports
*2 RS232/485, 1 USB OTG, 6 GPIO
*WiFi/BT/LTE solution ready
*Yocto Linux support
*-20 ~ 70 °C operating temperature/ 12~24V DC power supply
*Equipped with hardware watchdog timer for system protection

== '''產品官網連結(Product information Link)''' ==

[https://www.advantech.com/zh-tw/products/a6f86282-b6ed-4f54-b5b1-cddf3e3ab3cc/epc-r3220/mod_ba26afd3-1706-4172-a93c-3f2c7dc9cc41 '''EPC-R3220''']

= '''接口布局和尺寸(Layout and Sizes)''' =

=== '''EPC-R3220  接口布局圖 Board Dimension Layout ''' ===

'''Front I/O '''

[[File:EPC-3220 FrontIO2021-10-04 103643.jpg|RTENOTITLE]]

'''Left-Side'''

[[File:EPC-R3220 LeftIO2021-10-04 103920.jpg|RTENOTITLE]]

'''Right-Side'''

[[File:EPC-R3220Right2021-10-04 104111.jpg|RTENOTITLE]]

 

[[File:EPC-R3220 connector Inside2021-10-04 131212.jpg|RTENOTITLE]]

 

=== '''接口引脚定義 (Pin definitions)''' ===

*[[串口(Debug_port_、RS-232、RS-485_、GPIO)|串口(Debug port 、RS-232、RS-485 、GPIO)]]
*[[LAN接口|LAN接口(LAN)]]
*USB接口(USB1-2、USB-4-5、USB Type C、USB OTG)
*[[电源(DC-IN)|电源(DC-IN)]]
*MINI_PCIE接口、I2C_接口
*[[SW1(SD启动or_EMMC启动）|SW1(SD启动 or EMMC启动）]]

=== '''机械尺寸  ('''Mechanical Characteristics) ===

'''EPC-R3220  '''

[[File:EPC-R3220 ME2021-10-04 104559.jpg|RTENOTITLE]]

----

= '''快速入门 (Quick Start)''' =

=== '''系统下载 (OS Download)''' ===

Note：  LIV= Yocto Linux Image
<div style="text-align:start; -webkit-text-stroke-width:0px"><div>              '''LIV38=Yocto-5.0'''</div>
{| class="wikitable" style="font-size: 14px; margin: 1em 0px; background-color: rgb(249, 249, 249); border: 1px solid rgb(170, 170, 170); border-collapse: collapse; color: rgb(0, 0, 0); width: 858px;"
|-
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:80px" | '''Product'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:111px" | '''CPU'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:111px" | '''Image Version'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:103px" | '''Release Date'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:64px" | '''Release'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:102px" | '''Release notes'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:115px" | '''Image Download'''
| style="border: 1px solid rgb(170, 170, 170); background: rgb(240, 240, 240); width: 143px;" | '''Test Report'''
|-
| style="border:1px solid #aaaaaa; width:50px" | EPC-R3220
| style="border:1px solid #aaaaaa; width:50px" | AM335x
| style="border:1px solid #aaaaaa; width:50px" | LIV38005
| style="border:1px solid #aaaaaa; width:50px" | 2026-01-19
| style="border:1px solid #aaaaaa; width:35px" | Beta
| style="border:1px solid #aaaaaa; width:100px" | [https://ess-wiki.advantech.com.tw/view/EPC-R3220_Yocto5.0_Release_notes Release note]
| style="border:1px solid #aaaaaa; width:100px" |
[https://pan.baidu.com/s/1QuJiMlIbkCs1Fj-03vuNuQ?pwd=a887 Baidu]

[https://www.dropbox.com/scl/fo/fm2vgpyln9dnyfu5m2b05/ABm1t1wiE2RrfQLBEH35xRY?rlkey=360akr1sc40h59f7tl3dxmt59&st=ppywisb3&dl=0 Dropbox]

| style="border: 1px solid rgb(170, 170, 170); width: 143px;" | [https://ess-wiki.advantech.com.tw/wiki/images/5/5f/EPC-R3220_Yocto5.0_2026-01_test_report.xlsx Test Report]
|}
<ul style="/* insecure input */">
<li>Alpha:  Basic I/O function bring up by RD;</li>
</ul>
<ul style="/* insecure input */">
<li>Beta:  Basic I/O function、performance and middleware verified by RD. Peripherals integrated;</li>
</ul>
<ul style="/* insecure input */">
<li>GA:  Beta version by QE verification;</li>
</ul>
<ul style="/* insecure input */">
<li>RTM:  Beta version by SI/Power/QE verification and pre-loaded;</li>
</ul>
</div>
 

=== '''Linux 燒錄方法 (Linux Flash eMMC Method)''' ===

'''使用Flash tool 燒錄鏡像到eMMC (Flash image into eMMC by Flash Tools)  [Use Ubuntu 18.04 to create SD card (Test the SD image can boot into Linux without problem that created on Ubuntu18.04 or 20.04)]'''

解壓縮檔案(Unzip the files) 

[[File:EPC-R3220unzip12021-10-04 143828.jpg|RTENOTITLE]]

'''mkdir ti-sdk-XXX(XXX represents numbers, e.g. ti-sdk-001)'''

Command : phill@riscserver-Default-string:/home/RISC_BSP_Home/EPC-R3220/R3220A1AIM20LIV20012_am335x_2021-07-29$ mkdir ti-sdk-001

'''Unzip file to ti-sdk-001'''

Command : tar -xJf processor-sdk-linux-image-am335xepcr3220a1-20210729031957.tar.xz -C ti-sdk-001

[[File:EPC-R3220Unzip ti0012021-10-04 151725.jpg|RTENOTITLE]]

Step0: 檢查SD卡在Linux 環境的代號 (check SD card symbol in Linux system) 

[[File:EPC-R3220 checkSD2021-10-04 152134.jpg|RTENOTITLE]]

[[File:EPC-R3220 checkSD12021-10-04 152201.jpg|RTENOTITLE]]

Step1: 創造一張可開機的SD 卡 (Create a bootable SD card)

 $ cd ti-sdk-XXX/bin

 [[File:EPC-R3220 bin2021-10-04 160222.jpg|RTENOTITLE]]

$ sudo ./create-sdcard.sh

[[File:EPC-R3220 createSD2021-10-04 160506.jpg|RTENOTITLE]]

Select SD card:

[[File:EPC-R3220 selectsd2021-10-04 161451.jpg|RTENOTITLE]]

Select number of partitions:

[[File:EPC-R3220 selectSD12021-10-04 161702.jpg|RTENOTITLE]]

[[File:EPC-R3220 selectpartition2021-10-04 161850.jpg|RTENOTITLE]]

[[File:EPC-R3220 continue2021-10-04 162044.jpg|RTENOTITLE]]

Select Pre-built System image:

[[File:EPC-R3220 prebuildsystemimage2021-10-04 162244.jpg|RTENOTITLE]]

Select tisdk-rootfs-image-XXX.tar.xz(XXX represents machine name, e.g. am335xepcr3220a1):

[[File:EPC-R3220 selecttidisk image2021-10-04 162518.jpg|RTENOTITLE]]

[[File:EPC-R3220 selecttidisk image result2021-10-04 162518.jpg|RTENOTITLE]]

If you need to transfer whole system to on-board flash, please press y followed by Enter.

[[File:EPC-R3220 inand2021-10-04 162836.jpg|RTENOTITLE]]

[[File:EPC-R3220 inand result2021-10-04 162836.jpg|RTENOTITLE]]

 

Step2: 將可開機的SD 卡插入底板SD卡卡槽(Plug the SD card into Carrier board 's SD card slot)

 [[File:EPC-R3220 SD slotpulgin2021-10-07 134342.jpg|RTENOTITLE]]

Step3: 確認開機選擇指撥開關(Check the SW1 switch)

            SPL開機模式(SPL boot mode: boot from SD/MMC, SPI...) 

            1--off  2---off

            eMMC開機模式(eMMC(SPI) boot mode): The R3220 can only support SPI and SD boot in HW design. So it needs to flash the MLO file to the SPI flash, and it can boot the SPI first and then boot the u-boot from the eMMC

            1--on  2--off

            Note: After change switch setting. Unplug and plug AC power for the change to take effect.

Step3:打開電源和終端機 (Turn on the Power & Terminal)

     [[File:EPC-R3220 turnonpower2021-10-07 1521111.jpg|RTENOTITLE]]

      [[File:EPC-R3220 Login Yocto2021-10-07 1520041111.jpg|RTENOTITLE]]

   

 

Step4: 利用mk-eMMC-boot.sh 安裝eMMC 鏡像(Flash image to eMMC Flash by mk-eMMC-boot.sh ) 

[[File:EPC-R3220 mk-eMMC-boot.sh2021-10-07 160353.jpg|RTENOTITLE]]

[[File:EPC-R3220 mk-eMMC-boot.sh 12021-10-07 160438.jpg|RTENOTITLE]]

[[File:EPC-R3220 mk-eMMC-boot.sh 22021-10-07 160353.jpg|RTENOTITLE]]

[[File:EPC-R3220 mk-eMMC-boot.sh 3 22021-10-07 160353.jpg|RTENOTITLE]]

[[File:EPC-R3220 mk-eMMC-boot.sh 4 12021-10-07 160438.jpg|RTENOTITLE]]

[[File:EPC-R3220 mk-eMMC-boot.sh 5 12021-10-07 160438.jpg|RTENOTITLE]]

  [[File:EPC-R3220 mk-eMMC-boot.sh 6 12021-10-07 160438.jpg|RTENOTITLE]]

 

        

     

=== '''Debug 串口調試 (Debug port Setting)''' ===

以 Tera Term  为例介绍如何使用串口调试功能
<pre> Baud Rate波特率：115200
Data 数据位：8
Parity 奇偶校验：无
  Stop 停止位：1
Flow Control流控：无</pre>

: 

Tera Term Tool 

[[File:TeraTerm 2021-09-10 140930n.jpg|RTENOTITLE]]

[[File:TeraTerm12021-09-10 141114n.jpg|RTENOTITLE]]

Check the Sriel port in Device Manager (查看PC端的串口号)：

if you can not identify the Serial device , please check your serial driver. 

[[File:COMportinx862021-09-10 141610.jpg|RTENOTITLE]]

Debug port connection (串口連接) 

[[File:EPC-R3220 turnonpower2021-10-07 152136.jpg|RTENOTITLE]]

 

Log into Terminal  Tool (进入串口调试终端)：

[[File:EPC-R3220 Login Yocto2021-10-07 1520041111.jpg|RTENOTITLE]]

----

= '''Linux系统的基本使用(Linux System Basic Operating Method)''' =

=== '''乙太網路使用方法(Ethernent Testing Method)''' ===

'''Command : ifconfig '''

[[File:EPC-R3220 ethnet ifconfig 2022-01-07 162824.jpg|RTENOTITLE]]

'''Command: Ping - I eth1 8.8.8.8  or Ping - I eth0 8.8.8.8  '''

[[File:EPC-R3220 ethernet ping 2022-01-07 163028.jpg|RTENOTITLE]]

=== '''WiFi使用方法(WIFI Testing Method)''' ===

'''M.2 Mrvl. WIFI/BT Test EPC-R3220 supports MarverllSD8897 wifi/bt modules throught M.2.'''
<div>[[File:EPC-R3220 wifi m.2 2021-10-07 164711.jpg|RTENOTITLE]]</div>
=== '''4G使用方法(4G Testing Method)''' ===
<div>Script : [[4G_ppp_EPC-R3220.7z|4G_ppp.sh ]]</div> <div>            [[4G_rndis_EPC-R3220.7z|4G_rndis.sh ]]</div> <div>SOP: [[EIOT-_EPC-R3220_EWM-C117_auto_run_script_.docx|Test EWM-C117 with EPC-R3220]]</div>
=== '''GPIO使用方法(GPIO Operating Method)''' ===

[[File:EPC-R3220 GPIO Test2021-10-07 165814.jpg|RTENOTITLE]]

[[File:EPC-R3220 GPIO Test 1 2021-10-07 170203.jpg|RTENOTITLE]]

 
<div> </div>
=== '''串口使用方法(Serial Port Operating Method)''' ===

RS-232 Test 

[[File:EPC-R3220 RS-232 Test2021-10-07 170819.jpg|RTENOTITLE]]

=== '''蓝牙使用方法(BlueTooth Operating Method)''' ===
<pre>Command :

$ hciconfig hci0 up
$ bluetoothctl
$ discoverable on
$ pairable on
$ scan on
[NEW] FC:18:3C:8D:75:F4 myphone
$ scan off
$ pair FC:18:3C:8D:75:F4
$ connect FC:18:3C:8D:75:F4</pre>

[[File:BTTest2021-09-09 132449.jpg|RTENOTITLE]]

=== '''  遠程訪問及文件傳輸(Remote Access and File Transimmion)''' ===

'''              查看主板IP位址 ( Chech IP Address )：'''
<pre> Command : ifconfig</pre>

[[File:EPC-R3220 ifconfig ssh 2021-10-07 171106.jpg|RTENOTITLE]]

==== Windows下SSH访问及文件传输 ====

SSH Remote Log into Device 

*SSH远程登录,以putty选择putty.exe(或者使用Xshell、SecureCRT等类似软件)
*需要设置远程设备的IP、通讯端口(默认22)、通讯方式，登录后验证用户名密码

 

[[File:SSHsettingdetail.png|RTENOTITLE]]

[[File:EPC-R3220 ifconfig ssh 1 2021-10-07 171607.jpg|RTENOTITLE]]

 

[[File:Sshsetting12021-09-10 143743n.jpg|RTENOTITLE]]

Account is “root” , no password.

[[File:EPC-R3220 ifconfig ssh 2 2021-10-07 171807.jpg|RTENOTITLE]]

 

=== '''RS-485 測試方式 (RS-485 testing method) ''' ===

'''Test tool script : '''

'''Uart change mode'''

百度網盤(Baidu Disk): '''链接：[https://pan.baidu.com/s/1HGJoW0jqp_GGK5VFvXAieg &nbsp https://pan.baidu.com/s/1HGJoW0jqp_GGK5VFvXAieg &nbsp]; 提取码：luug '''

'''[[File:EPC-R3220 RS485-1 2021-11-17 094556.jpg|RTENOTITLE]]'''

[[File:EPC-R3220 485-2 2021-11-17 094837.jpg|RTENOTITLE]]

[[File:EPC-R3220 485-3 2021-11-17 094945.jpg|RTENOTITLE]]

 

 

[[File:EPC-R3220 485-4 2021-11-17 095024.jpg|RTENOTITLE]]

[[File:EPC-R3220 485-5 2021-11-17 095024.jpg|RTENOTITLE]]

= '''通用方法(General Method)''' =

===   '''  ''''''  查看CPU频率(Check CPU Frequency)''' ===
<pre> root@am335xepcr3220a1:/# cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
>> 600000
root@am335xepcr3220a1:/# cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq
>> 800000</pre>

=== '''      查看内存容量(Check Memory Capacity)''' ===
<pre>root@am335xepcr3220a1:~# busybox free -m[  143.716190] NET: Registered protocol family 15

             total       used       free     shared    buffers     cached
Mem:          1002        152        849          9         23         88
-/+ buffers/cache:         40        961
Swap:            0          0          0
</pre>

=== '''      查看存储容量(Check Storage Capacity)''' ===
<pre style="margin-left: 40px;">root@am335xepcr3220a1:~# busybox df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 6.1G      2.2G      3.5G  39% /
devtmpfs                476.7M      4.0K    476.7M   0% /dev
tmpfs                   501.2M         0    501.2M   0% /dev/shm
tmpfs                   501.2M      9.6M    491.6M   2% /run
tmpfs                   501.2M         0    501.2M   0% /sys/fs/cgroup
tmpfs                   501.2M         0    501.2M   0% /tmp
tmpfs                    16.0M         0     16.0M   0% /media/ram
tmpfs                    50.0M    128.0K     49.9M   0% /var/volatile
/dev/mmcblk1p3           58.0M     31.1M     23.7M  57% /run/media/mmcblk1p3
/dev/mmcblk1p6          739.9M    796.0K    700.7M   0% /cache
/dev/mmcblk1p5            2.9M     34.0K      2.6M   1% /run/media/mmcblk1p5
/dev/mmcblk1p1           68.9M    472.5K     68.4M   1% /run/media/mmcblk1p1
tmpfs                   100.2M         0    100.2M   0% /run/user/0</pre>

=== '''      網路Ping測試(Ping Network Testing)''' ===
<pre> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=2.10 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=2.10 ms</pre>

=== '''      設置RTC (RTC Setting) ''' ===
<pre>root@am335xepcr3220a1:~# date 101212102021 && hwclock -w && date
Tue Oct 12 12:10:00 UTC 2021
Tue Oct 12 05:52:57 UTC 2021
root@am335xepcr3220a1:~# date
Tue Oct 12 05:52:58 UTC 2021
root@am335xepcr3220a1:~#</pre>

'''         '''

= '''Linux BSP編譯方法(Yocto BSP Compile Method)''' =

=== [[EPC-R3220_Yocto_5.0_BSP_User_Guide|'''EPC-R3220_Yocto 5.0 BSP User Guide''']] ===

 

{| border="0" cellpadding="10" cellspacing="0" style="width:100%;"
|-
| <iframe height="230" key="advonline" level="campaign" path="en/aim-linux_community/" width="100%"></iframe>
|}

EPC-R3220 Yocto5.0 Release notes

2026-02-27T01:47:39Z

Xingxing.li: Created page with " '''Release Note ''' {| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%" |- | '''SDK version ''' | 11.02.05.02   |- | '''Uboot versi..."

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%"
|-
| '''SDK version '''
|
11.02.05.02

 

|-
| '''Uboot version'''
| 2025.01
|-
| '''Kernel version '''
| 6.12.49
|-
| '''Python'''
| 3.12.12
|-
| '''G Streamer '''
| 1.22.12
|-
| '''Docker '''
| 25.0.3
|}

 

'''Change List'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width=""
|-
| '''Item'''
|
'''Description'''

|-
| '''1'''
| First Beta release
|}

 

'''Accessories Support List'''

{| border="1" cellpadding="1" cellspacing="1"
|-
! scope="col" | Item
! scope="col" | Advantech PN
! scope="col" | Chip/Vendor
! scope="col" | MPN
! scope="col" | Factor
! scope="col" | Host Interface
|-
| 4G
| 968DD00443
| Quectel
| EC20CEFRG-MINIPCIE
| Mini-PCIE
| USB2.0
|}

EPC-R3220 Yocto5.0 Release Note

2026-02-27T01:44:41Z

Xingxing.li: Created page with " <span style="f..."

Note：  LIV= Yocto Linux Image
<div style="text-align:start; -webkit-text-stroke-width:0px"><div>              '''LIV38=Yocto-5.0'''</div>
{| class="wikitable" style="font-size:14px; margin:1em 0px; background-color:#f9f9f9; border:1px solid #aaaaaa; border-collapse:collapse; color:#000000; width:800px"
|-
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:80px" | '''Product'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:111px" | '''CPU'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:111px" | '''Image Version'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:103px" | '''Release Date'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:64px" | '''Release'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:102px" | '''Release notes'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:115px" | '''Image Download'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:87px" | '''Test Report'''
|-
| style="border:1px solid #aaaaaa; width:50px" | EPC-R3220
| style="border:1px solid #aaaaaa; width:50px" | AM335x
| style="border:1px solid #aaaaaa; width:50px" | LIV38005
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:50px; background-color:#f9f9f9" | 2026-01-19
| style="border:1px solid #aaaaaa; width:35px" | Beta
| style="border:1px solid #aaaaaa; width:100px" | [[EPC-R3220_Yocto5.0_Release_notes|Release note]]
| style="border:1px solid #aaaaaa; width:100px" |
[https://pan.baidu.com/s/1QuJiMlIbkCs1Fj-03vuNuQ?pwd=a887 Baidu]

[https://www.dropbox.com/scl/fo/fm2vgpyln9dnyfu5m2b05/ABm1t1wiE2RrfQLBEH35xRY?rlkey=360akr1sc40h59f7tl3dxmt59&st=ppywisb3&dl=0 Dropbox]

| style="border:1px solid #aaaaaa; width:60px" | [https://ess-wiki.advantech.com.tw/wiki/images/5/5f/EPC-R3220_Yocto5.0_2026-01_test_report.xlsx Test Report]
|}
<ul style="/* insecure input */">
<li>Alpha:  Basic I/O function bring up by RD;</li>
</ul>
<ul style="/* insecure input */">
<li>Beta:  Basic I/O function、performance and middleware verified by RD. Peripherals integrated;</li>
</ul>
<ul style="/* insecure input */">
<li>GA:  Beta version by QE verification;</li>
</ul>
<ul style="/* insecure input */">
<li>RTM:  Beta version by SI/Power/QE verification and pre-loaded;</li>
</ul>
</div>

AIM-Linux/BSP/NXP/Linux Yocto OS Release note/AOM-5521/VH0009

2026-02-10T01:57:24Z

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%"
|-
| '''Uboot version '''
|
v2025.04_6.12.20_2.0.0

|-
| '''Kernel version '''
| 6.12.20_2.0.0
|}

'''Change Log'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" style="width: 301px;" width=""
|-
| '''Item'''
| style="width: 93px;" |
'''Change List'''

| style="width: 163px;" |
'''Description'''

|-
| '''1'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed OTG function
|-
| '''2'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed LVDS-Panel function
|-
| '''3'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed HDMI Hot plug
|-
| '''4'''
| style="width: 93px;" | Issue
| style="width: 163px;" | Fixed MIPI-DSI Panel function
|}

 

AIM-Linux/BSP/Qualcomm/mio5355a1 yocto4.0.22-le1.3 v1.1.0 kernel-6.6.52 qcs6490+qcs5430

2026-02-09T08:03:16Z

Darren.huang: Created page with " '''Release Note ''' {| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%" |- | '''UEFI version ''' | 6.0.260121.BOOT.MXF.1.0.c1-00254.3-KODIA..."

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%"
|-
| '''UEFI version '''
| 6.0.260121.BOOT.MXF.1.0.c1-00254.3-KODIAKLA-
|-
| '''Kernel version '''
| 6.6.52
|}

'''Change Log'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width=""
|-
| '''Item'''
|
'''Change List'''

|
'''Description'''

|-
| '''1'''
| New Feature
| Public BSP
|-
| '''2'''
| Known Issue 
|  
|}

AOM-3841 Debian12 user guide

2026-02-05T01:50:28Z

Xingxing.li:

== '''產品特性(Features)''' ==

*2.0 GHzRockchip RK3576 Arm Quad Cortex-A72 2.2GHz and Quad Cortex-A53  
*Onboard 4/8 GB LPDDR4 memory and eMMC / UFS
*Supports HDMI, DP and 1 x 4 lane MIPI-DSI
*Gen1, SDIO, 3 x MIPI-CSI, 3 x UART2 x GMAC, Type C, 1 x PCIe 2.1/SATA 3.1, 1 x PCIe 2.1/SATA 3.1/USB3.2 
*Supports Linux Debian12 and Android14

=== '''產品官網鏈接（Product official website link）''' ===

[https://www.advantech.com/en-us/products/69436ae1-5f45-4c24-bd86-ae44341adc07/aom-3841/mod_4dbe41cc-2909-4d20-978d-1161788dc0c9 AOM-3841 - Advantech]

== '''接口布局和尺寸（Layout and Sizes）''' ==

=== '''AOM-3841 Board Dimension Layout''' ===

 

=== '''AOM-3841 Mechanical Specifications''' ===

*Dimension：RTXe form factor size：（D X W）77 x 65 mm
*Height on Top：2mm
*Height on Bottonm：1.5mm

 

=== '''Electrocal Specifications''' ===

*Power Supply Voltage：DC-in 5V±5%
*Power Supply Current：

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| style="width: 93px;" | '''Model'''
| style="width: 166px;" | '''Maximum mode'''
| '''Kernel idle'''
| '''Sleep mode'''
|-
| style="width: 93px;" | AOM-3841
| style="width: 166px;" | 4.92W
| 0.76W
| 0.08W
|}

Test Conditions: 1. Test loading: - Maximum load mode: Running programs* - Idle mode: DUT power management off and no running any program 2. OS: Debian12 *Programs software: Burnin.sh (full loading for CPU+NPU+GPU+VPU)

=== '''Environmental Specifications''' ===

*Operating Temperature：0~70 °C / -40 ~ 85 °C
*Operating Humidity: 40°C @ 95% relative humidity, non-condensing
*Storage Temperature: -40 ~ 85 °C 
*Storage Humidity: 95% @ 60 °C 

== '''AOM-DB3500  Board Dimension Layout''' ==

=== '''Connector Locations''' ===

[[File:AOM-3841 AOM-DB3500 Connector.jpg|700x600px|AOM-3841 AOM-DB3500 Connector.jpg]][[File:AOM-3841 AOM-DB3500 Connector1.jpg|700x600px|AOM-3841 AOM-DB3500 Connector1.jpg]]

=== '''I/O Connector Locations''' ===

[[File:AOM-DB3500 IO Connector Locations.png|RTENOTITLE]]

[[File:AOM-DB3500 IO Connector Locations1.png|RTENOTITLE]]

=== '''Mechanical Diagram''' ===

For more details regarding our 2D/3D models, please visit the Advantech support service website at: [http://www.advantech.com http://www.advantech.com].

'''Board Mechanical Diagram - Front'''

[[File:AOM-DB3500 Mechanical Diagram.png|600x450px|AOM-DB3500 Mechanical Diagram.png]]

''' Board Mechanical Diagram – Side1'''

[[File:AOM-DB3500 Mechanical Diagram1.png|RTENOTITLE]]

''' Board Mechanical Diagram - Side2'''

[[File:AOM-DB3500 Mechanical Diagram2.png|RTENOTITLE]]

=== '''Assembly Diagram''' ===

These figures demonstrate the order of assembly needed when attaching the thermal module and COM module to the carrier board.

[[File:AOM-DB3500 Assembly Diagram.png|RTENOTITLE]]

== '''AOM-3841 on AOM-DB3500 Connector，Jumper，Switch Settings''' ==

=== '''Connector List''' ===

{| border="1" cellpadding="1" cellspacing="1" style="width: 825px;"
|-
| style="width: 88px;" | '''Lable'''
| style="width: 289px;" | '''Function'''
| style="width: 124px;" | '''Lable'''
| style="width: 297px;" | '''Function'''
|-
| style="width: 88px;" | DC IN
| style="width: 289px;" | 4Pin Terminal Connector for DC IN（Input）
| style="width: 124px;" | CN3
| style="width: 297px;" | GPIO Pin Header
|-
| style="width: 88px;" | ROM-AB1
| style="width: 289px;" | RTXe connector
| style="width: 124px;" | HDMI RX
| style="width: 297px;" | HDMI RX Connector（Input）
|-
| style="width: 88px;" | ROM-CD1
| style="width: 289px;" | RTXe connector
| style="width: 124px;" | CAN0_1
| style="width: 297px;" | CAN Bus Connector
|-
| style="width: 88px;" | PWRBTN PH
| style="width: 289px;" | Power Button Pin Header
| style="width: 124px;" | HDM A TYPE
| style="width: 297px;" | HDMI Connector
|-
| style="width: 88px;" | RSTBTN_PH
| style="width: 289px;" | Reset Button Pin Header
| style="width: 124px;" | TYPEC_DP
| style="width: 297px;" | DP&USB2.0+USB 3.0 Typec Connector
|-
| style="width: 88px;" | DEBUG
| style="width: 289px;" | Debug Port
| style="width: 124px;" | SD
| style="width: 297px;" | SD Card Connector
|-
| style="width: 88px;" | MIC1
| style="width: 289px;" | MIC-IN Connector（Input）
| style="width: 124px;" | MICRO USB
| style="width: 297px;" | Micro USB Connector（USB2.0 only）
|-
| style="width: 88px;" | LOUT1
| style="width: 289px;" | Headphones Connector（Output）
| style="width: 124px;" | USB1/2
| style="width: 297px;" | TypeA USB Connector（2xUSB2.0+USB3.0）
|-
| style="width: 88px;" | MIC2
| style="width: 289px;" | MIC-IN Connector（Input）
| style="width: 124px;" | SPI_CN2
| style="width: 297px;" | SPI0 Pin Header
|-
| style="width: 88px;" | LOUT2
| style="width: 289px;" | Headphones Connector（Output）
| style="width: 124px;" | SPI_CN1
| style="width: 297px;" | SPI1 Pin Header
|-
| style="width: 88px;" | PCIEA-X4
| style="width: 289px;" | PCIe x4 Connector
| style="width: 124px;" | GMAC0
| style="width: 297px;" | GMAC0 Connector
|-
| style="width: 88px;" | EDP 
| style="width: 289px;" | EDP Connector
| style="width: 124px;" | GMAC1
| style="width: 297px;" | GMAC1 Connector
|-
| style="width: 88px;" | EDP BL
| style="width: 289px;" | EDP Backlight Connector
| style="width: 124px;" | ERP DEBUG
| style="width: 297px;" | EPR MCU FW Update Connector
|-
| style="width: 88px;" | I2S0
| style="width: 289px;" | I2S0 Connector
| style="width: 124px;" | RTC BAT
| style="width: 297px;" | RTC Coin Battery Connector
|-
| style="width: 88px;" | I2S1
| style="width: 289px;" | I2S1 Connector
| style="width: 124px;" | CN1
| style="width: 297px;" | Watchdog Connector
|-
| style="width: 88px;" | SIM
| style="width: 289px;" | SIM card Connector
| style="width: 124px;" | M.2_B
| style="width: 297px;" | M.2 Key-B Connector
|-
| style="width: 88px;" | CN2
| style="width: 289px;" | I2C Connector for I2C0
| style="width: 124px;" | M.2_E1
| style="width: 297px;" | M.2 Key-E Connector
|-
| style="width: 88px;" | CM1_2
| style="width: 289px;" | COM Port Port1,2 Con-nector
| style="width: 124px;" | M.2_E2
| style="width: 297px;" | M.2 Key-B Connector（for SDIO）
|-
| style="width: 88px;" | CN4
| style="width: 289px;" | I2C Connector for I2C1
| style="width: 124px;" | CN6
| style="width: 297px;" | Resvered Signal Connector
|-
| style="width: 88px;" | CSI0_FPC
| style="width: 289px;" | MIPI FPC Connector for CSI0
| style="width: 124px;" | CN5
| style="width: 297px;" | SDIO Connector（for SD1）
|-
| style="width: 88px;" | CSI1_FPC
| style="width: 289px;" | MIPI FPC Connector for CSI1
| style="width: 124px;" | CN7
| style="width: 297px;" | Supply +5V Connector
|-
| style="width: 88px;" | CSI2_FPC
| style="width: 289px;" | MIPI FPC Connector for CSI2
| style="width: 124px;" |  
| style="width: 297px;" |  
|}

=== '''Jumper Locations''' ===

[[File:AOM-DB3500 Jumper Locations.png|RTENOTITLE]]

=== '''Switch Locations''' ===

[[File:AOM-DB3500 Switch Locations.png|RTENOTITLE]]

=== '''Button Locations''' ===

[[File:AOM-DB3500 Button Locations.png|600x450px|AOM-DB3500 Button Locations.png]]

{| border="1" cellpadding="1" cellspacing="1" style="width: 916px;"
|-
| style="width: 63px;" | '''Lable'''
| style="width: 379px;" | '''Function'''
| style="width: 46px;" | '''Lable'''
| style="width: 403px;" | '''Functiion'''
|-
| style="width: 63px;" | PWR BTN
| style="width: 379px;" | Power Button
| style="width: 46px;" | J8
| style="width: 403px;" | M2_E1 Power Select
|-
| style="width: 63px;" | RST BTN
| style="width: 379px;" | Reset Button
| style="width: 46px;" | J10
| style="width: 403px;" | M.2_B Power Selsct
|-
| style="width: 63px;" | SW1
| style="width: 379px;" | BOOT SELECT Switch
| style="width: 46px;" | J9
| style="width: 403px;" | UART1 to M2_E2 or M2_E1 Connector Select
|-
| style="width: 63px;" | SW2
| style="width: 379px;" | USB0 PWE_EN Select Switch
| style="width: 46px;" | J2
| style="width: 403px;" | AT/ATX Select Header
|-
| style="width: 63px;" | SW3
| style="width: 379px;" | USB0 OC# Select Switch
| style="width: 46px;" | J37
| style="width: 403px;" | GPIO4_Z_G Selection
|-
| style="width: 63px;" | J12
| style="width: 379px;" | EDP0/LVDS0/DSI Hot-Plug   Detect Selection Header
| style="width: 46px;" | J26
| style="width: 403px;" | GPIO0_Z_G Selection
|-
| style="width: 63px;" | J15
| style="width: 379px;" | EDP VDD Power Select
| style="width: 46px;" | J28
| style="width: 403px;" | GPIO0 Selection
|-
| style="width: 63px;" | J16
| style="width: 379px;" | EDP Backlight Power Select
| style="width: 46px;" | J31
| style="width: 403px;" | GPIO4 Selection
|-
| style="width: 63px;" | J17
| style="width: 379px;" | Header For SD1 Selection
| style="width: 46px;" | J20
| style="width: 403px;" | GPIO7 Selection
|-
| style="width: 63px;" | J18
| style="width: 379px;" | Header For SD1_CD# Selecttion
| style="width: 46px;" | J24
| style="width: 403px;" | GPIO7A Selection
|-
| style="width: 63px;" | J30
| style="width: 379px;" | Header For  EDP0_BKLT_EN and EDP0_BKLT_PWM
| style="width: 46px;" | J25
| style="width: 403px;" | GPIO1 Selection
|-
| style="width: 63px;" | J22
| style="width: 379px;" | CAN0 BUS Terminal Resistor
| style="width: 46px;" | J27
| style="width: 403px;" | GPIO1_Z_G Selection
|-
| style="width: 63px;" | J23
| style="width: 379px;" | CAN1 BUS Terminal Resistor
| style="width: 46px;" | J29
| style="width: 403px;" | GPIO6 Selection
|-
| style="width: 63px;" | J14
| style="width: 379px;" | Header For WDT_OUT#  Link Selection
| style="width: 46px;" | J32
| style="width: 403px;" | GPIO5 Selection
|-
| style="width: 63px;" | J13
| style="width: 379px;" | Header For WDT_OUT# Selection
| style="width: 46px;" | J1
| style="width: 403px;" | SD0_WP Select Header
|-
| style="width: 63px;" | J11
| style="width: 379px;" | TYPEC_OTG_ID Selection Header
| style="width: 46px;" | J5
| style="width: 403px;" | SPI1_CS#  Select Header
|-
| style="width: 63px;" | J6
| style="width: 379px;" | SPI0_CS#  Select Header
| style="width: 46px;" | J7
| style="width: 403px;" | USB3 2.0 OTG and Host Select  Header
|-
| style="width: 63px;" | J35
| style="width: 379px;" | U7 mode Select
| style="width: 46px;" | J36
| style="width: 403px;" | U58 mode Select
|}

=== '''LED Function List''' ===

'''[[File:AOM-DB3500 LED Locations.png|600x450px|AOM-DB3500 LED Locations.png]]'''

{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
| '''Location'''
| '''Function'''
|-
| +V12 LED
| Carrier Board +V12 Indicate
|-
| +V12 SB LED
| Carrier Board +V12_SB Indicate
|-
| +V3.3 LED
| Carrier Board +V3.3 Indicate
|-
| +V3.3 SB LED
| Carrier Board +V3.3_SB Indicate
|-
| +V5 LED
| Carrier Board +V5 Indicate
|-
| +V5 SB LED
| Carrier Board +V5_SB Indicate
|-
| MOD_PWR_LED
| Module Power Indicate
|-
| LED1
| M2_E1-Key LED1 Indicate
|-
| LED2
| M2_E1-Key LED2 Indicate
|-
| LED3
| M2_B-Key LED3 Indicate
|-
| LED4
| M2_E2-Key LED4 Indicate
|-
| LED5
| M2_E2-Key LED5 Indicate
|}

== '''快速入门（Quick Start）''' ==

=== '''系统下载（OS Download）''' ===

'''Note：LIV=Yocto Linux , UIV=Ubuntu，DIV=Debain，AIV=Android '''

'''            LBV=BSP，LIV=Image'''

{| border="2"
|-
| '''Product'''
| '''Image Version'''
| '''Release Date'''
| '''Release Version'''
| '''Release notes'''
| '''Image Download'''
| '''BSP Download Tag'''
| '''SDK'''
| '''Comment'''
| '''Test Report'''
|-
| colspan="1" | AOM-3841
| DIV110025
| 2025/09/24
| RTM
| [https://ess-wiki.advantech.com.tw/view/AOM-3841_Debian12_Release_note Release_note]
|
[https://pan.baidu.com/s/1j-gDKWcBHmWHzeN8RDH8Aw?pwd=a887 Baidu] Password：a887 [https://www.dropbox.com/scl/fo/bnlhwsuyjeayv7s76v897/AAi7ZkvUOI9yEBCFO_x3sDc?rlkey=8oxwx4pe8gwnzzkw23t1oa1us&st=ceghyvpy&dl=0 Dropbox]

| RK3576_RISC_DIV110025.xml
| colspan="1" | Ask PM for Help
|  
| [http://ess-wiki.advantech.com.tw/wiki/images/4/42/AOM3841A1AIM38DIV110025_2025-09-24_test_report.xlsx Test Report]
|}

*Alpha:  Basic I/O function bring up by RD;

*Beta:  Basic I/O function、performance and middleware verified by RD. Peripherals integrated;

*GA:  Beta version by QE verification;

*RTM:  Beta version by SI/Power/QE verification and pre-loaded;

=== '''Debian 烧录方法（Debian flash eMMC Method）''' ===

1、[[AOM-3841_on_AOM-DB3500_Usering_RKTool.|AOM-3841 on AOM-DB3500 Usering_RKTool.]]

2、[[AOM-3841_on_AOM-DB3500_Usering_bootup_sd_disk_made_by_SDDiskTool.|AOM-3841 on AOM-DB3500 Usering bootup_sd_disk made_by SDDiskTool.]]

== '''Linux 基本使用方式（Basic usage of Linux）''' ==

[[AOM-3841_（Develop_Board_AOM-DB3500）Support_List_Desocroption|AOM-3841 （Develop Board AOM-DB3500）Support List Desocroption]]

[[AOM-3841_DC_IN|DC_IN]]

[[AOM-3841_UART_RS232（DEBUG、COM1、COM2、M.2_E1）|UART_RS232（DEBUG、COM1、COM2、M.2 E1）]]

[[AOM-3841_Button（RST、PWR）|Button（RST、PWR）]]

[[AOM-3841_AUDIO_MIC1/OUT1_&_MIC2/OUT2|AUDIO_MIC1/OUT1 & MIC2/OUT2]]

[[AOM-3841_Display（HDMI、DP、EDP）|Display（HDMI、DP、EDP）]]

[[AOM-3841_M.2_B_Key——5G（PCIE型）|M.2_B Key——5G（PCIE型）]]

[[AOM-3841_M2_E1_Key——WIFI/BT/SATA|M2_E1 Key——WIFI/BT/SATA]]

[[AOM-3841_SPI_CN1&SPI)CN2&CN2_I2C——I2C/SPI|SPI_CN1/SPI_CN2 & CN2_I2C/CN4_I2C——I2C/SPI]]

[[AOM-3841_GMAC0/1|GMAC0/1]]

[[AOM-3841_CAN_FD（CAN0/1）|CAN FD（CAN0/1）]]

[[AOM-3841_Video_In_（MIPI_CSI0/CIS1）——Camera|Video In （MIPI CSI0/CIS1）——Camera]]

[[AOM-3841_GPIO_CN3|GPIO_CN3]]

[[AOM-3841_ADC_Pin_Header|ADC_Pin Header]]

[[AOM-3841_Watchdog|Watchdog]]

[[AOM-3841_RTC|RTC]]

== '''Linux BSP 编译方法（Linux BSP Compile Method）''' ==

=== [[Linux_BSP_User_Guide_for_AOM-3841_Series-Debian12|Linux_BSP_User_Guide_for AOM-3841 Series-Debian12]] ===

AOM-3841 Android15 Release notes

2026-02-02T03:14:53Z

Xingxing.li: Created page with " '''Release Note ''' {| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%" |- | '''SDK version ''' | ANDROID15_RKR4 |- | '''Uboot version&nbsp..."

'''Release Note '''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width="30%"
|-
| '''SDK version '''
| ANDROID15_RKR4
|-
| '''Uboot version '''
| 2017.09
|-
| '''Kernel version '''
| 6.1.118
|}

 

'''Change List'''

{| bgcolor="#F8F8F8" border="1" cellpadding="1" cellspacing="1" width=""
|-
| '''Item'''
|
'''Description'''

|-
| '''1'''
| Beta release
|-
| '''2'''
|  
|}

 

'''Accessories Support List'''

{| border="1" cellpadding="1" cellspacing="1" style="width: 714px;"
|-
! scope="col" | Item
! scope="col" | Advantech PN
! scope="col" style="width: 151px;" | Chip/Vendor
! scope="col" style="width: 85px;" | MPN
! scope="col" style="width: 51px;" | Factor
! scope="col" style="width: 260px;" | Host Interface
|-
| 5G
|  
| style="width: 151px;" | Quectel
| style="width: 85px;" | RM520N-GL
| style="width: 51px;" | M.2
| style="width: 260px;" | PCIE
|-
| Codec
| ROM-EG57
| style="width: 151px;" | RTL  ALC5640-VB-CGT
| style="width: 85px;" |  
| style="width: 51px;" |  
| style="width: 260px;" | Audio Codec board for RK series
|}

AOM-3841 Android15 Release Note

2026-02-02T02:59:43Z

Note: '''L'''IV= Yocto Linux , '''U'''IV=Ubuntu , '''D'''IV = Debian , '''A'''IV = Android, L'''B'''V=BSP , L'''I'''V= Image
<div style="text-align:start; -webkit-text-stroke-width:0px">
{| class="wikitable" style="font-size:14px; margin:1em 0px; background-color:#f9f9f9; border:1px solid #aaaaaa; border-collapse:collapse; color:#000000" width="1000"
|-
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:280px" | '''Platform'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:280px" | '''Product'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:80px" | '''Image Version'''
| style="border:1px solid #aaaaaa; background:none 0% 0% repeat scroll #f0f0f0; width:80px" | '''Release Date'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:80px" | '''Release Version'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:80px" | '''Release notes'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:126px" | '''Image Download'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:173px" | '''BSP Download Tag'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:173px" | '''Test Report'''
| style="border:1px solid #aaaaaa; background:#f0f0f0; width:173px" | '''Comment'''
|-
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:280px; background-color:#f9f9f9" | RK3576
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:280px; background-color:#f9f9f9" | AOM-3841
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:80px; background-color:#f9f9f9" | v0.1.7
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:80px; background-color:#f9f9f9" | 2025/11/18
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:80px; background-color:#f9f9f9" | Beta
| style="border:1px solid #aaaaaa; width:80px" | [[AOM-3841_Android15_Release_notes|Release_note]]
| style="border:1px solid #aaaaaa; width:126px" |
[https://pan.baidu.com/s/1MsenQ8w01SU4PXi1_IkeVA?pwd=a887 Baidu]

Password：a887

[https://www.dropbox.com/scl/fo/qzdpwymv2u8qhizg62dkf/APa2yHpYGQ-thT9DZuwyH94?rlkey=5qd5uaeauyoou4eprcfeumx4w&st=fsyjdfx4&dl=0 Dropbox]

| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:173px; background-color:#f9f9f9" | aom3841a1_android-15.0-mid-rkr4_v0.1.7_kernel-6.1.118_rk3576.xml
| style="border:1px solid #aaaaaa; width:583px" | [https://ess-wiki.advantech.com.tw/wiki/images/3/3d/Aom3841a1_android-15.0-mid-rkr4_v0.1.7_kernel-6.1.118_rk3576_2025-11-19_test_report.xlsx Test Report]
| style="border:1px solid #aaaaaa; padding:0.2em 0.4em; width:583px; background-color:#f9f9f9" |  
|}
<ul style="/* insecure input */">
<li>Alpha:  Basic I/O function bring up by RD;</li>
</ul>
<ul style="/* insecure input */">
<li>Beta:  Basic I/O function、performance and middleware verified by RD. Peripherals integrated;</li>
</ul>
<ul style="/* insecure input */">
<li>GA:  Beta version by QE verification;</li>
</ul>
<ul style="/* insecure input */">
<li>RTM:  Beta version by SI/Power/QE verification and pre-loaded;</li>
</ul>
</div>