Bootloader testing in LAVA
summary
LAVA now supports Interactive testing that sends typed commands to a bootloader console, matches expected success and failure strings, and records named results; a new flasher method plus the hardware mux SD-wire lets a dispatcher remotely DD images to an SD card and swap it into the DUT. Demo runs on Raspberry Pi find an actual bootloader crash, showing the system works but requires board-level recovery paths, stable console output, unique device IDs or USB-by-path workarounds, and comprehensive expected-string lists.
AI-written summary · about
chapters (9)
- 0:00Introduction to LAVA
- 1:01Why test bootloaders
- 2:51What is LAVA and how it works
- 10:24Challenges testing bootloaders
- 12:10Solutions for bootloader testing
- 13:14Provisioning with SD wire
- 14:40Interactive testing in LAVA
- 20:41Hardware boot media options
- 22:29Summary and Q&A
related talks
56mLAVA for LITE Platforms and Tests
42mLAVA on your desk BoF
55mBest practices for getting devices in LAVA
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
45mUpdate on LAVA Testing for bare metal systems
44mAutomation beyond Testing and Embedded System Validation
41mTesting with Volcanoes - Fuego+LAVA Going Distributed
34mFrom Zero to First Test in Your Own LAVA Laboratory in less than 45 minutes)