samsung: tizen_rpi: Set to slot_a by default when run tfm

In some case, it's resetting to normal mode from download mode.
So it's always running as ramdisk boot mode.

To fix above issue, Set to slot_a by default when run tfm.
"run tfm" means that user tries to flahs entire image.
So it doesn't need that it enters to slot_b mode.

To prevent the overwrite, change the loading address to 0x02500000.
Because scriptaddr is using 0x02400000.

Change-Id: Iad0791484fb30d08d4584763088b80ad05979df1
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>

diff --git a/include/samsung/tizen_rpi.h b/include/samsung/tizen_rpi.h
index b7593e13d97664ed3f69f5f4326abe4c0e2a2046..fc7f12f255938db60d7360ba7ec28f78ad724a62 100644 (file)
--- a/include/samsung/tizen_rpi.h
+++ b/include/samsung/tizen_rpi.h
@@ -110,7 +110,7 @@
        "nodef_val=6665646e\0"                  \
        "normal_val=6d726f6e\0"                 \
        "download_val=6c6e7764\0"               \
-       "tfm=setenv bootmode download; run bootcmd\0"   \
+       "tfm=setenv bootmode download; run set_to_part_a; run bootcmd\0"        \
        "tizen_bootarg=cgroup_enable=memory "           \
                TIZEN_VC_MEM                            \
                "8250.nr_uarts=1 dma.dmachans=0x7f35 bcm2709.serial=0xed6687d3 "        \

diff --git a/tizen/bootscript/tizen-boot-rpi4.scr b/tizen/bootscript/tizen-boot-rpi4.scr
index f6bac09b665808b65e819ced21e1a573dd49ff93..b284cea662ae155ebe982e09e3c3201818eefcd4 100644 (file)
--- a/tizen/bootscript/tizen-boot-rpi4.scr
+++ b/tizen/bootscript/tizen-boot-rpi4.scr
@@ -44,8 +44,8 @@ fi
 if test "0x${distro_bootpart}" -ne "${bootpart}"; then
        # Load the environmet from partition_b
        echo "Loading uboot.env from boot_${partition_ab}"
-       load $devtype $devnum:$bootpart 0x02400000 uboot.env
-       env import -b 0x02400000 0x4000
+       load $devtype $devnum:$bootpart 0x02500000 uboot.env
+       env import -b 0x02500000 0x4000
        exit
 fi