docs: Add README for booting instructions for all devices

Add README for booting instructions for all devices with supported
boot mediums.

Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>

6 files changed, 1008 insertions, 0 deletions

diff --git a/docs/README.booting.flash.md b/docs/README.booting.flash.md
new file mode 100644
index 00000000..3bc39882
--- /dev/null
+++ b/docs/README.booting.flash.md
@@ -0,0 +1,133 @@
+# Booting OS Images from Flash Device 
+
+Booting OS Images from flash devices such as QSPI/NOR/NAND/OSPI.
+
+* [U-boot boot scripts configurations](#u-boot-boot-scripts-configurations)
+* [Booting from QSPI or NOR or OSPI](#booting-from-qspi-or-nor-or-ospi)
+
+## U-boot boot scripts configurations
+
+1. In QSPI/OSPI/NAND boot modes the boot.scr partition offset is fixed for all the
+   platforms by default in u-boot, and you can change by updating 
+   CONFIG_BOOT_SCRIPT_OFFSET in u-boot config. Default boot script size is 
+   512KB(script_size_f=0x80000). 
+2. Below table describes boot.scr partition offset and load address for all the
+   platforms.
+
+| Device     | Partition Offset address for boot.scr | Load address of boot.scr in DDR        |
+|------------|---------------------------------------|----------------------------------------|
+| MicroBlaze | 0x1F00000                             | DDR base address + DDR Size - 0xe00000 |
+| Zynq-7000  | 0xFC0000                              | DDR base address + 0x3000000           |
+| ZynqMP     | 0x3E80000                             | DDR base address + 0x20000000          |
+| Versal     | 0x7F80000                             | DDR base address + 0x20000000          |
+
+## Booting from QSPI or NOR or OSPI
+
+This section demonstrates the booting OS images from QSPI boot mode. For this, 
+you need to make sure you have QSPI interface on board or a QSPI daughter card.
+
+> **Note:** Instructions are same for QSPI or NOR and OSPI flash.
+
+1. For example we'll assume QSPI flash size is 128MB and default CONFIG_BOOT_SCRIPT_OFFSET
+   defined in u-boot.
+
+| Flash Partition Name | Partition Offset | Partition Size |
+|----------------------|------------------|----------------|
+| boot.bin             | 0x0              | 30MB           |
+| bootenv              | 0x1E00000        | 256Kb          |
+| kernel               | 0x1E40000        | 33MB           |
+| bootscr              | 0x3E80000        | 1.5MB          |
+| rootfs               | 0x4000000        | 64MB           |
+
+2. Create a flash partition device-tree nodes depending on your flash size. ex:
+```
+&qspi {
+        #address-cells = <1>;
+        #size-cells = <0>;
+        flash0: flash@0 {
+                spi-tx-bus-width=<4>;
+                spi-rx-bus-width=<4>;
+                partition@0 {
+                        label = "boot";
+                        reg = <0x00000000 0x01e00000>;
+                };
+                partition@1 {
+                        label = "bootenv";
+                        reg = <0x01e00000 0x00040000>;
+                };
+                partition@2 {
+                        label = "kernel";
+                        reg = <0x01e40000 0x02040000>;
+                };
+                partition@3 {
+                        label = "bootscr";
+                        reg = <0x03e80000 0x01800000>;
+                };
+                partition@4 {
+                        label = "rootfs";
+                        reg = <0x04000000 0x04000000>;
+                };
+        };
+};
+```
+3. Set the U-boot boot script variables to match the flash partition offsets in
+   local.conf
+```
+QSPI_KERNEL_OFFSET = "0x1E40000"
+QSPI_KERNEL_SIZE = "0x2040000"
+QSPI_RAMDISK_OFFSET = "0x4000000"
+QSPI_RAMDISK_SIZE = "0x4000000"
+```
+4. Build the images and make sure images are copied to tftp directory.
+5. Once images are built, to ensure taget is booted using JTAG or SD boot modes.
+6. Also have boot.bin copied to DDR location using XSCT `dow` or `tftpboot` or 
+   `fatload` command.
+7. Halt at U-Boot then run the following commands to flash the images on the
+   QSPI flash.
+```
+# check QSPI is available or not
+U-Boot> sf probe 0 0 0
+
+# Erase the boot partition
+U-Boot> sf erase 0x0 0x1E00000
+
+# Copy the boot.bin to DDR location using tftpboot
+U-Boot> tftpboot 0x10000000 ${TFTPDIR}/boot.bin
+
+# Write boot.bin file image to flash partition
+U-Boot> sf write 0x10000000 0x0 ${filesize}
+
+# Erase the bootenv partition for env storage (saveenv).
+U-Boot> sf erase 0x1E00000 0x1E40000
+
+# Erase the kernel partition
+U-Boot> sf erase 0x1E40000 0x2040000
+
+# Copy the Image file to DDR location using tftpboot
+U-Boot> tftpboot 0x10000000 ${TFTPDIR}/Image
+
+# Write kernel image to flash partition
+U-Boot> sf write 0x10000000 0x1E40000 ${filesize}
+
+# Erase the bootscr partition
+U-Boot> sf erase 0x3E80000 0x1800000
+
+# Copy the boot.scr file to DDR location using tftpboot
+U-Boot> tftpboot 0x10000000 ${TFTPDIR}/boot.scr
+
+# Write boot.scr file to flash partition
+U-Boot> sf write 0x10000000 0x3E80000 ${filesize}
+
+# Erase the rootfs partition
+U-Boot> sf erase 0x4000000 0x4000000
+
+# Copy the rootfs.cpio.gz.u-boot file to DDR location using tftpboot
+U-Boot> tftpboot 0x10000000 ${TFTPDIR}/rootfs.cpio.gz.u-boot
+
+# Write rootfs image to flash partition
+U-Boot> sf write 0x10000000 0x4000000 ${filesize}
+```
+8. After flashing the images, turn off the board and change the boot mode pin 
+   settings to QSPI boot mode.
+9. Power cycle the board. The board now boots up using the images in the QSPI
+   flash.
diff --git a/docs/README.booting.microblaze.md b/docs/README.booting.microblaze.md
new file mode 100644
index 00000000..1ffcc3c8
--- /dev/null
+++ b/docs/README.booting.microblaze.md
@@ -0,0 +1,170 @@
+# Booting OS Images on MicroBlaze target boards
+
+Booting OS images on MicroBlaze target boards can be done using JTAG and QSPI boot modes.
+
+* [Setting Up the Target](#setting-up-the-target)
+* [Booting from JTAG](#booting-from-jtag)
+  * [Loading Bitstream using XSCT](#loading-bitstream-using-xsct)
+  * [Loading U-boot using XSCT](#loading-u-boot-using-xsct)
+  * [Loading Kernel, Device tree, Root Filesystem and U-boot boot script](#loading-kernel-device-tree-root-filesystem-and-u-boot-boot-script)
+    * [Using XSCT](#using-xsct)
+    * [Using TFTP](#using-tftp)
+
+## Setting Up the Target
+
+> **Note:** For microblaze-generic machine configuration file KCU105 evaluation 
+> board is used as reference.
+
+1. Connect a USB cable between the USB-JTAG, USB-UART connector on the target 
+   and the USB port on the host machine. 
+2. Connect 12V power to the KCU105 6-Pin power supply to J15 and turn on the board
+   power with the SW1 switch.
+3. Default UART terminal (serial port) settings is Speed `115200`, Data `8 bit`,
+   Parity `None`, Stop bits ` 1 bit` and Flow control `None`.
+4. Set the board to JTAG and other boot modes by setting the boot mode switch by 
+   referring to board user guide. For KCU105 board below is the configuration 
+   boot mode settings (SW15).
+
+> **Note:** Switch OFF = 1 = High; ON = 0 = Low
+
+| Boot Mode  | Mode Pins M[2:0] |
+|------------|------------------|
+| JTAG       | 101              |
+| QSPI       | 001              |
+
+## Booting from JTAG
+
+This boot flow requires the use of the AMD Xilinx tools, specifically XSCT and 
+the associated JTAG device drivers. This also requires access to the JTAG interface
+on the board, a number of AMD Xilinx and third-party boards come with on-board JTAG
+modules.
+
+1. Source the Vivado or Vitis tools `settings.sh` scripts.
+2. Power on the board, Open the XSCT console in the Vitis IDE by clicking the
+   XSCT button. Alternatively, you can also open the XSCT console by selecting
+   Xilinx -> XSCT Console.
+```
+$ xsct
+```
+3. In the XSCT console, connect to the target over JTAG using the connect command.
+   Optionally user can use `-url` to specify the local/remote hw_server. The 
+   connect command returns the channel ID of the connection.
+```
+xsct% connect
+```
+4. The targets command lists the available targets and allows you to select a
+   target using its ID. The targets are assigned IDs as they are discovered on
+   the JTAG chain, so the IDs can change from session to session.
+```
+xsct% targets
+```
+
+> **Note:** For non-interactive usage such as scripting, you can use the `-filter`
+   option to select a target instead of selecting the target using its ID.
+
+### Loading Bitstream using XSCT
+
+* Download the bitstream for the target using XSCT with the `fpga` command. Microblaze 
+bitstream will be located in the `${DEPLOY_DIR_IMAGE}` directory. Optionally user
+can use `fpga -no-revision-check` to skip FPGA silicon revision.
+
+```
+xsct% fpga -no-revision-check ${DEPLOY_DIR_IMAGE}/system-${MACHINE}.bit
+xsct% after 2000
+xsct% targets -set -nocase -filter {name =~ "microblaze*#0"}
+xsct% catch {stop}
+xsct% after 1000
+```
+### Loading U-boot using XSCT
+
+1. Download `u-boot.elf` to the target CPU using XSCT. Microblaze u-boot.elf will be
+located in the `${DEPLOY_DIR_IMAGE}` directory. Before u-boot.elf is loaded suspend
+the execution of active target using `stop` command.
+```
+xsct% dow ${DEPLOY_DIR_IMAGE}/u-boot.elf
+```
+2. After loading u-boot.elf resume the execution of active target using the `con`
+command in XSCT shell.
+```
+xsct% con
+```
+3. In the target Serial Terminal, press any key to stop the U-Boot auto-boot.
+```
+...
+Hit any key to stop autoboot: 0
+U-Boot>
+```
+
+### Loading Kernel, Device tree, Root Filesystem and U-boot boot script
+
+Load the images into the target DDR/MIG load address i.e., 
+`DDR base address + <image_offset>`. MicroBlaze U-boot boot script(boot.scr) 
+load address is calculated as `DDR base address + DDR Size - 0xe00000`
+
+Below example uses base DDR address as 0x80000000 and DDR size as 0x80000000 
+which matches in vivado address editor.
+
+| Image Type         | Base DDR Address | Image Offset | Load Address in DDR |
+|--------------------|------------------|--------------|---------------------|
+| Kernel             | 0x80000000       | 0x0          | 0x80000000          |
+| Device Tree        | 0x80000000       | 0x1e00000    | 0x81e00000          |
+| Rootfs             | 0x80000000       | 0x2e00000    | 0x82e00000          |
+| U-boot boot script | 0x80000000       | 0xe00000     | 0xff200000          |
+
+> **Note:** 
+> 1. `<target-image>` refers to core-image-minimal or petalinux-image-minimal
+> 2. For pxeboot boot create a symlink for `<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot`
+> as shown `$ ln -sf ${DEPLOY_DIR_IMAGE}/<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot ${DEPLOY_DIR_IMAGE}/rootfs.cpio.gz.u-boot`
+> to ensure the INITRD name in pxeboot.cfg matches with image name.
+> 3. Whilst it is possible to load the images via JTAG this connection is slow and
+this process can take a long time to execute (more than 10 minutes). If your
+system has ethernet it is recommended that you use TFTP to load these images
+using U-Boot. 
+
+#### Using XSCT
+
+1. Suspend the execution of active target using `stop` command in XSCT.
+```
+xsct% stop
+```
+2. Using the `dow` command to load the images into the target DDR/MIG
+load address.
+```
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/linux.bin.ub 0x80000000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x81e00000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot 0x82e00000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0xff200000
+```
+
+#### Using TFTP
+
+1. Configure the `ipaddr` and `serverip` of the U-Boot environment. 
+```
+U-Boot> set serverip <server ip>
+U-Boot> set ipaddr <board ip>
+```
+2. Load the images to DDR address. Make sure images are copied to tftp directory.
+```
+U-Boot> tftpboot 0x80000000 ${TFTPDIR}/linux.bin.ub
+U-Boot> tftpboot 0x81e00000 ${TFTPDIR}/system.dtb
+U-Boot> tftpboot 0x82e00000 ${TFTPDIR}/core-image-minimal-${MACHINE}.cpio.gz.u-boot
+U-Boot> tftpboot 0xff200000 ${TFTPDIR}/boot.scr
+```
+
+### Booting Linux
+
+Once the images are loaded continue the execution.
+
+1. After loading images resume the execution of active target using the `con`
+command in XSCT shell, Skip step 1 for if you have used TFTP to load images.
+```
+xsct% con
+```
+2. Terminate xsct shell.
+```
+xsct% exit
+```
+3. In the target Serial Terminal, from U-Boot prompt run `boot` command.
+```
+U-Boot> boot
+```
diff --git a/docs/README.booting.storage.md b/docs/README.booting.storage.md
new file mode 100644
index 00000000..4d33600d
--- /dev/null
+++ b/docs/README.booting.storage.md
@@ -0,0 +1,118 @@
+# Booting OS Images from Storage Device 
+
+Booting OS Images from storage devices such as SD Card, eMMC, USB and SATA devices.
+
+* [Booting from SD or eMMC](#booting-from-sd-or-emmc)
+* [Writing wic image to SD or eMMC device](#writing-image-to-sd-or-emmc-device)
+  * [Using Wic file](#using-wic-file)
+  * [Using Yocto images](#using-yocto-images)
+* [Secondary boot from USB or SATA device](#secondary-boot-from-usb-or-sata-device)
+
+## Booting from SD or eMMC
+
+Setup the card with the first partition formatted as FAT16/32. If you intend to
+boot with the root filesystem located on the SD card, also create a second
+partition formatted as EXT4.
+
+It is recommended that the first partition be at least 512MB in size, however
+this value will depend on whether using a ramdisk for the root filesystem and
+how large the ramdisk is.
+
+This section describes how to manually prepare and populate an SD card image.
+There are automation tools in OpenEmbedded that can generate disk images already
+formatted and prepared such that they can be written directly to a disk. Refer
+to the Yocto Project Manual for more details:
+https://docs.yoctoproject.org/4.1.2/singleindex.html#creating-partitioned-images-using-wic
+
+## Writing image to SD or eMMC device
+
+There are two ways to write the images to SD card or eMMC device.
+
+1. Find the device name of SD or eMMC device and make sure it is unmounted. In
+   this example we'll assume it is /dev/mmcblk<devnum><partnum>.
+2. To write image to eMMC device make sure you need to boot Linux from JTAG or 
+   SD or QSPI first, then copy the wic image to `<target_rootfs>/tmp` directory.
+
+### Using Wic file
+
+Write wic image file to the SD card or eMMC device.
+```
+$ sudo dd if=xilinx-default-sd-${DATETIME}-sda.direct of=/dev/mmcblk<devnum> bs=4M 
+```
+
+### Using Yocto images
+
+> **Note:** Use actual files to copy and don't use symlink files.
+
+1. Create a FAT32 and EXT4 partition on SD card or eMMC device.
+```
+$ sudo parted -s /dev/mmcblk<devnum> mklabel gpt mkpart primary fat32 1MiB 512MiB mkpart ext4 512MiB 8GiB name 1 boot name 2 root
+$ sudo mkfs.fat -n boot /dev/mmcblk<devnum>1 && sudo mkfs.ext4 -L root /dev/mmcblk<devnum>2
+$ sudo lsblk /dev/mmcblk<devnum> -o NAME,FSTYPE,LABEL,PARTLABEL
+```
+2. Mount the FAT32 and EXT4 partition.
+```
+$ sudo mount -L boot /mnt/boot; sudo mount -L root /mnt/rootfs` 
+```
+3. Copy the boot images to the SD card or eMMC device FAT32 partition.
+   * boot.bin
+   * boot.scr
+   * Image or uImage (For Zynq7000 only)
+   * system.dtb
+   * rootfs.cpio.gz.u-boot (If using a ramdisk)
+```
+$ cp ${DEPLOY_DIR_IMAGE}/boot.bin /mnt/boot/boot.bin
+$ cp ${DEPLOY_DIR_IMAGE}/boot.scr /mnt/boot/boot.scr
+$ cp ${DEPLOY_DIR_IMAGE}/Image /mnt/boot/Image
+$ cp ${DEPLOY_DIR_IMAGE}/system.dtb /mnt/boot/system.dtb
+$ cp ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot /mnt/boot/rootfs.cpio.gz.u-boot
+```
+4. Extract `core-image-minimal-${MACHINE}-${DATETIME}.rootfs.tar.gz` file content to the SD 
+   card or eMMC device EXT4 partition.
+```
+$ sudo tar -xf ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}-${DATETIME}.rootfs.tar.gz -C /mnt/rootfs
+$ sync
+```
+5. Unmount the SD Card or eMMC device and boot from SD or eMMC boot modes.
+```
+$ umount /mnt/boot
+$ umount /mnt/rootfs
+```
+
+## Secondary boot from USB or SATA device
+
+On Zynq, ZynqMP and Versal devices supports secondary boot medium such as USB or
+SATA external storage devices. This means target soc primary boot medium should
+be either JATG or SD/eMMC or QSPI/NOR/NAND boot modes.
+
+> **Note:** Use actual files to copy and don't use symlink files.
+
+1. Create a FAT32 and EXT4 partition on SD card or eMMC device.
+```
+$ sudo parted -s /dev/sd<X> mklabel gpt mkpart primary mkpart ext4 512MiB 8GiB name 1 root
+$ sudo sudo mkfs.ext4 -L root /dev/sd<X>1
+$ sudo lsblk /dev/sd<X> -o NAME,FSTYPE,LABEL,PARTLABEL
+```
+2. Mount the FAT32 and EXT4 partition.
+```
+$ sudo mount -L root /mnt/rootfs` 
+```
+3. Extract `core-image-minimal-${MACHINE}-${DATETIME}.rootfs.tar.gz` file content
+   to the USB or SATA device EXT4 partition.
+```
+$ sudo tar -xf ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}-${DATETIME}.rootfs.tar.gz -C /mnt/rootfs
+$ sync
+```
+4. Unmount the USB or SATA device.
+```
+$ umount /mnt/rootfs
+```
+5. Boot from JATG or SD/eMMC or QSPI/NOR/NAND boot modes and halt at u-boot.
+6. Set U-boot bootargs for USB or SATA rootfs and boot from run secondary boot 
+   from USB or SATA device
+```
+U-Boot> setenv sata_root 'setenv bootargs ${bootargs} root=/dev/sd<X>1 rw rootfstype=ext4 rootwait'
+U-Boot> setenv sataboot 'run sata_root; run default_bootcmd'
+U-Boot> saveenv
+U-Boot> run sataboot
+```
diff --git a/docs/README.booting.versal.md b/docs/README.booting.versal.md
new file mode 100644
index 00000000..afdeba2b
--- /dev/null
+++ b/docs/README.booting.versal.md
@@ -0,0 +1,189 @@
+# Booting OS Images on Versal target boards
+
+Booting OS images on Versal boards can be done using JTAG, SD, eMMC and QSPI boot
+modes.
+
+* [Setting Up the Target](#setting-up-the-target)
+* [Booting from JTAG](#booting-from-jtag)
+  * [Loading boot.bin using XSCT](#loading-bootbin-using-xsct)
+  * [Loading Kernel, Root Filesystem and U-boot boot script](#loading-kernel-root-filesystem-and-u-boot-boot-script)
+    * [Using XSCT](#using-xsct)
+    * [Using TFTP](#using-tftp)
+* [Booting from SD](#booting-from-sd)
+* [Booting from QSPI](#booting-from-qspi)
+
+## Setting Up the Target
+
+> **Note:** For versal-generic machine configuration file VCK190 evaluation 
+> board is used as reference.
+
+1. Connect a USB cable between the FTDI FT4232HL U20 USB-to-Quad-UART bridge USB
+   Type-C connector on the target and the USB port on the host machine.
+2. Connect 12V power to the VCK190 6-Pin Molex connector and turn on the board
+   power with the SW13 switch.
+3. Default UART terminal (serial port) settings is Speed `115200`, Data `8 bit`,
+   Parity `None`, Stop bits ` 1 bit` and Flow control `None`.
+4. Set the board to JTAG and other boot modes by setting the boot mode switch by 
+   referring to board user guide. For VCK190 board Below is the configuration 
+   boot mode settings (SW1).
+
+> **Note:** Switch OFF = 1 = High; ON = 0 = Low
+
+| Boot Mode | Mode Pins [3:0] | Mode SW1 [4:1]    | Comments                                          |
+|-----------|-----------------|-------------------|---------------------------------------------------|
+| JTAG      | 0000            | ON, ON, ON, ON    | Supported with or without boot module attached    |
+| QSPI      | 0010            | ON, ON, OFF, ON   | Supported only with boot module X-EBM-01 attached |
+| SD        | 1110            | OFF, OFF, OFF, ON | Supported with or without boot module attached    |
+
+## Booting from JTAG
+
+This boot flow requires the use of the AMD Xilinx tools, specifically XSCT and 
+the associated JTAG device drivers. This also requires access to the JTAG interface
+on the board, a number of AMD Xilinx and third-party boards come with on-board JTAG
+modules.
+
+1. Source the Vivado or Vitis tools `settings.sh` scripts.
+2. Power on the board, Open the XSCT console in the Vitis IDE by clicking the
+   XSCT button. Alternatively, you can also open the XSCT console by selecting
+   Xilinx -> XSCT Console.
+```
+$ xsct
+```
+3. In the XSCT console, connect to the target over JTAG using the connect command.
+   Optionally user can use `-url` to specify the local/remote hw_server. The 
+   connect command returns the channel ID of the connection.
+```
+xsct% connect
+```
+4. The targets command lists the available targets and allows you to select a
+   target using its ID. The targets are assigned IDs as they are discovered on
+   the JTAG chain, so the IDs can change from session to session.
+```
+xsct% targets
+```
+
+> **Note:** For non-interactive usage such as scripting, you can use the `-filter`
+   option to select a target instead of selecting the target using its ID.
+
+### Loading boot.bin using XSCT
+
+1. Download the boot.bin for the target using XSCT with the `device program` command.
+Versal boot.bin will be located in the `${DEPLOY_DIR_IMAGE}` directory. Default
+boot.bin consists of boot pdi, plm.elf, psm.elf, bl31.elf, u-boot.elf and 
+system.dtb. This boot.bin is generated using bootgen tool by passing a .bif file.
+
+> **Note:** In yocto by default, ${DEPLOY_DIR_IMAGE}/system.dtb is used for both
+> u-boot and kernel.
+
+```
+xsct% targets -set -nocase -filter {name =~ "*PMC*"}
+xsct% device program ${DEPLOY_DIR_IMAGE}/boot.bin
+xsct% targets -set -nocase -filter {name =~ "*A72*#0"}
+xsct% stop
+```
+2. After loading boot.bin resume the execution of active target using the `con`
+command in XSCT shell.
+```
+xsct% con
+```
+3. In the target Serial Terminal, press any key to stop the U-Boot auto-boot.
+```
+...
+Hit any key to stop autoboot: 0
+U-Boot>
+```
+
+### Loading Kernel, Root Filesystem and U-boot boot script
+
+Load the images into the target DDR/PL DRR load address i.e.,
+`DDR base address + <image_offset>`. 
+
+Below example uses base DDR address as 0x0 which matches in vivado address editor.
+
+| Image Type         | Base DDR Address | Image Offset | Load Address in DDR |
+|--------------------|------------------|--------------|---------------------|
+| Kernel             | 0x0              | 0x200000     | 0x200000            |
+| Device Tree        | 0x0              | 0x1000       | 0x1000              |
+| Rootfs             | 0x0              | 0x4000000    | 0x4000000           |
+| U-boot boot script | 0x0              | 0x20000000   | 0x20000000          |
+
+> **Note:** 
+> 1. `<target-image>` refers to core-image-minimal or petalinux-image-minimal
+> 2. For pxeboot boot create a symlink for `<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot`
+> as shown `$ ln -sf ${DEPLOY_DIR_IMAGE}/<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot ${DEPLOY_DIR_IMAGE}/rootfs.cpio.gz.u-boot`
+> to ensure the INITRD name in pxeboot.cfg matches with image name.
+> 3. Whilst it is possible to load the images via JTAG this connection is slow and
+this process can take a long time to execute (more than 10 minutes). If your
+system has ethernet it is recommended that you use TFTP to load these images
+using U-Boot. 
+> 4. If common ${DEPLOY_DIR_IMAGE}/system.dtb is used by u-boot and kernel, this
+> is already part of boot.bin we can skip loading dtb, else load kernel dtb.
+
+#### Using XSCT
+
+1. Suspend the execution of active target using `stop` command in XSCT.
+```
+xsct% stop
+```
+2. Using the `dow` command to load the images into the target DDR/PL DDR load 
+   address.
+```
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/Image 0x200000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x1000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot 0x4000000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0x20000000
+xsct% targets -set -nocase -filter {name =~ "*A72*#0"}
+```
+
+#### Using TFTP
+
+1. Configure the `ipaddr` and `serverip` of the U-Boot environment. 
+```
+Versal> set serverip <server ip>
+Versal> set ipaddr <board ip>
+```
+2. Load the images to DDR address. Make sure images are copied to tftp directory.
+```
+U-Boot> tftpboot 0x200000 ${TFTPDIR}/Image
+U-Boot> tftpboot 0x1000 ${TFTPDIR}/system.dtb
+U-Boot> tftpboot 0x4000000 ${TFTPDIR}/core-image-minimal-${MACHINE}.cpio.gz.u-boot
+U-Boot> tftpboot 0x20000000 ${TFTPDIR}/boot.scr
+
+```
+### Booting Linux
+
+Once the images are loaded continue the execution.
+
+1. After loading images resume the execution of active target using the `con`
+command in XSCT shell, Skip step 1 for if you have used TFTP to load images.
+```
+xsct% con
+```
+2. Terminate xsct shell.
+```
+xsct% exit
+```
+3. In the target Serial Terminal, from U-Boot prompt run `boot` command.
+```
+U-Boot> boot
+```
+
+## Booting from SD
+
+1. Load the SD card into the VCK190 board in the J302 SD slot.
+2. Configure the VCK190 board to boot in SD-Boot mode (1-ON, 2-OFF, 3-OFF, 4-OFF)
+   by setting the SW1. Refer [Setting Up the Target](#setting-up-the-target).
+3. Follow SD boot instructions [README](README.booting.storage.md) for more details.
+
+## Booting from QSPI
+
+1. To boot VCK190 board in QSPI boot mode, you need to connect a QSPI daughter
+   card (part number: X_EBM-01, REV_A01).
+2. With the card powered off, install the QSPI daughter card.
+3. Power on the VCK190 board and boot using JTAG or SD boot mode, to ensure that
+   U-Boot is running and also have boot.bin copied to DDR location using XSCT
+   `dow` or `tftpboot` or `fatload` command.
+4. Follow Flash boot instructions [README](README.booting.flash.md) for more details.
+5. After flashing the images, turn off the power switch on the board, and change
+   the SW1 boot mode pin settings to QSPI boot mode (1-ON, 2-OFF, 3-ON, 4-ON) by
+   setting the SW1. Refer [Setting Up the Target](#setting-up-the-target).
\ No newline at end of file
diff --git a/docs/README.booting.zynq.md b/docs/README.booting.zynq.md
new file mode 100644
index 00000000..de3fc189
--- /dev/null
+++ b/docs/README.booting.zynq.md
@@ -0,0 +1,186 @@
+# Booting OS Images on Zynq target boards
+
+Booting OS images on Zynq boards can be done using JTAG, SD, eMMC, QSPI and NAND
+boot modes.
+
+* [Setting Up the Target](#setting-up-the-target)
+
+## Setting Up the Target
+1. Connect a USB cable between the CP210x USB-to-UART bridge USB Mini-B on
+   the target and the USB port on the host machine.
+2. Connect a micro USB cable from the ZC702 board USB UART port (J17) to the USB 
+   port on the host machine.
+3. Default UART terminal(serial port) settings is Speed `115200`, Data `8 bit`,
+   Parity `None`, Stop bits ` 1 bit` and Flow control `None`.
+4. Set the board to JTAG and other boot mode by setting the boot mode switch by 
+   referring to board user guide. For zynq-generic machine configuration
+   file ZC702 evaluation board is used as reference and below is the
+   configuration boot mode settings (SW16).
+
+> **Note:** Switch OFF = 0 = Low; ON = 1 = High
+
+| Boot Mode | Mode Pins [0:4] | Mode SW16 [1:5]         | Comments               |
+|-----------|-----------------|-------------------------|------------------------|
+| JTAG      | 00000           | OFF, OFF, OFF, OFF, OFF | PS JTAG                |
+| QSPI      | 01000           | OFF, ON, OFF, OFF, OFF  | QSPI 32-bit addressing |
+| SD        | 00110           | OFF, OFF, ON, ON, OFF   | SD 2.0                 |
+
+## Booting from JTAG
+
+This boot flow requires the use of the AMD Xilinx tools, specifically XSCT and 
+the associated JTAG device drivers. This also requires access to the JTAG interface
+on the board, a number of AMD Xilinx and third-party boards come with on-board JTAG
+modules.
+
+1. Source the Vivado or Vitis tools `settings.sh` scripts.
+2. Power on the board, Open the XSCT console in the Vitis IDE by clicking the
+   XSCT button. Alternatively, you can also open the XSCT console by selecting
+   Xilinx -> XSCT Console.
+```
+$ xsct
+```
+3. In the XSCT console, connect to the target over JTAG using the connect command.
+   Optionally user can use `-url` to specify the local/remote hw_server. The 
+   connect command returns the channel ID of the connection.
+```
+xsct% connect
+```
+4. The targets command lists the available targets and allows you to select a
+   target using its ID. The targets are assigned IDs as they are discovered on
+   the JTAG chain, so the IDs can change from session to session.
+```
+xsct% targets
+```
+
+> **Note:** For non-interactive usage such as scripting, you can use the `-filter`
+   option to select a target instead of selecting the target using its ID.
+
+### Loading boot components using XSCT
+
+1. Download the boot images for the target using XSCT with the `fpga` and `dow` 
+   command. Zynq boot images will be located in the `${DEPLOY_DIR_IMAGE}`
+   directory. 
+
+> **Note:** In yocto by default, ${DEPLOY_DIR_IMAGE}/system.dtb is used for both
+> u-boot and kernel.
+
+2. Program the bitstream or skip this step if you are loading from u-boot or linux.
+```
+xsct% fpga -no-revision-check ${DEPLOY_DIR_IMAGE}/download.bit
+```
+3. Select APU Cortex-A9 Core 0 to load and execute FSBL.
+```
+xsct% targets -set -nocase -filter {name =~ "arm*#0"}
+xsct% catch {stop}
+```
+5. Download and run FSBL from APU Cortex-A9 Core 0
+```
+xsct% dow ${DEPLOY_DIR_IMAGE}/zynq_fsbl.elf
+xsct% con
+```
+7. Now download U-boot.elf and Device tree to APU and execute.
+```
+xsct% stop
+xsct% dow ${DEPLOY_DIR_IMAGE}/u-boot.elf
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x100000
+xsct% con
+```
+
+8. In the target Serial Terminal, press any key to stop the U-Boot auto-boot.
+```
+...
+Hit any key to stop autoboot: 0
+U-Boot>
+```
+
+### Loading Kernel, Root Filesystem and U-boot boot script
+
+Load the images into the target DDR load address i.e.,
+`DDR base address + <image_offset>`. 
+
+Below example uses base DDR address as 0x0 which matches in vivado address editor.
+
+| Image Type         | Base DDR Address | Image Offset  | Load Address in DDR |
+|--------------------|------------------|---------------|---------------------|
+| Kernel             | 0x0              | 0x200000      | 0x200000            |
+| Device Tree        | 0x0              | 0x100000      | 0x100000            |
+| Rootfs             | 0x0              | 0x4000000     | 0x4000000           |
+| U-boot boot script | 0x0              | 0x3000000     | 0x3000000           |
+
+> **Note:** 
+> 1. `<target-image>` refers to core-image-minimal or petalinux-image-minimal
+> 2. For pxeboot boot create a symlink for `<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot`
+> as shown `$ ln -sf ${DEPLOY_DIR_IMAGE}/<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot ${DEPLOY_DIR_IMAGE}/rootfs.cpio.gz.u-boot`
+> to ensure the INITRD name in pxeboot.cfg matches with image name.
+> 3. Whilst it is possible to load the images via JTAG this connection is slow and
+this process can take a long time to execute (more than 10 minutes). If your
+system has ethernet it is recommended that you use TFTP to load these images
+using U-Boot. 
+> 4. If common ${DEPLOY_DIR_IMAGE}/system.dtb is used by u-boot and kernel, this
+> is already part of boot.bin we can skip loading dtb, else load kernel dtb.
+
+#### Using XSCT
+
+1. Suspend the execution of active target using `stop` command in XSCT.
+```
+xsct% stop
+```
+2. Using the `dow` command to load the images into the target DDR/PL DDR load 
+   address.
+```
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/uImage 0x200000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x100000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot 0x4000000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0x3000000
+```
+
+#### Using TFTP
+
+1. Configure the `ipaddr` and `serverip` of the U-Boot environment. 
+```
+Versal> set serverip <server ip>
+Versal> set ipaddr <board ip>
+```
+2. Load the images to DDR address. Make sure images are copied to tftp directory.
+```
+U-Boot> tftpboot 0x200000 ${TFTPDIR}/uImage
+U-Boot> tftpboot 0x100000 ${TFTPDIR}/system.dtb
+U-Boot> tftpboot 0x4000000 ${TFTPDIR}/core-image-minimal-${MACHINE}.cpio.gz.u-boot
+U-Boot> tftpboot 0x3000000 ${TFTPDIR}/boot.scr
+
+```
+### Booting Linux
+
+Once the images are loaded continue the execution.
+
+1. After loading images resume the execution of active target using the `con`
+command in XSCT shell, Skip step 1 for if you have used TFTP to load images.
+```
+xsct% con
+```
+2. Terminate xsct shell.
+```
+xsct% exit
+```
+3. In the target Serial Terminal, from U-Boot prompt run `boot` command.
+```
+U-Boot> boot
+```
+
+## Booting from SD
+
+1. Load the SD card into the ZC702 board in the SD slot.
+2. Configure the ZC702 board to boot in SD-Boot mode (1-OFF, 2-OFF, 3-ON, 4-ON, 5-OFF)
+   by setting the SW6. Refer [Setting Up the Target](#setting-up-the-target).
+3. Follow SD boot instructions [README](README.booting.storage.md) for more details.
+
+## Booting from QSPI
+
+1. To boot ZC702 board in QSPI boot mode, Power on the ZCU102 board and boot 
+   using JTAG or SD boot mode, to ensure that U-Boot is running and also have 
+   boot.bin copied to DDR location using XSCT `dow` or `tftpboot` or `fatload`
+   command.
+2. Follow Flash boot instructions [README](README.booting.flash.md) for more details.
+3. After flashing the images, turn off the power switch on the board, and change
+   the SW16 boot mode pin settings to QSPI boot mode (1-OFF, 2-ON, 3-OFF, 4-OFF, 5-OFF)
+   by setting the SW16. Refer [Setting Up the Target](#setting-up-the-target).
\ No newline at end of file
diff --git a/docs/README.booting.zynqmp.md b/docs/README.booting.zynqmp.md
new file mode 100644
index 00000000..c8f8aa21
--- /dev/null
+++ b/docs/README.booting.zynqmp.md
@@ -0,0 +1,212 @@
+# Booting OS Images on ZynqMP target boards
+
+Booting OS images on ZynqMP boards can be done using JTAG, SD, eMMC, QSPI and 
+NAND boot modes.
+
+* [Setting Up the Target](#setting-up-the-target)
+* [Booting from JTAG](#booting-from-jtag)
+  * [Loading boot components using XSCT](#loading-boot-components-using-xsct)
+  * [Loading Kernel, Root Filesystem and U-boot boot script](#loading-kernel-root-filesystem-and-u-boot-boot-script)
+    * [Using XSCT](#using-xsct)
+    * [Using TFTP](#using-tftp)
+* [Booting from SD](#booting-from-sd)
+* [Booting from QSPI](#booting-from-qspi)
+
+## Setting Up the Target
+1. Connect a USB cable between the CP2180 USB-to-Quad-UART bridge USB Micro-B on
+   the target and the USB port on the host machine.
+2. Connect a micro USB cable from the ZCU102 board USB UART port (J83) to the USB
+   port on the host machine.
+3. Default UART terminal(serial port) settings is Speed `115200`, Data `8 bit`,
+   Parity `None`, Stop bits ` 1 bit` and Flow control `None`.
+4. Set the board to JTAG and other boot mode by setting the boot mode switch by 
+   referring to board user guide. For zynqmp-generic machine configuration
+   file zcu102 evaluation board is used as reference and below is the
+   configuration boot mode settings (SW6).
+
+> **Note:** Switch OFF = 1 = High; ON = 0 = Low
+
+| Boot Mode | Mode Pins [3:0] | Mode SW6 [3:0]    | Comments                  |
+|-----------|-----------------|-------------------|---------------------------|
+| JTAG      | 0000            | ON, ON, ON, ON    | PS JTAG                   |
+| QSPI      | 0010            | ON, ON, OFF, ON   | QSPI 32-bit addressing    |
+| SD        | 1110            | OFF, OFF, OFF, ON | SD 3.0 with level shifter |
+
+## Booting from JTAG
+
+This boot flow requires the use of the AMD Xilinx tools, specifically XSCT and 
+the associated JTAG device drivers. This also requires access to the JTAG interface
+on the board, a number of AMD Xilinx and third-party boards come with on-board JTAG
+modules.
+
+1. Source the Vivado or Vitis tools `settings.sh` scripts.
+2. Power on the board, Open the XSCT console in the Vitis IDE by clicking the
+   XSCT button. Alternatively, you can also open the XSCT console by selecting
+   Xilinx -> XSCT Console.
+```
+$ xsct
+```
+3. In the XSCT console, connect to the target over JTAG using the connect command.
+   Optionally user can use `-url` to specify the local/remote hw_server. The 
+   connect command returns the channel ID of the connection.
+```
+xsct% connect
+```
+4. The targets command lists the available targets and allows you to select a
+   target using its ID. The targets are assigned IDs as they are discovered on
+   the JTAG chain, so the IDs can change from session to session.
+```
+xsct% targets
+```
+
+> **Note:** For non-interactive usage such as scripting, you can use the `-filter`
+   option to select a target instead of selecting the target using its ID.
+
+### Loading boot components using XSCT
+
+1. Download the boot images for the target using XSCT with the `fpga` and `dow` 
+   command. ZyqnMP boot images will be located in the `${DEPLOY_DIR_IMAGE}`
+   directory. 
+
+> **Note:** In yocto by default, ${DEPLOY_DIR_IMAGE}/system.dtb is used for both
+> u-boot and kernel.
+
+2. Program the bitstream or skip this step if you are loading from u-boot or linux.
+```
+xsct% fpga -no-revision-check ${DEPLOY_DIR_IMAGE}/download.bit
+```
+3. By default, JTAG security gates are enabled. Disable the security gates for 
+   DAP, PL TAP, and PMU (this makes the PMU MB target visible to the debugger).
+```
+xsct% targets -set -nocase -filter {name =~ "*PSU*"}
+xsct% mask_write 0xFFCA0038 0x1C0 0x1C0
+```
+3. Verify if the PMU MB target is listed under the PMU device. Now, load the PMU
+   firmware.
+```
+xsct% targets -set -nocase -filter {name =~ "*MicroBlaze PMU*"}
+xsct% catch {stop}
+xsct% dow ${DEPLOY_DIR_IMAGE}/pmufw.elf
+xsct% con
+```
+5. Reset APU Cortex-A53 Core 0 to load and execute FSBL, This step is important, 
+   because when the ZynqMP boots up in JTAG boot mode, all the APU and RPU cores
+   are held in reset. You must clear the resets on each core before performing 
+   debugging on these cores. You can use the `rst` command in XSCT to clear the
+   resets.
+```
+xsct% targets -set -nocase -filter {name =~ "*A53*#0"}
+xsct% rst -processor -clear-registers
+```
+6. Download and run FSBL from APU Cortex-A53 Core 0
+```
+xsct% dow ${DEPLOY_DIR_IMAGE}/zynqmp_fsbl.elf
+xsct% con
+```
+7. Now download TF-A, U-boot.elf and Device tree to APU and execute.
+```
+xsct% stop
+xsct% dow ${DEPLOY_DIR_IMAGE}/bl31.elf
+xsct% dow ${DEPLOY_DIR_IMAGE}/u-boot.elf
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x100000
+xsct% con
+```
+
+8. In the target Serial Terminal, press any key to stop the U-Boot auto-boot.
+```
+...
+Hit any key to stop autoboot: 0
+U-Boot>
+```
+
+### Loading Kernel, Root Filesystem and U-boot boot script
+
+Load the images into the target DDR/PL DRR load address i.e.,
+`DDR base address + <image_offset>`. 
+
+Below example uses base DDR address as 0x0 which matches in vivado address editor.
+
+| Image Type         | Base DDR Address | Image Offset | Load Address in DDR |
+|--------------------|------------------|--------------|---------------------|
+| Kernel             | 0x0              | 0x200000     | 0x200000            |
+| Device Tree        | 0x0              | 0x1000       | 0x1000              |
+| Rootfs             | 0x0              | 0x04000000   | 0x4000000           |
+| U-boot boot script | 0x0              | 0x20000000   | 0x20000000          |
+
+> **Note:** 
+> 1. `<target-image>` refers to core-image-minimal or petalinux-image-minimal
+> 2. For pxeboot boot create a symlink for `<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot`
+> as shown `$ ln -sf ${DEPLOY_DIR_IMAGE}/<target-image>-${MACHINE}-${DATETIME}.cpio.gz.u-boot ${DEPLOY_DIR_IMAGE}/rootfs.cpio.gz.u-boot`
+> to ensure the INITRD name in pxeboot.cfg matches with image name.
+> 3. Whilst it is possible to load the images via JTAG this connection is slow and
+this process can take a long time to execute (more than 10 minutes). If your
+system has ethernet it is recommended that you use TFTP to load these images
+using U-Boot. 
+> 4. If common ${DEPLOY_DIR_IMAGE}/system.dtb is used by u-boot and kernel, this
+> is already part of boot.bin we can skip loading dtb, else load kernel dtb.
+
+#### Using XSCT
+
+1. Suspend the execution of active target using `stop` command in XSCT.
+```
+xsct% stop
+```
+2. Using the `dow` command to load the images into the target DDR/PL DDR load 
+   address.
+```
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/Image 0x200000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0x100000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot 0x4000000
+xsct% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0x20000000
+```
+
+#### Using TFTP
+
+1. Configure the `ipaddr` and `serverip` of the U-Boot environment. 
+```
+Versal> set serverip <server ip>
+Versal> set ipaddr <board ip>
+```
+2. Load the images to DDR address. Make sure images are copied to tftp directory.
+```
+U-Boot> tftpboot 0x200000 ${TFTPDIR}/Image
+U-Boot> tftpboot 0x100000 ${TFTPDIR}/system.dtb
+U-Boot> tftpboot 0x4000000 ${TFTPDIR}/core-image-minimal-${MACHINE}.cpio.gz.u-boot
+U-Boot> tftpboot 0x20000000 ${TFTPDIR}/boot.scr
+
+```
+### Booting Linux
+
+Once the images are loaded continue the execution.
+
+1. After loading images resume the execution of active target using the `con`
+command in XSCT shell, Skip step 1 for if you have used TFTP to load images.
+```
+xsct% con
+```
+2. Terminate xsct shell.
+```
+xsct% exit
+```
+3. In the target Serial Terminal, from U-Boot prompt run `boot` command.
+```
+U-Boot> boot
+```
+
+## Booting from SD
+
+1. Load the SD card into the ZCU102 board in the J100 SD slot.
+2. Configure the ZCU102 board to boot in SD-Boot mode (1-ON, 2-OFF, 3-OFF, 4-OFF)
+   by setting the SW6. Refer [Setting Up the Target](#setting-up-the-target).
+3. Follow SD boot instructions [README](README.booting.storage.md) for more details.
+
+## Booting from QSPI
+
+1. To boot ZCU012 board in QSPI boot mode, Power on the ZCU102 board and boot 
+   using JTAG or SD boot mode, to ensure that U-Boot is running and also have 
+   boot.bin copied to DDR location using XSCT `dow` or `tftpboot` or `fatload`
+   command.
+2. Follow Flash boot instructions [README](README.booting.flash.md) for more details.
+3. After flashing the images, turn off the power switch on the board, and change
+   the SW6 boot mode pin settings to QSPI boot mode (1-ON, 2-ON, 3-OFF, 4-ON) by
+   setting the SW6. Refer [Setting Up the Target](#setting-up-the-target).
\ No newline at end of file