mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/2] test: arm: describe Qemu Raspberry Pi 3b labgrid environment
Date: Tue, 11 Jun 2024 08:58:11 +0200	[thread overview]
Message-ID: <20240611065811.2900029-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240611065811.2900029-1-a.fatoum@pengutronix.de>

The Raspberry Pi 3b has multiple non-secure UARTs, which can be useful
for debugging.

The existing Qemu ARM64 Virt platform can already gain multiple UARTs
via virtio, but PL011/8250 UARTs may be easier to use from secure monitors
or EFI runtime services.

The second console can be connected to with:

  microcom -t localhost:2302

But requires the Bluetooth serdev node to be removed manually for now.

All tests run successfully, but the default heartbeat throws errors,
presumably, because the VideoCore firmware used with Qemu doesn't
implement GPIO control as expected by the gpio-raspberrypi-exp driver
used for heartbeat. This doesn't bother us in CI and can be solved
later on though.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 test/arm/qemu-raspi3b@multi_v8_defconfig.yaml | 20 +++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 test/arm/qemu-raspi3b@multi_v8_defconfig.yaml

diff --git a/test/arm/qemu-raspi3b@multi_v8_defconfig.yaml b/test/arm/qemu-raspi3b@multi_v8_defconfig.yaml
new file mode 100644
index 000000000000..4f591ba21596
--- /dev/null
+++ b/test/arm/qemu-raspi3b@multi_v8_defconfig.yaml
@@ -0,0 +1,20 @@
+targets:
+  main:
+    drivers:
+      QEMUDriver:
+        qemu_bin: qemu-system-aarch64
+        machine: raspi3b
+        cpu: cortex-a53
+        memory: 1G
+        kernel: barebox-raspberry-pi.img
+        extra_args: "\
+          -serial chardev:serial2 \
+          -chardev socket,id=serial2,host=localhost,port=2302,nodelay=on,server=on,wait=off"
+      BareboxDriver:
+        prompt: 'barebox@[^:]+:[^ ]+ '
+        bootstring: 'commandline:'
+      BareboxTestStrategy: {}
+images:
+  barebox-raspberry-pi.img: !template "$LG_BUILDDIR/images/barebox-raspberry-pi.img"
+imports:
+  -  ../strategy.py
-- 
2.39.2




  reply	other threads:[~2024-06-11  6:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  6:58 [PATCH 1/2] watchdog: bcm2835: add support for powering off SoC Ahmad Fatoum
2024-06-11  6:58 ` Ahmad Fatoum [this message]
2024-06-13  7:22 ` 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=20240611065811.2900029-2-a.fatoum@pengutronix.de \
    --to=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