Copy files back to the development board in reverse direction and repeat the test 3 times.

Expected Results:

Transmission speed ≥ 80MB/s (about 640Mbps) under USB 3.0 mode.
Transmission speed ≥ 30MB/s (about 240Mbps) under USB 2.0 mode.
No data loss, transmission interruption or file corruption.

2.3 Power Supply Capability Test

Prerequisites:

Same as Section 2.1
Prepare a 2.5-inch portable hard drive (requiring power supply of 5V/0.5A or above)

Operation Steps:

Connect the portable hard drive to the USB port of the Hub.
Check if the hard drive indicator light is on, and run lsblk to view the device node.
Perform large file read and write operations continuously for 10 minutes.
Check system logs for warnings about insufficient power or device disconnection.

Expected Results:

The portable hard drive starts normally and can be recognized, read and written by the system.
No device disconnection or data corruption during long-duration read and write operations.
No over-current or power supply related errors in system logs.

2.4 Abnormal Scenario Test

Hot-plug test: Plug and unplug USB devices during data transmission to verify system stability.
Low voltage test: Reduce the power supply voltage of the development board to 4.5V and check if USB devices work normally.
Multi-device concurrency test: Connect multiple USB devices simultaneously to verify the load capacity of the Hub.

3. Type-C to HDMI/DP Output Test

3.1 Video Output Function Test

Prerequisites:

The development board is powered on and the system boots up completely.
The Type-C to HDMI/DP adapter is connected properly and the monitor is powered on.

Operation Steps:

Plug the Type-C end into the Type-C port of the development board, and connect the HDMI/DP end to the monitor.
Execute display configuration commands (Linux: xrandr; Android: System Settings).
Switch display output to HDMI and set the resolution to 1080P@60Hz.
Observe the screen and check for screen distortion, black screen or flickering.

Expected Results:

The monitor lights up automatically and displays the desktop or screen of the development board.
Resolution and refresh rate can be configured normally with clear and undistorted images.
No screen distortion, black screen, flickering or lag.

3.2 Audio and Video Synchronization Test

Prerequisites:

Same as Section 3.1
The monitor supports HDMI/DP audio output.

Operation Steps:

Play a 1080P test video with audio tracks.
Observe video fluency and listen to sound from the monitor speaker.
Check audio-video synchronization and verify for noise or audio interruption.

Expected Results:

The video plays smoothly with stable frame rate (≥30fps).
Audio and video are synchronized without lag or stutter.
Sound is clear with no noise, interruption or popping sound.

3.3 Hot-plug Test

Prerequisites:
Same as Section 3.1
Operation Steps:

Connect the Type-C to HDMI/DP adapter first and confirm normal display.
Unplug the HDMI/DP end and observe system response.
Reconnect the HDMI/DP end and observe system response.
Repeat hot plugging 10 times and record each result.

Expected Results:

After unplugging HDMI/DP, the system automatically switches back to the onboard display or goes black (in line with design requirements).
The monitor restores display automatically after reconnection without manual configuration.
No system crash or driver errors occur during hot plugging.

3.4 Abnormal Scenario Test

Resolution switching test: Switch among 720P/1080P/4K to verify display compatibility.
Long-time playback test: Play videos continuously for 24 hours to verify stability.
Low-resolution output test: Set resolution to 480P to verify downward compatibility.

III. Display and Video Interface Test

1. HDMI/DP Output Test

1. Specification Description:

Sv translation

language	en

Test File Download

uart file download ：uart
test.wav download ：test.wav
UartAssist.exe download：UartAssist.exe

Basic Equipment Information

1. Basic Equipment Information

Item	Details
Device Model	EDGE-RK3588 Development Board
Hardware Version	V1.2A
System Version	Debian 11 Xfce
Firmware Version	rk3588_edge_v12_debian_xfce_rk7_v1.2 (Neutral Version)
Kernel Version	Linux 5.10

2. Core Hardware Configuration

Item	Configuration Details
CPU	8-core heterogeneous architecture: 4×Cortex-A76 (High-performance Core) + 4×Cortex-A55 (Energy-efficient Core), max main frequency up to 2.4GHz
GPU	Mali-G610 MP4 Graphics Processor Supported standards: OpenGL ES 1.1/2.0/3.2, OpenCL 2.2, Vulkan 1.2
DDR Memory	LPDDR4X, optional capacity: 4GB/8GB/16GB
NPU AI Computing Power	6.0 TOPS, supports INT4/INT8/FP16 computing precision
Onboard Storage	Supports eMMC 5.1 / SDIO 3.0 interface Optional capacity: 16GB/32GB/64GB/128GB

3. Power Supply Parameters

Item	Specification
DC Power Requirement	Input: 12V 2A DC Interface: 5.5mm × 2.0mm DC barrel port ⚠️ Note: Voltage lower than 12V may cause boot failure
Extended Power Supply	Reserved POE power interface, supports external POE module power supply (separate configuration required)

I. Basic Power Supply Test

1. Power Interface Function Verification

Verify the compatibility, electrical performance and safety of the device power interface to ensure compliance with power supply parameter requirements.。

2. Test Environment and Tool Adaptability

Tools / Environment	Specifications
DC Power Adapter	12V 2A DC (Compatible with 5.5mm×2.0mm interface)
Multimeter	Supports voltage and current measurement
POE Module (Optional)	Matches reserved POE interface of the device
DUT	Target product (with power interface)

3. Basic Test Procedure Specifications

1. DC Power Interface Compatibility Test

Test Steps:
1.Confirm the DC power adapter is 12V 2A DC with 5.5mm×2.0mm interface size.
2.Connect the adapter to the device power interface, then check if the device powers on normally.
Judgment Standard:
The power plug can be smoothly inserted and pulled out, and the device starts up normally without any abnormality.

2. Input Voltage Lower Limit Verification

Test Steps:
1.Adjust the adjustable DC power supply to 11.5V (lower than 12V) and connect it to the device.
2.Observe whether the device fails to boot or other abnormal conditions occur.
Judgment Standard:
The device cannot start normally when the voltage is lower than 12V, which is consistent with the notes of power supply parameters.

3. POE Interface Extended Power Supply Test (Optional)

Test Steps:
1.Connect the POE module to the reserved POE interface of the device.
2.Power on the POE module and observe the operating state of the device.
Judgment Standard:

The device can be stably powered by the POE module and operates normally.

2

II.Wired Communication Interface Test

1.RS232 Serial Port Test

RS232 corresponding device node: ttyS3 (V1.2 version) / ttyS4 (V1.4 version)

Test Preparation:

1.Confirm the serial port node

代码块

language	shell
title	bash

# Method 1: List all serial ports
ls -la /dev/ttyS*

# Method 2: Determine by hardware version
# Check board version label or run:
cat /proc/device-tree/model
# If output contains V1.4, use /dev/ttyS4
# If output contains V1.2, use /dev/ttyS3

2.Two-minute Loopback Test

代码块

language	shell
title	bash

# Step 1: Hardware Short Connection (Required)
# Short TX (Pin 2) and RX (Pin 3) of the RS232 interface using a jumper wire

# Step 2: Prepare Test Tool
# Upload the UART test program to the device (if transferring from Windows)
adb push C:\Users\Administrator\Desktop\uart ./

# Step 3: Grant Permissions
chmod 777 ./uart

# Step 4: Execute Test
# Terminal 1: Receive data
cat /dev/ttyS3

# Terminal 2: Send data
./uart /dev/ttyS3
# Enter test text and check the reception result in Terminal 1

Output Example

代码块

language	shell
title	bash

# Terminal 2 Program Output Example:
# fcntl=0
# isatty success!
# fd-open=3
# set done!
# please input:         # Waiting for user input (e.g. 45 3A F7 98)

# Terminal 1 receives the data input from Terminal 2 (e.g. 45 3A F7 98)

