Explain how to run the FVP model in more detail. Fix README.md bugs and make it look better.
Signed-off-by: Pawel Zalewski pzalewski@thegoodpenguin.co.uk --- README.md | 54 ++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 38 insertions(+), 16 deletions(-)
diff --git a/README.md b/README.md index 717c83e..f3f35a4 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,11 @@ meta-morello -============== +============
Meta-morello provides the layer required to build the firmware that lives on the SD card and a `Morello` enabled `Linux` kernel for the Morello System Development Platform.
-- Use the provided `kas` scripts to get all of the dependencies. -- Read on how to get and use `kas` here [1] +- Use the provided `kas` scripts to get all of the dependencies. +- Read on how to get and use `kas` here [1]
Booting the hardware -------------------- @@ -20,28 +20,50 @@ The machines have been split into: - morello-fvp for running a `FVP` image using `runfvp` script @ `meta-arm`
Building images --------------------- - -kas build ./kas/morello-soc.yml +---------------
+``` +$ kas build ./kas/morello-soc.yml +``` or - -kas build ./kas/morello-fvp.yml - +``` +$ kas build ./kas/morello-fvp.yml +``` FVP ---
-For instructions on how to run the image with `FVP` go here [4] +To run the FVP model: +``` +$ cd poky +$ . oe-init-build-env ../build +$ ./../meta-arm/scripts/runfvp --console tmp-fvp/deploy/images/morello-fvp/rootfs-morello-fvp.fvpconf +``` +or +``` +$ cd poky +$ . oe-init-build-env ../build +$ ./../meta-arm/scripts/runfvp tmp-fvp/deploy/images/morello-fvp/rootfs-morello-fvp.fvpconf +``` +Then inspect the FVP console output for information on your uart_ap port: +``` +$ terminal_uart_ap: Listening for serial connection on port 5003 +``` +With that knowledge you can now run: +``` +$ telnet localhost 5003 +``` +For further instructions on how to run the image with `FVP` go here [4]
Images ------
The outputs can be found under build/temp/deploy/images: -- board-firmware-sd-image.img goes on the SD card via DD -- morello-linux-image..img goes on the USB via DD +- board-firmware-sd-image.img goes on the SD card via DD +- morello-linux-image..img goes on the USB via DD
Linux and musl-libc ------------------- + The linux kernel and musl-libc are locked in sync so that the release tags from upstream always match.
@@ -70,7 +92,7 @@ https://op-lists.linaro.org/mailman3/lists/linux-morello-distros.op-lists.li... References ----------
-[1] https://kas.readthedocs.io/en/latest/ \ -[2] https://developer.arm.com/documentation/den0132/0100/Setting-up-the-Morello-... \ -[3] https://developer.arm.com/documentation/102278/0001/?lang=en -[4] https://github.com/jonmason/meta-arm/blob/master/documentation/runfvp.md \ No newline at end of file +[1] https://kas.readthedocs.io/en/latest/ +[2] https://developer.arm.com/documentation/den0132/0100/Setting-up-the-Morello-... +[3] https://developer.arm.com/documentation/102278/0001/?lang=en +[4] https://github.com/jonmason/meta-arm/blob/master/documentation/runfvp.md \ No newline at end of file