diff options
| -rw-r--r-- | docs/getting-started/app-workflow-bootables.md | 7 | ||||
| -rw-r--r-- | docs/getting-started/machines/qemu.md | 19 |
2 files changed, 20 insertions, 6 deletions
diff --git a/docs/getting-started/app-workflow-bootables.md b/docs/getting-started/app-workflow-bootables.md index 508ff7a..86f57bc 100644 --- a/docs/getting-started/app-workflow-bootables.md +++ b/docs/getting-started/app-workflow-bootables.md @@ -9,14 +9,11 @@ The following list overviews the process. 1. Insert your media into the appropriate build host interface (e.g. USB port). 2. Determine the device name of your portable media (e.g. ``sdb``). -3. Download the ``mkefi-agl.sh`` script. -4. Check your available script options. -5. Use ``mkefi-agl.sh`` to create your media. +3. Write out the image using e.g. ``etcher`` , ``bmaptool`` or ``dd``. You can detailed steps for creating bootable images for several types of images in the following sections: -* "[Create a bootable media](./machines/intel.html#3-creating-bootable-media)" for most Intel boards * "[Deploying the AGL Demo Image](./machines/qemu.html#3-deploying-the-agl-demo-image)" for emulation images * "[Booting the Image Using a MicroSD Card](./machines/renesas.html#7-booting-the-image-using-a-microsd-card) for supported Renesas boards -* "[Booting the Image on Raspberry Pi](./machines/raspberrypi.html#2-booting-the-image-on-raspberrypi) for Raspberry Pi 2 and 3 boards +* "[Booting the Image on Raspberry Pi](./machines/raspberrypi.html#2-booting-the-image-on-raspberrypi) for Raspberry Pi 4 board diff --git a/docs/getting-started/machines/qemu.md b/docs/getting-started/machines/qemu.md index e7b7c77..af8d91e 100644 --- a/docs/getting-started/machines/qemu.md +++ b/docs/getting-started/machines/qemu.md @@ -56,9 +56,22 @@ For this example, the target is "agl-demo-platform": By default, the build process puts the resulting image in the Build Directory: ``` +<build_directory>/tmp/deploy/images/qemux86-64/ + +e.g. + <build_directory>/tmp/deploy/images/qemux86-64/agl-demo-platform-qemux86-64.vmdk.xz ``` +**Note:** + +If you built your image with bitbake, you can now just use the ``runqemu`` wrapper. + +**Note:** +If you need to run it outside of the bitbake environment or need special settings for +hardware pass-through or the like, read on: + + ## 3. Deploying the AGL Demo Image Deploying the image consists of decompressing the image and then @@ -88,7 +101,11 @@ Depending on your Linux distribution, use these commands to install QEMU: **NOTE:** if you have created an AGL crosssdk, it will contain a QEMU binary for the build host. This SDK QEMU binary does not support graphics. -Consequently, you cannot use it to boot the AGL image. +Consequently, you cannot use it to boot the AGL image and +need to call your host's qemu binary instead. + +**NOTE:** the VM images need UEFI in the emulator to boot. Thus you need +to install the necessary files with below commands (ovmf). If your build host is running [Arch Linux](https://www.archlinux.org/), use the following commands: |