2.RS485 Serial Port

Test


Test Purpose
 Verify the bidirectional data communication function of the RS485 serial port (mapped to system device /dev/ttyS0) of the RK3588 device with the UART Assist tool on the computer side, ensuring the availability of the serial port hardware, driver and communication link.

Test Environment

Device / Tool	Configuration Information
RK3588 Device	System: Embedded Linux (e.g. Armbian) RS485 Serial Port: /dev/ttyS0 (Baud Rate 115200, 8N1)
PC	Tool: UART Assist (Serial Debug Assistant) Hardware: USB to RS485 Module (e.g. CH340+MAX485)
Connection	RS485 Wiring: Connect RS485_A of RK3588 to Module A, RS485_B to Module B, Common Ground (GND)

3. Hardware Wiring

Connect RK3588 RS485 pins to the USB-to-RS485 module:
- RK3588 RS485_A → Module A
- RK3588 RS485_B → Module B
- RK3588 GND → Module GND (Common ground is required to avoid signal interference)
Connect the USB-to-RS485 module to the computer's USB port and install the corresponding driver (e.g. CH340 driver).

4. Test Steps

4.1 PC-side UART Assist Configuration

Open the UART Assist tool and select the serial port corresponding to the USB-to-RS485 adapter (e.g. COM3);
Configure parameters: Baud rate 115200, Data bits 8, Parity none, Stop bits 1, Flow control none;
Click "Open Serial Port" to confirm a successful connection.

4.2 Unidirectional Transceiver Test (PC → RK3588)

Start serial port reception on the RK3588 side:

代码块

language	shell
title	bash

# Step 1: Prepare Test Tool
# Upload the UART test program to the device (if transferring from Windows)
adb push C:\Users\Administrator\Desktop\uart ./

# Step 2: Grant Permissions
chmod 777 ./uart

# Step 3: Execute Test
# Terminal 1: Receive data
cat /dev/ttyS0

# Terminal 2: Run the command tool to configure correct serial port parameters
./uart /dev/ttyS0

2.Enter test data (e.g. "RK3588 RS485 Test") in UART Assist on the PC side, and click "Send" (as shown in the figure below);

3.Observe RK3588 Terminal 1 (as shown in the figure below). If the received test data is displayed, the unidirectional receiving function is normal.

4.3 Unidirectional Transceiver Test (RK3588 → PC)

Keep UART Assist on the PC side in the "Open" state;
Send test data on the RK3588 side:

代码块

language	shell
title	bash

# Step 1: Prepare Test Tool
# Upload the UART test program to the device (if transferring from Windows)
adb push C:\Users\Administrator\Desktop\uart ./

# Step 2: Grant Permissions
chmod 777 ./uart

# Step 3: Execute Test
# Send data
./uart /dev/ttyS0
# Enter test text (as shown in the figure below)

3.Observe UART Assist on the PC side (as shown in the figure below). If the received test data is displayed, the unidirectional transceiver function is normal.

3. USB Interface Test

1.Device Connection Status Identification
Use the following commands to confirm whether the device is connected to the system and obtain device node information:

代码块

language	shell
title	bash

# View all block devices and identify the USB device node (e.g. /dev/sda1)
lsblk
# View detailed USB device information, including controller and device ID
lsusb

Result Description: In the output of lsusb, ID 1d6b:0002 stands for USB 2.0 controller, and ID 1d6b:0003 stands for USB 3.0 controller. The corresponding USB version can be judged by the bus where the device is mounted.

2.USB Version Compatibility Test
Accurately confirm USB version via device speed parameters. USB2.0 corresponds to High-Speed (480Mbps), USB3.0 corresponds to Super-Speed (5000Mbps). Operations are as follows:

1.Check device speed file

代码块

language	shell
title	bash

