aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2023-04-02 22:12:29 +0100
committerMarc Zyngier <maz@kernel.org>2023-04-02 22:12:29 +0100
commit1b50c381d4dc803bf5565c2c1f8f311640deb029 (patch)
tree99edb48c45fa4def3edd8af8b9330e37e6350b56
parent79a82a16c1e1df080a963d73d107c3b61ce6b5fe (diff)
downloadcs-sw-1b50c381d4dc803bf5565c2c1f8f311640deb029.tar.gz
README updatedual-port
Signed-off-by: Marc Zyngier <maz@kernel.org>
-rw-r--r--README.txt12
1 files changed, 10 insertions, 2 deletions
diff --git a/README.txt b/README.txt
index 57aaf74..a7ac2c3 100644
--- a/README.txt
+++ b/README.txt
@@ -4,6 +4,11 @@ So you have built (or otherwise obtained) a device labelled "Central
Scrutinizer" which allows you interact with the serial port of a M1/M2
and reboot it.
+Otherwise, you can look at
+https://git.kernel.org/pub/scm/linux/kernel/git/maz/cs-hw.git
+for the hardware side of the project. Everything in this file
+assumes that the board is assembled and functionnal.
+
This file describe how to build the software and flash it onto the
Raspberry-Pi Pico that controls the adapter. As for the HW, the SW
started its life as m1-ubmc, but let's be clear that its name really
@@ -29,8 +34,7 @@ to use anything else.
** Install the pico-sdk:
-I've mostly used version 1.4 of the SDK, but 1.5 seems to work
-too. YMMV.
+I've used versions 1.4 and 1.5 of the SDK. YMMV.
git clone -b master https://github.com/raspberrypi/pico-sdk.git
@@ -103,6 +107,10 @@ Models I know of:
No idea about other machines.
+Optionally, you can make use of the micro-USB connector that is on
+the other side of the board. It's main use it to allow interacting
+with the Asahi m1n1 firmware, such as tethered booting.
+
** Use it
If you have correctly built and flashed the firmware, you will have