i.MX 8M Plus Starter Kit Torizon Software QA Test Plan
- 1 1. Purpose
- 2 2. Board Preparations
- 3 3. QA Tests
- 3.1 3.1. SD Installation and Booting Test
- 3.2 3.2. Ethernet Test
- 3.3 3.3. USB Flash Test
- 3.4 3.4. WiFi Test
- 3.5 3.5. HDMI Test
- 3.6 3.6. BlueTooth Test
- 3.7 3.7. Empty eMMC Boot Time Test
- 3.8 3.8. eMMC Installation and Booting Test
- 3.9 3.9. USB2-only Power Test
- 3.10 3.10. USB1 Host Mode Test
- 3.11 3.11. USB1 Device Mode Test
- 3.12 3.12. USB2 Device Mode Test
- 3.13 3.13. RoyaleViewer/Qt Test
- 3.14 3.14. MIPI Cameras Test
- 3.15 3.15. SLAM/Flexx2 Tests
- 3.16 3.16. Torizon Cloud Test
- 3.17 3.17. Torizon OS docker container Test
- 3.18 3.18. Torizon OS OTA Test
1. Purpose
This document provides a description of the QA tests used for validation of i.MX 8M Plus Starter Kit weekly engineering builds and release builds.
2. Board Preparations
Connect to the board (see Setting up the i.MX 8M Plus SOM Starter Kit ):
Ethernet cable
WiFi antenna
USB hub, with USB keyboard and mouse attached, into the
USB1
connector.HDMI monitor
3. QA Tests
3.1. SD Installation and Booting Test
Install release image to SD card, as per TBD .
Boot to shell prompt using SD card, measure boot time (~25 seconds).
3.2. Ethernet Test
Check that internet access is configured automatically.
Run
ping google.com
.
3.3. USB Flash Test
Insert USB Flash to USB hub. Run “lsblk”. Make sure
/dev/sda
and/dev/sda1
are present:user@imx8mpnavq:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 28.9G 0 disk └─sda1 8:1 1 28.9G 0 part /media/user/BEF4-F228 ...
3.4. WiFi Test
Unplug Ethernet cable.
Configure and test WiFi as per Setting up Wi-Fi.
3.5. HDMI Test
Check that Torizon Splash image is displayed on HDMI monitor when booting.
3.6. BlueTooth Test
1. TBD: setup bluetooth in Torizon OS
Power on a Bluetooth device in the vicinity, validate that the target detects it:
user@imx8mpnavq:/home/user# sudo hcitool scan Scanning ... 50:1A:A5:E5:34:8A JABRA BT2045 F0:F6:1C:67:F4:D4 iPhone yur
Power on a BLE device in the vicinity, validate that the target detects it:
user@imx8mpnavq:/home/user# sudo hcitool lescan LE Scan ... 14:BB:6E:2F:9B:07 (unknown) ^C
3.7. Empty eMMC Boot Time Test
TBD: add support for booting Torizon OS from SD card (NAVQP-237)
Make sure the system is booted from SD card.
Remove partition table from eMMC:
$ sudo dd if=/dev/zero of=/dev/mmcblk2 bs=8M count=100 conv=fdatasync
Reboot and check boot time is about ~25 seconds
$ sudo reboot
3.8. eMMC Installation and Booting Test
Install images to eMMC as per Installing Torizon OS to i.MX 8MPlus NAVQ+ Target
Repeat Ethernet, WiFi and HDMI tests while booting from eMMC.
3.9. USB2-only Power Test
Disconnect all cables (except serial debug) to power off the board.
Use Type-C to Type-C cable and plug it into NAVQ Plus USB2 Type-C (closer to center) and a Laptop with Type-C port.
Validate that the NAVQ Plus boots to login prompt normally (no boot loop).
Use Type-A to Type-C cable and plug it into NAVQ Plus USB2 Type-C (closer to center) and a Laptop/Desktop with Type-A port.
Validate that the NAVQ Plus boots to login prompt normally (no boot loop).
3.10. USB1 Host Mode Test
Plug-in a USB hub into USB1.
Power Up device via USB2.
Plug-in a USB device into the hub.
Verify that the plugged-in device is enumerated (via dmesg).
3.11. USB1 Device Mode Test
Disconnect the cable from USB1.
Reboot the board
Run usb-gadget-mtp1 service:
user@imx8mpnavq:~$ sudo systemctl start usb-gadget-mtp@38100000.usb [sudo] password for user: user@imx8mpnavq:~$
Connect the USB1 to a desktop host.
Verify that the host recognized NAVQ Plus as an MTP (“NavqPlus” device is shown in the Windows Explorer).
3.12. USB2 Device Mode Test
Power up device using USB1 port
Run usb-gadget-mtp2 service:
# Stop the Ethernet gadget on USB2, enabled by default in imx-image-desktop-ros image. user@imx8mpnavq:~$ sudo systemctl stop usb-gadget-eth@38200000.usb [sudo] password for user: ... user@imx8mpnavq:~$ sudo systemctl start usb-gadget-mtp@38200000.usb user@imx8mpnavq:~$
Connect the USB2 to a desktop host/laptop.
Verify that the host/laptop recognized NAVQ Plus as an MTP.
Restore back USB Ethernet gadget on USB2 (or just do “sudo reboot” instead):
user@imx8mpnavq:~$ sudo systemctl stop usb-gadget-mtp@38200000.usb [sudo] password for user: user@imx8mpnavq:~$ sudo systemctl start usb-gadget-eth@38200000.usb
3.13. RoyaleViewer/Qt Test
Make sure HDMI display and USB Mouse are connected to the kit.
Copy the test file https://emcraft.com/misc/test.rrf to a USB Flash. Insert the USB Flash into the kit.
From the shell prompt, on the serial console, run PMD RoyaleViewer:
user@imx8mpnavq:~$ royaleviewer.sh ...
On the HDMI display, navigate to “Tools” → “Load File” and load the test file.
Verify that RoyaleViewer plays the saved frames correctly.
3.14. MIPI Cameras Test
Verify the camera functionality as per the respective application notes:
Using Emcraft OV5640 Camera
3.15. SLAM/Flexx2 Tests
Follow instruction in the following AN documents for verifying SLAM and object avoidance functionality:
Enhanced Object Avoidance in SLAM Using PMD USB Flexx2 Camera
3.16. Torizon Cloud Test
Follow instruction in the following AN documents for verifying SLAM and object avoidance functionality:
Accessing i.MX 8MPlus NAVQ+ Targets from the Torizon Cloud
3.17. Torizon OS docker container Test
Follow instruction in the following AN documents for verifying SLAM and object avoidance functionality:
Running Docker Containers in Torizon OS on the i.MX 8MPlus NAVQ+ Board
3.18. Torizon OS OTA Test
Follow instruction in the following AN documents for verifying SLAM and object avoidance functionality:
Updating Torizon OS on i.MX 8MP Target from the Torizon Cloud