# Traverse all USB devices and output their transfer speed
for device in $(ls /sys/bus/usb/devices/); do
    if [ -f "/sys/bus/usb/devices/$device/speed" ]; then
        speed=$(cat /sys/bus/usb/devices/$device/speed)
        echo "Device: $device, Speed: $speed Mbps"
    fi
done

2.通过详细信息验证Verify through detailed information

代码块

language	shell
title	bash

# 查看指定USB设备的详细参数，搜索Speed字段 View detailed parameters of specified USB device, filter Speed field
lsusb -v | grep -E "Speed|Device"

结果说明：输出中 Result description: In the output, Speed: 480Mbit/s 对应 corresponds to USB2.0，0, and Speed: 5000Mbit/s 对应 corresponds to USB3.0。0.

3.

传输性能测试传输速率是

Transmission Performance Test

Transmission speed is the core difference between USB2.0

与

and USB3.0

的核心差异点，USB2.0 理论速率 480Mbps，USB3.0 理论速率 5Gbps。以下提供两种常用测试方法，分别适用于存储设备和网络类 USB 设备。

. The theoretical speed of USB2.0 is 480Mbps, while that of USB3.0 is 5Gbps. Two commonly used test methods are provided below, applicable to USB storage devices and network USB devices respectively.

1. Simple Test: dd Command

The dd command can quickly test read and write speeds for preliminary verification. Mount the USB device first before testing.
1.1 Mount the USB device:

1. 简易测试：dd 命令

dd命令可快速测试读写速率，适合初步验证，测试时需先挂载 USB 设备。

1.1.挂载 USB 设备：

代码块

language	shell
title	bash

# 假设通过lsblk确认USB设备节点为Assume the USB device node is /dev/sda1，创建挂载点并挂载sda1 confirmed by lsblk, create mount point and mount
mkdir -p /mnt/usb
mount /dev/sda1 /mnt/usb

1 1.2 . 测试顺序写速率：Test sequential write speed:

代码块

language	shell
title	bash

# 写入1GB零数据到USB设备，绕过缓存确保结果真实 Write 1GB zero data to the USB device, bypass cache to ensure real results
dd if=/dev/zero of=/mnt/usb/testfile bs=1M count=1024 conv=sync oflag=direct

1.3.测试顺序读速率：Test sequential read speed:

代码块

language	shell
title	bash

# 读取USB设备中的测试文件并丢弃，测试读取速度
dd Read the test file from the USB device and discard it to test the read speed
dd if=/mnt/usb/testfile of=/dev/null bs=1M iflag=direct

1.4.测试后清理临时文件：Clean up temporary files after testing：

代码块

language	shell
title	bash

rm /mnt/usb/testfile

结果说明：命令执行完毕后会显示传输时间和速率，USB2.0 实际写速率通常在 10 - 30MB/s，USB3.0 实际写速率通常在 50 - 150MB/s（受设备本身性能影响）。

2. 专业测试：fio 工具

fio工具支持复杂的 IO 场景测试，结果更全面，适合深度性能评估。

2.1.安装 fio：

Result Description: After the command is executed, the transfer time and speed will be displayed.

The actual write speed of USB 2.0 is usually 10 - 30 MB/s.
The actual write speed of USB 3.0 is usually 50 - 150 MB/s (affected by the performance of the device itself).

2. Professional Test: fio Tool

The fio tool supports complex IO scenario testing with more comprehensive results, suitable for in-depth performance evaluation.

2.1 Install fio:

代码块

language	shell
title	bash

# Ubuntu/Debian
sudo apt install fio -y

2.2.Code block for fio 测试命令代码块test commands：

代码块

language	shell
title	bash

# Sequential write 顺序写测试test
fio -filename=/temp/testfile -direct=1 -ioengine=psync -iodepth 128 -rw=write -bs=1M -size=3G -numjobs=4 -runtime=30 -group_reporting -name=iopstest -time_based=1

# 顺序读测试Sequential read test
fio -filename=/temp/testfile -direct=1 -ioengine=psync -iodepth 128 -rw=read -bs=1M -size=3G -numjobs=4 -runtime=30 -group_reporting -name=iopstest -time_based=1

