Problem Relocating u-boot QSPI text location from 0x100000 to 0x10000

[hero]

Hi All,

I have a ls1043 based custom board and I am able to use my custom RCW and 2018.09 u-boot to boot just fine.

I am trying the u-boot text location on QSPI flash from 0x100000 to 0x10000.

Looks like that requires 2 changes, RCW/PBL and u-boot itself.

RCW change:
The RCW/PBL change to change the Boot location pointer high-order address (BOOTLOCPTRH) Page 457 of LS1043ARM.pdf

--- rcw/LSDK-18.12/mainline/src/ls1043aqds/RR_FQPP_1455/rcw_1600_qspiboot_T20.rcw 2019-09-27 22:11:49.000000000 -0700
+++ /rcw/LSDK-18.12/mainline/src/ls1043aqds/RR_FQPP_1455/rcw_1600_qspiboot.rcw 2019-09-27 22:11:49.000000000 -0700
@@ -147,7 +147,7 @@
// QSPI flash clock
write 0x57015c, 0x40100000
write 0x570600, 0x00000000
-write 0x570604, 0x40100000
+write 0x570604, 0x40010000
.end

patched for u-boot as below:
diff --git a/configs/ls1043aqds_qspi_defconfig b/configs/ls1043aqds_qspi_defconfig
index 2f14022..a4ad5a8 100644
--- a/configs/ls1043aqds_qspi_defconfig
+++ b/configs/ls1043aqds__qspi_defconfig
@@ -1,6 +1,6 @@
CONFIG_ARM=y
CONFIG_TARGET_LS1043AQDS=y
-CONFIG_SYS_TEXT_BASE=0x40100000
+CONFIG_SYS_TEXT_BASE=0x40010000
CONFIG_FSL_LS_PPA=y
CONFIG_DISTRO_DEFAULTS=y
CONFIG_NR_DRAM_BANKS=2

No luck with these change.
After I flash the u-boot to the new location 0x10000 and reset, the unit never comes up.

Can someone please help advice if there is something else that needs to be done to relocate u-boot?

Thanks,
Bhanu

ls1043 ask

u-boot image

u-boot init‌

[hero]

Hi ufedor,

> If "not" - which images were used when booting is possible?

Sorry, I did not catch that. Please find the known good images attached. I called then "GOLD".

2b094bd104c0fe61af5a4038e968d241eb836fc7 rcw_1600_qspiboot_T40.bin.swapped.GOLD
3a991dcd0b25da8995cbdf71e991d40d5c0f7406 u-boot_ls1043aqds_wg_t40_qspi.bin.GOLD

Thanks,

Mukund J

[ufedor]

Sorry for the delay.

I've inspected provided images and did not find any obvious issue.

Please enable debug messages in U-Boot and use CodeWarrior to determine the processor state during unsuccessful boot.

[hero]

Hi,

The board does not have JTAG on board. Does u-boot support console stubs to just like KGDB?

Thanks

[ufedor]

Using debug messages it can be possible to determine position where the booting stops.

[hero]

Hiufedor,

If you look into the screenlog log file(snippet below), a reset after programming "u-boot_ls1043aqds_wg_t40_qspi.bin.zip" and "rcw_1600_qspiboot_T40.bin.swapped.zip kills the boards and does not bring it up anymore.

Snippet from the screenlog:

=> cmp.b 0x82000000 0x80000000 0xe0
Total of 224 byte(s) were the same
=> reset
resetting ...

Does not BOOT after this.

1. And I cannot figure what in those files cause this failure.

2. And how to fix it so that when I relocate the uboot  to qspi offset 0x10000, it works.

Mukund J

[ufedor]

If "not" - which images were used when booting is possible?

[hero]

Hi Ufedor,

Did you notice the attachments you were asking for?

Did you get a chance to review the?

Mukund J

[hero]

I have attached more than screenlog.5.zip

I have attached these 4 files, RCW and u-boot part of those atttachments. Do you see them?

files I have attached:

screenlog.5.zip
rcw_1600_qspiboot_T40.rcw.zip
u-boot_ls1043aqds_wg_t40_qspi.bin.zip
rcw_1600_qspiboot_T40.bin.swapped.zip

Thanks,

Mukund J

[ufedor]

Are you saying that the "screenlog.5.zip" was obtained when the "u-boot_ls1043aqds_wg_t40_qspi.bin.zip" and "rcw_1600_qspiboot_T40.bin.swapped.zip" were programmed into the SPI Flash?

If "not" - which images were used when booting is possible?

[hero]

Hi ufedor,

I did not quite get your question. But, I will try and answer a few things.

The images I used are attached. And these are the once that fail.

And these have the patch I provided early on applied to them.

u-boot_ls1043aqds_wg_t40_qspi.bin.zip

rcw_1600_qspiboot_T40.bin.swapped.zip

Both u-boot and RCW are from LSDK18.12.

u-boot/2018.09

rcw/LSDK-18.12

Does it answer your question? Otherwise, can you make it little more clear on what you are asking.

Thanks,

Mukund J

[ufedor]

You provided "screenlog.5" log.

Which RCW and U-Boot images correspond to this log?

[hero]

Hi ufedor,

Thanks for looking into this.

I am doing standalone builds for RCW and u-boot as I am building outside of yocto in my own build environment.

So, I don't have the composite build. Is there a quick way to make one out of yocto build.

I have also attached a bootlog, so that might help.

my instructions to install the image are below:

#How to upgrade rcw
tftp 0x82000000 rcw-tweeks/t40/mj-tweeked/rcw_1600_qspiboot_T40.bin.swapped
sf probe 0:0;sf erase 0 +$filesize;sf write 0x82000000 0 $filesize

# How to upgrade u-boot
tftp 82000000 rcw-tweeks/t40/mj-tweeked/u-boot_ls1043aqds_wg_t40_qspi.bin
sf probe 0:0;sf erase 10000 +$filesize;sf write 82000000 10000 $filesize

Mukund J

[ufedor]

Which RCW and U-Boot images are used when the processor is capable to boot?

[ufedor]

Described steps are correct.

Please ensure that binary images of RCW and U-Boot were programmed to the SPI Flash correctly.

Please consider that LSDK is capable to build composite firmware image (pre-built images are provided at LSDK Open Source , LSDK IMAGES) - refer to the LSDK Documentation:

Submit Form 

Please provide the resulting composite firmware image for inspection.