mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: barebox-bringup utility
Date: Mon, 5 Jan 2026 15:40:55 +0100	[thread overview]
Message-ID: <7bf80d43-af4b-4cfa-b341-615a519ad55d@pengutronix.de> (raw)
In-Reply-To: <aVvF7LW9-lAvPTuZ@pengutronix.de>

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?
> 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.

> and to accept input from a
> fifo.

Untested, but should be possible with mkfifo and redirection?

> 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.

> This loses output though, as the console is only started after barebox
> has already started, so I usually had running a permanent console on
> another terminal.
> 
> Maybe there are ways to improve the barebox pytest or to improve labgrid
> itself, but in the meantime somebody might find this useful as well.

I already rewrote my perl tool in python, so it's more approachable to
others. It would be cool if missing features are implemented there, so
everyone can use it.

Cheers,
Ahmad

> 
> 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 |




  reply	other threads:[~2026-01-05 14:41 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 [this message]
2026-01-06  7:11   ` Sascha Hauer

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=7bf80d43-af4b-4cfa-b341-615a519ad55d@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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