Corrupted QSPI flash LS1046ARDB

[clement_barriba]

First, we tried to flash uboot into ls1046ardb qspi using a debugger. After a bad manipulation, Uboot was unable to load and prompt in serial neither on bank0 nor bank4. In order to recover uboot in bank0 & bank4 we booted from an SD card and flashed uboot on bank0 and bank4 with “sf ...” commands.

With the command “cpld reset altbank” we can load uboot flashed in qspi bank4 (after a boot from SD card). But with SW3[5] = 1 ,in order to boot on bank4 after a simple reset, nothing happens.

Bank0 is totally inaccessible. After a reset without SD card, nothing happens, the board seems to be stuck in reset mode. Moreover, with the debugger, we can flash uboot_ls1046ardb_qspi.bin at 0x40100000 and dump it, but we are unable to flash rcw_1800_qspiboot.bin at 0x40000000~0x40008000 we can’t even erase this flash block, values are always 0.

Thank you in advance for your assistance.

[benedikt_schroe]

This issue is present in the flash file "snor_ls1000.bin" for LS1xxx from March-2019 - September-2019.

It is recommended to use the Lauterbach DVD release 2019.02 which doesn't contain this issue.

As an alternative, please contact Lauterbach (support@lauterbach.com) for an update.

If you don't want to do a full update of your software, please look for the file "snor_ls1000.bin" in your TRACE32 installation and replace it by a newer version. You can either use the binary from the Lauterbach DVD release 2019.02 or request it from the support.

[ufedor]

You wrote:

> with the debugger, we can flash uboot_ls1046ardb_qspi.bin at 0x40100000 and dump it, but we are unable

> to flash rcw_1800_qspiboot.bin at 0x40000000~0x40008000 we can’t even erase this flash block

Do you see a change in Flash Programmer behaviour when SW2[5] is altered?

[clement_barriba]

Do you mean SW3[5] ? I have not seen differences in Flash Programmer behaviour between SW3[5]=1 and SW3[5]=0.

[ufedor]

What is the RCW source when the CodeWarrior Flash Programmer is used?

Please after booting from SD card use U-Boot to program complete firmware image into SPI DEV#0 by executing "sf probe 0:0" command instead of "sf probe 0:1".

The firmware image could be downloaded from:

LSDK Open Source 

COMPONENTS -> LSDK IMAGES

[clement_barriba]

We are using RCW and firmware image from bootpartition_arm64_lts_4.14 (it works perfectly on bank4). Our debugger is Lauterbach power debug pro. We already tried to load the firmware image with the command "sf probe 0:0". After a memory dump with the command "md" we see that the flash is correctly programmed except the RCW at the address range 0x40000000 to 0x40007fff that is empty (filled with 0).

[ufedor]

Please discuss the debugger SPI Flash programming issue with Lauterbach.