All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH  0/6] Basic skeleton of RP2040 Raspbery Pi Pico
Date: Mon, 10 Jan 2022 17:50:58 +0000	[thread overview]
Message-ID: <20220110175104.2908956-1-alex.bennee@linaro.org> (raw)

Hi,

This is a rather incomplete and basic model of the Pico Pi that I
hacked up over the Christmas break. It took me a bit of faffing about
to get it up and running but as it stands it will now run the first
few hundred instructions of the RP2040 mask ROM before looping waiting
for CLK_SYS_SELECTED to update (which it never will as it is currently
unimplemented).

I don't know when I'll next get a chance to hack on it but I thought
it was worth posting as a reference. If anyone has an inclination to
take it further then at least the initial baby steps are done for you.

There is no rush to review this although I am curious if anyone has
comments about how the model is put together.

It uses -kernel to load the user program (although it never gets there
at the moment):

 qemu-system-arm -d unimp,guest_errors -M raspi-pico \
   --kernel ~/mysrc/pico-air.rust/pico-air.git/target/thumbv6m-none-eabi/debug/rp2040-project-template \
   -display none -serial mon:stdio 

Alex Bennée (6):
  hw/arm: arm initial boilerplate for RP2040 SoC
  hw/arm: add boilerplate for machines based on the RP2040
  hw/arm: wire-up memory from the Pico board and the SoC
  pc-bios: add pipico mask rom (!upstream)
  hw/arm: add mask boot ROM logic
  docs/devel: add some clarifying text for aliases

 docs/devel/memory.rst                   |  14 +-
 configs/devices/arm-softmmu/default.mak |   2 +
 include/hw/arm/rp2040.h                 |  39 +++++
 hw/arm/raspi_pico.c                     |  97 ++++++++++++
 hw/arm/rp2040.c                         | 201 ++++++++++++++++++++++++
 hw/arm/Kconfig                          |   6 +
 hw/arm/meson.build                      |   2 +
 pc-bios/pipico.rom                      | Bin 0 -> 16384 bytes
 8 files changed, 356 insertions(+), 5 deletions(-)
 create mode 100644 include/hw/arm/rp2040.h
 create mode 100644 hw/arm/raspi_pico.c
 create mode 100644 hw/arm/rp2040.c
 create mode 100644 pc-bios/pipico.rom

-- 
2.30.2



             reply	other threads:[~2022-01-10 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:50 Alex Bennée [this message]
2022-01-10 17:50 ` [RFC PATCH 1/6] hw/arm: arm initial boilerplate for RP2040 SoC Alex Bennée
2022-01-17 12:21   ` Philippe Mathieu-Daudé via
2022-01-10 17:51 ` [RFC PATCH 2/6] hw/arm: add boilerplate for machines based on the RP2040 Alex Bennée
2022-01-17 12:23   ` Philippe Mathieu-Daudé via
2022-01-10 17:51 ` [RFC PATCH 3/6] hw/arm: wire-up memory from the Pico board and the SoC Alex Bennée
2022-01-17 12:27   ` Philippe Mathieu-Daudé via
2022-01-10 17:51 ` [RFC PATCH 4/6] pc-bios: add pipico mask rom (!upstream) Alex Bennée
2022-01-10 17:51 ` [RFC PATCH 5/6] hw/arm: add mask boot ROM logic Alex Bennée
2022-01-10 17:51 ` [RFC PATCH 6/6] docs/devel: add some clarifying text for aliases Alex Bennée
2022-01-17 12:29   ` Philippe Mathieu-Daudé via
2022-01-18  7:28   ` Philippe Mathieu-Daudé via

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=20220110175104.2908956-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.