# 随机写测试Random write test
fio -filename=/temp/testfile -direct=1 -ioengine=psync -iodepth 128 -rw=randwrite -bs=1M -size=3G -numjobs=4 -runtime=30 -group_reporting -name=iopstest -time_based=1

# Random 随机读测试read test
fio -filename=/temp/testfile -direct=1 -ioengine=psync -iodepth 128 -rw=randread -bs=1M -size=3G -numjobs=4 -runtime=30 -group_reporting -name=iopstest -time_based=1

# 随机读写混合测试（默认读写比例 Mixed random read/write test (default read/write ratio 50:50）50)
fio -filename=/temp/testfile -direct=1 -ioengine=psync -iodepth 128 -rw=randrw -bs=1M -size=3G -numjobs=4 -runtime=30 -group_reporting -name=iopstest -time_based=1

4. Type-

C接口测试

C Interface Test

1.

ADB功能测试

ADB Function Test

1.1

. ADB基础连接测试

测试目的：验证 Type‑C 接口可正常建立 ADB 连接，设备可被 PC 识别。

测试步骤：

1.用 Type‑C 数据线连接待测设备与 PC。

2.设备端开启「开发者选项」→「USB 调试」。

3.PC 端执行 adb devices，检查设备是否被识别。

4.执行 adb shell，验证是否可进入设备命令行。

预期结果：

1.adb devices 输出设备序列号，状态为 device。

2.成功进入设备 shell，无连接超时或权限拒绝。

1.2. ADB 核心指令执行测试

测试目的：验证 ADB 核心指令在 Type‑C 链路下可正常执行。

测试步骤：

1.用文件传输：

执行

Basic ADB Connection Test

Test Purpose: Verify that the Type-C interface can establish ADB connection normally and the device can be recognized by PC.
Test Steps:

Connect the device under test and PC with a Type-C data cable.
Enable Developer options → USB debugging on the device.
Run adb devices on PC to check if the device is detected.
Run adb shell to verify access to the device command line.

Expected Results:

adb devices displays the device serial number with the status shown as device.
Successfully enter the device shell without connection timeout or permission denial.

1.2 Core ADB Command Execution Test

Test Purpose: Verify that core ADB commands work properly over the Type-C link.
Test Steps:

File transmission:
Run adb push test_file /data/

推送文件至设备。执行

2.设备控制：

执行 adb reboot 重启设备，重启后重新执行 adb devices。

3.日志抓取：

执行

to send files to the device.
Run adb pull /data/test_file ./

拉取文件至 PC。

to download files to PC.
Device control:
Run adb reboot to restart the device, then execute adb devices again after reboot.
Log capture:
Run

adb logcat -d > adb_log.txt

抓取系统日志。

to capture system logs.

Expected Results:

File transmission completes successfully, and the downloaded file has the same size as the original.
ADB connection recovers automatically after reboot.
The log file is not empty and contains valid running logs.

1.3 Type-C Plug & Play and Stability Test

Test Purpose: Verify the stability of ADB connection during Type-C cable plugging, unplugging and shaking.
Test Steps:

Single plug operation: Plug and unplug the data cable 10 times, and run adb devices after each operation.
Continuous plug operation: Rapidly plug and unplug 20 times with an interval of 1–2 seconds.
Shake test: Keep the cable connected and shake it gently, then observe the connection status.

Expected Results:

The device is recognized normally after each operation with no offline status.
ADB connection remains stable during shaking with no I/O errors.

1.4 High-load Stability Test for Type-C Connection

Test Purpose: Verify the stability of Type-C ADB function under high load.
Test Steps:

Large file transmission: Push a 1GB file to the device while running adb logcat.
Concurrent commands: Run adb push, adb shell top and adb logcat simultaneously.
Long-duration connection: Maintain ADB connection for 24 hours and run adb devices every hour.

Expected Results:

