diff options
author | Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> | 2023-10-31 08:49:35 -0600 |
---|---|---|
committer | Mark Hatle <mark.hatle@amd.com> | 2023-11-01 16:09:55 -0500 |
commit | a1ce9c028b4316643a99a64b93523dae85ebe40c (patch) | |
tree | d0b547fa956ef81177e2560328400f01888fbe88 /README.booting.md | |
parent | dbcc3152592f2677c7d73054ca57645199cddc81 (diff) | |
download | meta-xilinx-a1ce9c028b4316643a99a64b93523dae85ebe40c.tar.gz |
README.booting.md: Update boot instructions using slirp mode
Update boot instructions using slirp mode when tap devices are not
configured.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Diffstat (limited to 'README.booting.md')
-rw-r--r-- | README.booting.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/README.booting.md b/README.booting.md index 0f96a138..a632d7f9 100644 --- a/README.booting.md +++ b/README.booting.md | |||
@@ -5,10 +5,22 @@ AMD Xilinx Devices support different boot modes such as JTAG, SD, eMMC, QSPI etc | |||
5 | ## Booting Images with QEMU | 5 | ## Booting Images with QEMU |
6 | 6 | ||
7 | Once images are built, you can simulate the image using QEMU emulator. | 7 | Once images are built, you can simulate the image using QEMU emulator. |
8 | |||
9 | > **Note:** Use `slirp` option if you don't have sudo permissions and tap devices | ||
10 | are enabled on your build host. | ||
11 | |||
12 | * Without slirp | ||
8 | ``` | 13 | ``` |
9 | $ MACHINE=<target_mahcine_name> runqemu nographic | 14 | $ MACHINE=<target_mahcine_name> runqemu nographic |
10 | ``` | 15 | ``` |
11 | 16 | ||
17 | * With slirp | ||
18 | ``` | ||
19 | $ MACHINE=<target_mahcine_name> runqemu nographic slirp | ||
20 | ``` | ||
21 | |||
22 | > **Note:** To terminate qemu, usually the command is ctrl-a x | ||
23 | |||
12 | ## Booting Images with Hardware | 24 | ## Booting Images with Hardware |
13 | 25 | ||
14 | Follow booting instructions [README](docs) for more details. | 26 | Follow booting instructions [README](docs) for more details. |