Merge remote-tracking branch 'origin/master-next'

Change-Id: Ifda0fa9a9940d056f72bcad0ea94821face3685d

1 files changed, 22 insertions, 0 deletions

diff --git a/docs/getting-started/app-workflow-bootables.md b/docs/getting-started/app-workflow-bootables.md
new file mode 100644
index 0000000..508ff7a
--- /dev/null
+++ b/docs/getting-started/app-workflow-bootables.md
@@ -0,0 +1,22 @@
+# 3. Create Bootable Media #
+
+In order to test an application, your device must be running the image and, of course,
+the application.
+To run the image, you need to create a bootable image that can be launched
+from an external device such as an SD card or USB stick.
+
+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.
+
+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