ADB connection stays active during large file transmission, and log capture works normally.
No crash or timeout occurs when running multiple commands; CPU usage ≤ 80%.
The connection status remains device within 24 hours with no disconnection.

2. Type-C to USB Hub Test

2.1 Device Recognition and Compatibility Test

Prerequisites:

The development board is powered on and the system boots up completely.
The Type-C to USB Hub is connected properly.

Operation Steps:

Insert the Type-C end into the Type-C port of the development board.
Connect USB devices (USB flash drive, mouse, keyboard) to the USB ports of the Hub one by one.
Run lsusb to view the device list.
Check system logs with dmesg | grep usb.

Expected Results:

All USB devices are recognized correctly, and corresponding device IDs are shown in the lsusb output.
No recognition failures or error messages related to USB devices in system logs.
The USB flash drive can be mounted and read/written normally; the mouse and keyboard respond properly.

2.2 Data Transfer Speed Test

Prerequisites:

Same as Section 2.1
Prepare a 1GB test file named test.img

Operation Steps:

Connect a USB 3.0 flash drive and mount it to /mnt/usb.
Run the file copy command:

预期结果：

1.文件传输无失败，拉取文件与原文件大小一致。

2.重启后 ADB 连接可自动恢复。

3.日志文件非空，包含有效运行日志。

1.3. Type‑C 插拔与稳定性测试

测试目的：验证 Type‑C 接口在插拔、晃动等场景下 ADB 连接的稳定性。

测试步骤：

1.单次插拔：插拔数据线 10 次，每次插拔后执行 adb devices。

2.连续插拔：快速插拔 20 次，间隔 1–2 秒。

3.晃动测试：保持连接状态，轻微晃动数据线，观察连接状态。

预期结果：

1.每次插拔均可正常识别设备，无 offline 状态。

2.晃动过程中 ADB 连接不中断，无 IO 错误。

1.4. Type‑C 插拔与稳定性测试

测试目的：验证高负载场景下 Type‑C ADB 功能的稳定性。

测试步骤：

1.大文件传输：推送 1GB 文件至设备，同时执行 adb logcat。

2.多指令并发：同时执行 adb push、adb shell top、adb logcat。

3.长时间连接：保持 ADB 连接 24 小时，每小时执行 adb devices。

预期结果：

1.大文件传输过程中 ADB 不中断，日志抓取正常。

2.多指令并发无卡死或超时，CPU 占用 ≤ 80%。

3.24 小时内连接状态持续为 device，无自动断开。

2.Type-C 转 hub（USB）测试

2.1 设备识别与兼容性测试前置条件：

1.开发板上电正常，系统启动完成

2.Type-C 转 USB Hub 连接正常

操作步骤：

1.将 Type-C 端插入开发板 Type-C 接口

2.将 USB 设备（U 盘、鼠标、键盘）依次插入 Hub 的 USB 口

3.执行命令 lsusb 查看设备列表

4.查看系统日志 dmesg | grep usb

预期结果：

1.所有 USB 设备均能被系统正确识别，lsusb 输出中可见对应设备 ID

2.系统日志无 USB 设备识别失败或报错信息

3.U 盘可正常挂载 / 读写，鼠标 / 键盘可正常响应

2.2 数据传输速率测试

前置条件：

1.同 2.1

2.准备 1GB 测试文件（test.img）

操作步骤：

1.插入 USB3.0 U 盘并挂载到 /mnt/usb

2.执行文件拷贝命令：

代码块
dd if=/dev/zero of=/mnt/usb/test.img bs=1M count=1024

3.记录传输耗时，计算速率：速率 Record the transmission time and calculate the speed: Speed = 1024MB / 耗时（秒）Time (seconds)

4.反向拷贝回开发板，重复测试 3 次

预期结果：

1.USB3.0 模式下传输速率 ≥ 80MB/s（约 640Mbps）

2.USB2.0 模式下传输速率 ≥ 30MB/s（约 240Mbps）

3.无数据丢失、无传输中断、无文件损坏

