[PATCH v2 6/8] [RFC] CI: add U-Boot testing on real HW with tbot
Simon Glass
sjg at chromium.org
Sat Apr 5 22:46:34 CEST 2025
Hi Heiko,
On Sun, 6 Apr 2025 at 07:06, Heiko Schocher <hs at denx.de> wrote:
>
> From: Heiko Schocher <hs at nabladev.com>
>
> add U-Boot tests on real hardware with tbot, which is started
> from gitlab CI (no idea where it runs).
>
> Currently one board is implemented (imx8qxp based cxg3 board).
>
> This is a good example, as we need to get some binary blobs
> for the build to get a working bootloader binary. This blobs
> are stored in the tftp directory on the lab host, to which the
> hardware is connected to. Tbot copies them from the lab host
> to the CI host.
>
> After build has finished, tbot copies the resulting bootloader
> binaries to the lab host where with, the help of USB SDP bootmode
> and uuu tool, the new flash.bin image is booted, and with USB
> fastboot mode flashed into the emmc. After that worked, bootmode
> is switched to emmc and the new flash.bin gets bootet (and tbot
> checks the bootmode output, so we can be sure, that really the
> new image boots from the correct bootdevice). A simple tbot
> testcase for a ping over ethernet is done and ut command is called.
>
> After that the test/py framework is started (from the CI host),
> no external scripts are necessary for this, as all "scripts"
> needed for this framework are created from tbot at runtime.
>
> Signed-off-by: Heiko Schocher <hs at nabladev.com>
> ---
Thanks for sending this! I hope it will help with Tom's setup and get
some of his boards into CI.
Regards,
Simon
More information about the U-Boot
mailing list