README.booting.versal.md: Add missing xen jtag boot steps

1. Add missing xen jtag boot steps.
2. Add info on how to calculate Versal xen image offset for JTAG boot.

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

1 files changed, 19 insertions, 9 deletions

diff --git a/docs/README.booting.versal.md b/docs/README.booting.versal.md
index 4f673689..25738784 100644
--- a/docs/README.booting.versal.md
+++ b/docs/README.booting.versal.md
@@ -133,20 +133,27 @@ Below example uses base DDR address as 0x0 which matches in vivado address edito
 
 | Image Type         | Base DDR Address | Image Offset | Load Address in DDR |
 |--------------------|------------------|--------------|---------------------|
-| Kernel             | 0x0              | 0x200000     | 0x200000            |
-| Device Tree        | 0x0              | 0x1000       | 0x1000              |
+| Linux Kernel       | 0x0              | 0x200000     | 0x200000            |
+| Device Tree Blob   | 0x0              | 0x1000       | 0x1000              |
 | Rootfs             | 0x0              | 0x4000000    | 0x4000000           |
 | U-boot boot script | 0x0              | 0x20000000   | 0x20000000          |
 
 2. **Xen**
 
+> **Note:** Xen, Rootfs and Device Tree image offset is calculated as shown below.
+> * `Xen Rootfs = Base DDR Address + Linux Kernel Image Offset(0xE00000) + Size of Linux Kernel Image`
+> * `Xen Kernel = Base DDR Address + Xen Rootfs Image Offset (Ex: 0x2600000) + Size of Xen Rootfs`
+> * `Device Tree Blob = Base DDR Address + Xen Kernel Image Offset (Ex: 0xBA00000) + Size of Device Tree Blob`
+
 | Image Type         | Base DDR Address | Image Offset | Load Address in DDR |
 |--------------------|------------------|--------------|---------------------|
-| Kernel             | 0x0              | 0xE00000     | 0xE00000            |
-| Device Tree        | 0x0              | 0xC000000    | 0xc000000           |
-| Rootfs             | 0x0              | 0x02600000   | 0x02600000          |
+| Linux Kernel       | 0x0              | 0xE00000     | 0xE00000            |
+| Xen Rootfs         | 0x0              | 0x2600000    | 0x2600000           |
+| Xen Kernel         | 0x0              | 0xBA00000    | 0xBA00000           |
+| Device Tree Blob   | 0x0              | 0xC000000    | 0xC000000           |
 | 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`
@@ -176,12 +183,14 @@ xsdb% stop
    xsdb% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz.u-boot 0x4000000
    xsdb% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0x20000000
    ```
+
    * Xen XSDB
    ```
    xsdb% targets -set -nocase -filter {name =~ "*A72*#0"}
    xsdb% dow -data ${DEPLOY_DIR_IMAGE}/Image 0xE00000
-   xsdb% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0xc000000
-   xsdb% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz 0x02600000
+   xsdb% dow -data ${DEPLOY_DIR_IMAGE}/core-image-minimal-${MACHINE}.cpio.gz 0x2600000
+   xsdb% dow -data ${DEPLOY_DIR_IMAGE}/xen 0xBA00000
+   xsdb% dow -data ${DEPLOY_DIR_IMAGE}/system.dtb 0xC000000
    xsdb% dow -data ${DEPLOY_DIR_IMAGE}/boot.scr 0x20000000
    ```
 
@@ -208,9 +217,10 @@ Versal> set ipaddr <board ip>
    ```
    U-Boot> tftpboot 0xE00000 Image
    U-Boot> setenv kernel_size 0x$filesize
-   U-Boot> tftpboot 0xc000000 system.dtb
-   U-Boot> tftpboot 0x02600000 core-image-minimal-${MACHINE}.cpio.gz
+   U-Boot> tftpboot 0x2600000 core-image-minimal-${MACHINE}.cpio.gz
    U-Boot> setenv ramdisk_size 0x$filesize
+   U-Boot> tftpboot 0xBA00000 xen
+   U-Boot> tftpboot 0xC000000 system.dtb
    U-Boot> tftpboot 0x20000000 boot.scr
    ```