boot.cmd.ubifs: Fix in boot.scr for vck5000

Due to recent u-boot changes wrt boot_cmd, booti command is taking input
as booti 0x00200000 - 0x00001000, and ramdisk address offset is missing in
u-boot. So, added JTAG boot mode support in boot script to support jtag boot
target, When user wants to debug/boot vck5000 wrt to jtag boot mode.

Signed-off-by: John Vicky Vykuntapu <johnvicky.vykuntapu@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>

1 files changed, 4 insertions, 0 deletions

diff --git a/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx-scr/boot.cmd.ubifs b/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx-scr/boot.cmd.ubifs
index dca974ab..fde094cf 100644
--- a/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx-scr/boot.cmd.ubifs
+++ b/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx-scr/boot.cmd.ubifs
@@ -7,6 +7,10 @@
 
 for boot_target in ${boot_targets};
 do
+        echo "Trying to load boot images from ${boot_target}"
+        if test "${boot_target}" = "jtag" ; then
+                @@KERNEL_BOOTCMD@@ @@KERNEL_LOAD_ADDRESS@@ @@RAMDISK_IMAGE_ADDRESS@@ @@DEVICETREE_ADDRESS@@
+        fi
         if test "${boot_target}" = "xspi0" || test "${boot_target}" = "qspi" || test "${boot_target}" = "qspi0"; then
                 ubifsls @@FIT_IMAGE@@
                 if test $? = 0; then