4.5.1. Overview

Driver functional unit testing is a critical phase for verifying the stability, performance, and functional integrity of system drivers and hardware components. This chapter provides a detailed introduction to the test methods and standards for various driver functional units, ensuring the system delivers high reliability and excellent performance in real-world application scenarios.

4.5.1.1. Test Program Storage Path

To facilitate unified management and usage of test code, scripts, and tools, all test resources described in this chapter have been integrated into the BSP source code of the SDK delivery package. The storage path is as follows:

SDK Delivery Package BSP Path: app/samples/platform_samples/chip_base_test

When developers use the officially released SDK delivery package, the EVB (Evaluation Board) system image provided will by default install all test programs onto the following path on the development board:

Development Board Path: /app/platform_samples/chip_base_test

4.5.1.2. Test Environment Preparation

Before conducting driver functional unit tests, ensure the following environment preparations are completed:

Use the officially released SDK delivery package, which includes the corresponding test code and tools.
On the development board, verify the storage paths of test tools and scripts:
```
ls /app/platform_samples/chip_base_test
```
Follow the test methods described in this chapter to execute the corresponding test programs step by step, and record and analyze the results.

4.5.1.3. Test Execution Method

Developers can run test programs directly on the development board using the following steps:

Log in to the development board via serial port or SSH.

Navigate to the test program directory:

cd /app/platform_samples/chip_base_test

Execute the corresponding test script or program. For example, to run CPU / BPU / DDR stress tests:
```
cd /app/platform_samples/chip_base_test/01_cpu_bpu_ddr/scripts
./stress_test.sh
```

4.5.1.4. Test Objectives and Standards

Driver functional unit testing aims to achieve the following core objectives:

Functional Verification: Ensure the driver correctly implements the designed functionality.
Stability Testing: Verify driver stability through long-duration operation and boundary condition testing.
Performance Testing: Measure performance metrics between the driver and hardware to ensure system requirements are met.
Compatibility Testing: Validate driver compatibility across different hardware configurations or software versions.

Detailed test methods, procedures, and pass/fail criteria for each driver type will be elaborated in subsequent chapters.