LSDK 20.12 firmware image bricks LS1012A-FRWY

[laodzu]

I bricked my FRWY-LS1012A after installing the LSDK 20.12 firmware image.

The documentation[1] instructs me to download this firmware file[2].  The file is only 1.9 MiB in size but I still went ahead and installed it.  After flashing the image to SPI-NOR I now only see this message and then the board hangs:

NOTICE: DDR Init Done
NOTICE: BL2: v1.5(release):LSDK-20.12
NOTICE: BL2: Built : 04:33:20, Dec 11 2020
NOTICE: BL2: Booting BL31

Did I do something wrong or is this image broken?

Any advice on how to fix this with CodeWarrior?

Thanks in advance

  Detlev

[1] https://docs.nxp.com/bundle/GUID-3FFCCD77-5220-414D-8664-09E6FB1B02C6/page/GUID-3D1CA0B4-72C5-4EA3-8...

[2] https://www.nxp.com/lgfiles/sdk/lsdk2012/firmware_ls1012afrwy_uboot_qspiboot.img

[laodzu · Accepted solution]

So just for the records - I have to admit that I screwed up on this one.  I accidentally regarded my LS1012A-FRDM board as a LS1012A-FRWY board and thus installed a wrong image.  The FRDM board is simply not supported anymore so trying to unbrick it is futile.

[Pavel]

The FRWY board schematics 30191 revs A and B had 512MB DDR3L. The Rev C board schematic has 256MB.
Rev A and B were early versions of this board.

The boards are shipped with a sticker on the underside indicating the schematic "SCH" revision. For the Rev C board, the sticker says "SCH-32169 REV C".

firmware_ls1012afrwy_512mb_uboot_qspiboot.img should be used if you have a Rev A or Rev B schematic board.
firmware_ls1012afrwy_uboot_qspiboot.img should be used if you have a SCH Rev C board.

Check please revision of your board.

[laodzu]

Hi Pavel,

thanks for your reply.  I was aware that there are multiple versions as I saw the 512MiB option built by LSDK.  I did not find any information as to what the differences are, so thank you very much for the explanation (which should really be in the documents).

I checked the sticker and indeed I have an "Rev C" board, but the sticker says "SCH-29217 REV C". So I selected the correct firmware (by sheer luck).  I am still stuck as the board does not boot and the flash scripts tell me to disconnect RESET_REQ_B for which I cannot find a jumper or any other means to do this.

Any idea on how to unbrick the board?

[laodzu]

So I found this thread on how to re-flash an LS1012A:

https://community.nxp.com/t5/CodeWarrior-for-QorIQ/LS1012-custom-board-JTAG-speed-too-low/m-p/600769...

For the target images I would like to try the firmware image from LSDK 20.04.

I then get this error messages:

dzu@zarniwoop:/media/dzu/hd01-ext4/Freescale/CW4NET_v2020.06/CW_ARMv8/ARMv8/gdb/bin$ ./aarch64-fsl-gdb
GNU gdb (GDB) 7.11.1.0.05c0cb6-b200311 (NXP Semiconductors)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=x86_64-linux-gnu --target=aarch64-fsl-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) source ../../gdb_extensions/flash/cwflash.py 
Starting flash programmer services...
Starting local server...
Successfully started gdb server 127.0.0.1:45001
Set gdb remote timeout to 7200
Connecting to target...
Using LS1012A SoC
Using CWTAP connected to local usb port
Using jtag speed 16000
Connecting to probe...
 connected successfully
Successfully connected to probe
Initializing target...
Running init script /media/dzu/hd01-ext4/Freescale/CW4NET_v2020.06/CW_ARMv8/ARMv8/gdb_extensions/flash/scripts/../../../../Config/boards/LS1012A_RDB_init.py
RCW error encountered. In order to diagnose the error temporarily change the board configuration switches to ignore the assertion of the RESET_REQ_B signal. Please refer to board reference manual in order to locate the appropriate switch that controls this behavior.
Error: fail to initialize target
Closing debugger server...
Error: fail to start flash programming services.
(gdb)

Looking through the Freeway documents I am not sure how to do this on the board.

Any idea on how to proceed?