2.3 供电能力测试

前置条件：

1.同 3.1

2.准备 2.5 英寸移动硬盘（需 5V/0.5A 以上供电）

操作步骤：

1.将移动硬盘插入 Hub 的 USB 口

2.观察硬盘指示灯是否亮起，执行 lsblk 查看设备节点

3.进行大文件读写操作，持续 10 分钟

4.查看系统日志是否有供电不足或设备掉线信息

预期结果：

1.移动硬盘正常启动，系统可识别并读写

2.长时间读写过程中无设备掉线、无数据损坏

3.系统日志无 over-current 或供电相关报错

2.4. 异常场景测试

1.热插拔测试：在数据传输过程中插拔 USB 设备，验证系统稳定性

2.低电压测试：降低开发板供电电压至 4.5V，验证 USB 设备是否正常工作

3.多设备并发测试：同时插入多个 USB 设备，验证 Hub 负载能力

3.Type-C 转 HDMI/DP 输出测试

3.1 视频输出功能测试

前置条件：

1.开发板上电正常，系统启动完成

2.Type-C 转 HDMI/DP 转接器连接正常，显示器通电

操作步骤：

1.将 Type-C 端插入开发板 Type-C 接口，HDMI/DP 端插入显示器

2.执行显示配置命令（Linux：xrandr；Android：系统设置）

3.切换显示输出到 HDMI，设置分辨率为 1080P@60Hz

4.观察显示器画面，检查是否有花屏、黑屏、闪烁

预期结果：

1.显示器自动点亮，显示开发板桌面 / 画面

2.分辨率、刷新率可正常配置，画面清晰无失真

3.无花屏、无黑屏、无闪烁、无延迟

3.2 音视频同步输出测试

前置条件：

1.同 3.1

2.显示器支持 HDMI/DP 音频输出

操作步骤：

1.播放 1080P 测试视频（带音轨）

2.观察画面流畅度，同时监听显示器扬声器

3.检查音画是否同步，有无杂音、断音

预期结果：

1.视频画面流畅，帧率稳定（≥30fps）

2.音画同步，无延迟、无卡顿

3.声音清晰，无杂音、无断音、无爆音

3.3 热插拔测试

前置条件：

同 3.1

操作步骤：

1.先连接 Type-C 转 HDMI/DP，确认显示正常

2.拔掉 HDMI/DP 端，观察系统反应

3.重新插入 HDMI/DP 端，观察系统反应

4.重复热插拔 10 次，记录每次结果

预期结果：

1.拔掉 HDMI/DP 后，系统自动切回板载显示或黑屏（符合设计预期）

2.重新插入后，显示器自动恢复显示，无需手动配置

3.热插拔过程中无系统崩溃、无驱动报错

3.4. 异常场景测试

1.分辨率切换测试：在 720P/1080P/4K 之间切换，验证显示兼容性

2.长时间播放测试：连续播放视频 24 小时，验证稳定性

3.低分辨率输出测试：设置为 480P，验证向下兼容能力

三、显示与视频接口测试

1.HDMI/DP输出测试

1.规格说明：

接口核心规格关键限制

HDMI 2.1 单接口、支持 8K@30Hz/4K@60Hz、HDCP2.3 需 HDMI2.1 认证线缆，最大带宽 48Gbps

DP 1.4a（4Lane）单接口、支持 4K@60Hz、HDCP2.3 4K 可满帧 60Hz

Interface	Core Specifications	Key Limitations
HDMI 2.1	Single port, supports 8K@30Hz / 4K@60Hz, HDCP 2.3	Requires HDMI 2.1 certified cable, maximum bandwidth 48Gbps
DP 1.4a (4Lane)	Single port, supports 4K@60Hz, HDCP 2.3	Full 60Hz frame rate available for 4K resolution

Character device (starts with c)	HDMI input video capture device (core)	Read/writable by root/video group; major number 81, minor number 0
/dev/video-dec0

