From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: barebox-bringup utility
Date: Tue, 6 Jan 2026 08:11:16 +0100 [thread overview]
Message-ID: <aVy1lFT-kNasbH3h@pengutronix.de> (raw)
In-Reply-To: <7bf80d43-af4b-4cfa-b341-615a519ad55d@pengutronix.de>
On Mon, Jan 05, 2026 at 03:40:55PM +0100, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 1/5/26 3:08 PM, Sascha Hauer wrote:
> > Hi,
> >
> > Claude Code struggles to to bring up barebox properly with
> > labgrid-pytest and running barebox on real hardware with the barebox
> > integrated pytest infrastructure is also not easy as there are several
> > assumptions about QEMU in it.
>
> We have a container to address this.
>
> > I thought letting Claude write a small
> > python tool to start barebox in QEMU. It turned out to be useful for
> > interactive usage as well, so here it is:
> >
> > https://github.com/saschahauer/barebox-bringup
> >
> > It makes starting barebox as easy as:
> >
> > barebox-bringup -c ~/test/arm/imx6s-riotboard.yaml
> > barebox-bringup -c test/arm/virt@multi_v7_defconfig.yaml
>
> Does
>
> ./scripts/container.sh pytest --interactive \
> --lg-env test/arm/virt@multi_v8_defconfig.yaml
>
> not work for you?
No, I don't have podman installed.
However, labgrid-pytest --lg-env test/arm/virt@multi_v8_defconfig.yaml
--interactive works
> > It will open a console which captures the barebox output from the start.
> > The tool has options to capture to a log file
>
> This can be achieved with --lg-log when using pytest.
With --lg-log a logfile is created, but it's empty.
With output redirection to a file I get pytest output, but not the console.
Maybe that's different when using ./scripts/container.sh instead of
labgrid-pytest.
>
> > and to accept input from a
> > fifo.
>
> Untested, but should be possible with mkfifo and redirection?
Likely, yes.
>
> > At least with real hardware the closest I could get was:
> >
> > labgrid-client -c ~/test/arm/imx6s-riotboard.yaml -s barebox console
>
> By the way, I think we should start adding YAMLs for real hardware as
> well into the repository.
How do we accomplish this? The YAML files contain many site specific
details, like RemotePlace name, coordinator_address, which PowerDriver,
wether to use a USB loader, SD-MUX or JTAG for bringup. There's not much
left that is generic.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2026-01-06 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 14:08 Sascha Hauer
2026-01-05 14:40 ` Ahmad Fatoum
2026-01-06 7:11 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aVy1lFT-kNasbH3h@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox