On Tue, 2019-01-08 at 21:05 +0000, Milosz Wasilewski wrote:
On Tue, 8 Jan 2019 at 19:36, Diego Russo Diego.Russo@arm.com wrote:
Hello LAVA mailing list,
I see RPI3 is supported by LAVA but unfortunately it doesn't fit Mbed Linux OS (MBL) case. Our build system produces a WIC image which can be written on the SD card directly (instructions here: https://os.mbed.com/docs/linux-os/v0.5/getting-started/writing-and-booting-t... ). This is needed for two main reasons:
- MBL has its own booting flow
- MBL expects a partition layout (not only the rootfs) with
multiple partitions in order to work.
What's the best way to automate the deployment on MBL on RPI3 via LAVA in order to run our tests?
I'd say there isn't any if you can't deliver your software to the board without manual operation (preparing SD card using host PC). You could try some sort of SDMux (for example this: https://wiki.tizen.org/MuxPi or this: https://wiki.tizen.org/SDWire) but from my experience they don't work. I didn't check them with RPi though, so there is some small chance of success :)
What we do on various board where we have a similar use-case is to split the lava test in esentially two stages: * network boot the system and flash the sd card (using deploy to secnodary media with a custom writer) * then boot into the sd card image and run the tests
See https://lava.collabora.co.uk/scheduler/job/1419582/definition for a practical example how we do this.
What this does require is that the bootloader isn't overwritten if you flash an image e.g. to be in a seperate flash/emmc hardware parittion/on the network
For the raspberry pi 3 you can enable network boot for this purpose: https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmods/net_...