cheatsheet.md: Re-write QEMU invocation example
The commandline provided had several issues:
* The -dtb option was redundant as we boot with the cuImage, and caused
some kernel configuration to be skipped which in turn ended in a
kernel panic
* -append argument was redundant with respect to the devicetree
* The file paths used typically required the user to change up out of
the build directory after bitbaking obmc-phosphor-image
The patch addresses all of the above.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
diff --git a/cheatsheet.md b/cheatsheet.md
index 4e2c8f5..f51522c 100644
--- a/cheatsheet.md
+++ b/cheatsheet.md
@@ -91,18 +91,16 @@
QEMU's wiki has instructions for [building from
source](http://wiki.qemu.org/Documentation/GettingStartedDevelopers).
-Assuming the CWD is the root of the openbmc tree, a palmetto-bmc machine can be
-invoked with:
+Assuming the current working directory is the `build` directory (from sourcing
+`oe-init-build-env`), a palmetto-bmc machine can be invoked with:
```
qemu-system-arm \
-M palmetto-bmc \
-m 256 \
- -append "console=ttyS4" \
-nographic \
- -kernel build/tmp/deploy/images/palmetto/cuImage-palmetto.bin \
- -dtb build/tmp/deploy/images/palmetto/cuImage-aspeed-bmc-opp-palmetto.dtb \
- -initrd build/tmp/deploy/images/palmetto/obmc-phosphor-image-palmetto.cpio.gz
+ -kernel tmp/deploy/images/palmetto/cuImage-palmetto.bin \
+ -initrd tmp/deploy/images/palmetto/obmc-phosphor-image-palmetto.cpio.gz
```
To quit, type `Ctrl-a c` to switch to the QEMU monitor, and then `quit` to exit.