Stress test image

As of 0.4.1, rsetup can be used to create stress test images. This functionality relies on proper gpiod pin definition, as well as correct GPIO LEDs device tree definition, both are part of the system release requirements. As such, this can be used as a unified method to create stress test images.

factory_stress

This function is implemented in factory_stress, where the detailed command definition can be found in the source code.

To run this command, you need to supply a GPIO pin name, which will be connected to the GND/VCC pin during the device boot, as well as the default state when no wire is connected.

The factory stress test procedure begins with the pin connected, which is recognized by factory_stress as a signal to start the stress test, and update LEDs' pattern. The QA engineer will then disconnect the wire once the LED pattern indicates the test is started. This way, if the device fails the stress test and is rebooted, factory_stress will not be started again due to the GPIO value does not match the specified value.

Prepare the image

This is generally broken into 2 stages: find the GPIO pin's default status, and update the image.

Find the default GPIO status

While in theory any GPIO pins can be used, we should look for pins that are easy to identify. One such example is pin 40 which is at the end of the header, as well as being close to a GND pin to pull down (if the default state is high).

For example, on Radxa ZERO, if we want to use pin 7, we should run the following command on ZERO:

radxa@radxa-zero:~$ gpioget $(gpiofind PIN_7)
1

Since the default state is 1, we will instruct the QA engineer to connect pin 7 and pin 9 (which is GND) at the start of the test.

Update the image with stress test config

To run the stress test at the boot time, first, mount and systemd-nspawn into the image (you can use bsp with ./bsp install stress.img for this).

You should then install the required stress test utilities. Currently, they are stress-ng and memtester:

sudo apt-get update && sudo apt-get install -y stress-ng memtester

You should then delete /config/before.txt, which will cause a long boot delay due to the need to complete the first boot configuration. You can put a very basic system configuration there (so you can log in to check the issue), and then start the stress test. Continuing the above example of Radxa ZERO, this is the command we will use:

sudo rm /config/before.txt
cat << EOF | sudo tee -a /config/config.txt
no_fail
add_user radxa radxa
user_append_group radxa sudo
factory_stress PIN_7 0
EOF

Save and unmount the image. You can now deliver the stress test image to the QA engineer.

Usage

  1. Connect the GPIO jumper wire as instructed, and boot the system.

  2. The device will power on normally. Once it reaches the Linux kernel, the LED should be heartbeating: quick 2 blinks then after some delay, repeat.

  3. The stress service will then start after the system is fully booted. It will change the light pattern in 2 ways:

    • Off: This indicates the stress test has failed to start. Please contact for support.
    • Switching at 0.5s interval: This indicates the stress is running.

  4. Disconnect the GPIO jumper wire. The device status can be checked in a few hours.

Final LED status

  • Switching at 0.5s interval: This indicates the stress is running. PASS
  • On: This indicates the system was locked up and unable to reboot. FAIL
  • Off: Either the system was locked up and unable to reboot, or the device rebooted. FAIL