Reconnect the HDMI cable to ensure good contact
No playback window on the display	Incorrect configuration of the DISPLAY environment variable	Run `echo $DISPLAY` to confirm the value is `:0.0`, or execute commands in the local terminal
Stuttering / distorted image	Incompatible resolution of the signal source	Adjust the output resolution of the HDMI signal source to 1080P@60Hz and test again

Item	Details
Tool Name	ppvidedec
Tool Version

264, VP8, VP9
Decoding Type	Hardware-accelerated decoding
Maximum Decoding Capability	Supports 8K 10-bit

Idle ratio exceeds 90%, sufficient CPU resource redundancy; current high-ratio processes are desktop services (Xorg, xfwm4), belonging to basic system load
Memory Status	Total 3899MB, Used 829MB, Free 2968MB	Sufficient remaining memory, no risk of insufficient memory
Key Process CPU Ratio	Desktop Service (Xorg) 50%, Terminal (tilda) 12.5%	When running the video playback process, focus on its % CPU value (usually <10% when hardware decoding takes effect)
Memory Usage	Used 829MB, Cache 2864MB	High memory cache ratio ensures efficient system data read/write

Audio output for the first HDMI port
1	rockchipdp0	DisplayPort0

1st DisplayPort port (video output only, no audio support)
2	rockchipdp1	DisplayPort1

2nd DisplayPort port (video output only, no audio support)
4	rockchipes8388	ES8388 Codec

Audio plays normally on the display device
Onboard Headphone Output	aplay -D plughw:4,0 /test.wav

Audio plays normally through headphones
Hardware Sine Wave Test	speaker-test -D hw:4,0 -t sine -f 1000 -c 2 -l 2

audio capture card	Corresponds to the HDMI input audio channel of Rockchip chip Used to capture audio stream from HDMI signal	Detected normally (Subdevices: 1/1)
card 4: rockchipes8388 device 0

页面树结构

页面历史记录

版本比较

旧版本 121

新版本 当前版本

标识

Test File Download

Basic Equipment Information

I. Basic Power Supply Test

1. Power Interface Function Verification

2. Test Environment and Tool Adaptability

3. Basic Test Procedure Specifications

1. DC Power Interface Compatibility Test

2. Input Voltage Lower Limit Verification

3. POE Interface Extended Power Supply Test (Optional)

II.Wired Communication Interface Test

1.RS232 Serial Port Test

2.RS485 Serial Port

Test

3. USB Interface Test

1. Simple Test: dd Command

2.1 Install fio:

4. Type-

C Interface Test

1.

ADB Function Test

1.1

Basic ADB Connection Test

1.2 Core ADB Command Execution Test

1.3 Type-C Plug & Play and Stability Test

1.4 High-load Stability Test for Type-C Connection

2. Type-C to USB Hub Test

2.1 Device Recognition and Compatibility Test

2.2 Data Transfer Speed Test

2.Type-C 转 hub（USB）测试

3.Type-C 转 HDMI/DP 输出测试

三、显示与视频接口测试

1.HDMI/DP输出测试

2.3 Power Supply Capability Test

2.4 Abnormal Scenario Test

3. Type-C to HDMI/DP Output Test

3.1 Video Output Function Test

3.2 Audio and Video Synchronization Test

3.3 Hot-plug Test

3.4 Abnormal Scenario Test

III. Display and Video Interface Test

1. HDMI/DP Output Test

2. HDMI

Input Test

3.视频硬解码性能测试

3. Video Hard Decoding Performance Test

四、音频接口测试

V. Audio Interface Test

1.Audio Output Function Verification

2.

Audio Input Function Verification

VI. Storage Interface Test

1.M.2

Interface Test

1.

Device Identification Verification

2.

SATA Interface Test

VII. Wireless Communication Module Test

1.

Wi‑Fi Test

3. Wi-Fi

Network TCP/UDP

Protocol Performance Test

3.

4G Module Test

4.

SIM Card Function Verification

新版本当前版本