External loader for STM32WL5: code is not loaded in ram

Question

Hello,I'm trying to develop a custom external loader for STM32WL5 device, in a custom board using SPI flash memory Winbond W25Q80DV.In the past I've already developed external loaders successfully for other MCUs and boards.I again followed the steps described by official documentation, hints on this forum, examples in folder bin/ExternalLoader of CubeProgrammer: I set up a new project with CubeIDE, compiled, created .stldr file and copied it in ExternalLoader folder. If I debug the project everything is ok. Besides, opening CubeProgrammer, I correctly see my new external loader in external loader list and information provided are correct.The problem is that when I try to read from the SPI flash mapped address (set to 0x9000 0000 in this case) using CubeProgrammer, the procedure fails. Selecting Verbosity level 3, I can see these messages: 11:11:37:994 : UR connection mode is defined with the HWrst reset mode11:11:38:061 : ST-LINK SN : 54FF6906668549541930168711:11:38:062 : ST-LINK FW : V2J43S711:11:38:062 : Board : --11:11:38:062 : Voltage : 3.22V11:11:38:062 : SWD freq : 4000 KHz11:11:38:062 : Connect mode: Normal11:11:38:062 : Reset mode : Hardware reset11:11:38:062 : Device ID : 0x49711:11:38:063 : Revision ID : Rev Y11:11:38:063 : Reading data...11:11:38:063 : r ap 0 @0x1FFF7550 0x00000004 bytes Data 0x0000FFFF11:11:38:063 : Reading data...11:11:38:063 : r ap 0 @0x1FFF7550 0x00000004 bytes Data 0x0000FFFF11:11:38:063 : Database: Config 1 is active.11:11:38:063 : r ap 0 @0x1FFF73F8 0x00000004 bytes Data 0x3810000211:11:38:064 : r ap 0 @0x1FFF73FC 0x00000004 bytes Data 0x46AFDBD111:11:38:064 : flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer3\bin/FlashLoader/0x497.stldr is loaded11:11:38:064 : Debug in Low Power mode is not supported for this device.11:11:38:064 : r ap 0 @0x1FFF73F8 0x00000004 bytes Data 0x3810000211:11:38:064 : r ap 0 @0x1FFF73FC 0x00000004 bytes Data 0x46AFDBD111:11:38:064 : Reading data...11:11:38:064 : r ap 0 @0x1FFF75E0 0x00000004 bytes Data 0xFFFF010011:11:38:064 : r ap 0 @0x1FFF3EFE 0x00000004 bytes Data 0x008800C411:11:38:333 : r ap 0 @0x1FFF73F8 0x00000004 bytes Data 0x3810000211:11:38:334 : r ap 0 @0x1FFF73FC 0x00000004 bytes Data 0x46AFDBD111:11:38:334 : r ap 0 @0x1FFF3EFE 0x00000004 bytes Data 0x008800C411:11:38:334 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer3\bin/ExternalLoader/W25Q80DV_Term_Redox.stldr11:11:38:334 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer3\bin/ExternalLoader/W25Q80DV_Term_Redox.stldr11:11:38:334 : External loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer3\bin/ExternalLoader/W25Q80DV_Term_Redox.stldr is loaded11:11:38:334 : UPLOADING OPTION BYTES DATA ...11:11:38:334 : Bank : 0x0011:11:38:334 : Address : 0x5800402011:11:38:334 : Size : 96 Bytes11:11:38:334 : Reading data...11:11:38:334 : r ap 0 @0x58004020 0x00000060 bytes Data 0x3BFFF0AA11:11:38:335 : Bank : 0x0111:11:38:335 : Address : 0x5800408011:11:38:335 : Size : 8 Bytes11:11:38:335 : Reading data...11:11:38:335 : r ap 0 @0x58004080 0x00000008 bytes Data 0x80FF00FF11:11:38:335 : UPLOADING OPTION BYTES DATA ...11:11:38:336 : Bank : 0x0011:11:38:336 : Address : 0x5800402011:11:38:336 : Size : 96 Bytes11:11:38:336 : Reading data...11:11:38:336 : r ap 0 @0x58004020 0x00000060 bytes Data 0x3BFFF0AA11:11:38:336 : Bank : 0x0111:11:38:336 : Address : 0x5800408011:11:38:336 : Size : 8 Bytes11:11:38:336 : Reading data...11:11:38:337 : r ap 0 @0x58004080 0x00000008 bytes Data 0x80FF00FF11:11:38:337 : r ap 0 @0x1FFF73F8 0x00000004 bytes Data 0x3810000211:11:38:337 : r ap 0 @0x1FFF73FC 0x00000004 bytes Data 0x46AFDBD111:11:38:337 : r ap 0 @0x1FFF3EFE 0x00000004 bytes Data 0x008800C411:11:38:337 : UPLOADING ...11:11:38:337 : Size : 1024 Bytes11:11:38:337 : Address : 0x9000000011:11:38:337 : Read progress:11:11:38:337 : Reading data...11:11:38:337 : halt ap 011:11:38:338 : w ap 0 reg 15 PC (0x20000000)11:11:38:338 : w ap 0 reg 17 MSP (0x20000500)11:11:38:338 : w ap 0 reg 16 xPSR (0x01000000)11:11:38:339 : Loader read...11:11:38:339 : Init flashloader...11:11:38:340 : halt ap 011:11:38:340 : w ap 0 reg 0 R0 0x0000000011:11:38:340 : w ap 0 reg 1 R1 0x0000000011:11:38:341 : w ap 0 reg 2 R2 0x0000000011:11:38:341 : w ap 0 reg 3 R3 0x0000000011:11:38:342 : w ap 0 reg 4 R4 0x0000000011:11:38:342 : w ap 0 reg 5 R5 0x0000000011:11:38:343 : w ap 0 reg 6 R6 0x0000000011:11:38:343 : w ap 0 reg 7 R7 0x0000000011:11:38:343 : w ap 0 reg 8 R8 0x0000000011:11:38:343 : w ap 0 reg 9 R9 0x0000000011:11:38:343 : w ap 0 reg 10 R10 0x0000000011:11:38:343 : w ap 0 reg 11 R11 0x0000000011:11:38:343 : w ap 0 reg 12 R12 0x0000000011:11:38:344 : w ap 0 reg 13 SP 0x0000000011:11:38:344 : w ap 0 reg 14 LR 0x0000000011:11:38:344 : w ap 0 reg 15 PC 0x2000000911:11:38:344 : w ap 0 reg 16 xPSR 0x0100000011:11:38:344 : w ap 0 reg 17 MSP 0x0000000011:11:38:344 : w ap 0 reg 18 PSP 0x00000000 As you can see, after the step 11:11:38:338 : w ap 0 reg 15 PC (0x20000000)11:11:38:338 : w ap 0 reg 17 MSP (0x20000500)11:11:38:338 : w ap 0 reg 16 xPSR (0x01000000) a step is missing where the code is actually loaded in MCU ram at address 0x2000 0004. If I try to select other external loaders in the list, those, for example, developed for STM32H7 MCUs, the result is the same.Instead, for a few other loaders, for example N25Q256A_STM32L476G-EVAL loader, the code loading step is actually done (in red): 11:20:26:349 : w ap 0 reg 15 PC (0x20000000)11:20:26:349 : w ap 0 reg 17 MSP (0x20000500)11:20:26:349 : w ap 0 reg 16 xPSR (0x01000000)11:20:26:354 : w ap 0 @0x20001680 : 0x00000200 bytes, Data 0x00000000...    11:20:26:354 : w ap 0 @0x20000000 : 0x00000004 bytes, Data 0x0000BE00...11:20:26:392 : w ap 0 @0x20000004 : 0x00001258 bytes, Data 0xB085B500...11:20:26:392 : Loader read...11:20:26:392 : Init flashloader...I've done another test: if I try to use the CubeProgrammer software with another board equipped with STM32H735 MCU, regardless of the external loader selected, the code is ALWAYS loaded in ram.I'm asking for your help and hints.Anybody knows the reason of this weird behaviour?Am I missing anything or making some mistakes?Thank you very much.

LorVec81 · Accepted Answer

Previously I forgot to mention that I've already tested all the functions in debug in user space and everything worked correctly, sorry.

Anyway in the meantime I've done other tests and actually I confirm that it seems a stack overflow issue.

Infact I've drastically simplified the spif driver, trying to reduce the nested calls of the functions and so it works also from CubeProgrammer: I've been able to read the correct data and to erase the chip.

Now I will do deeper tests and, above all, I'll set up an IDE project with objects allocated in the memory mapped space of the spi flash memory (0x9000 0000) to verify the write functionality of the external loader also from the debug launcher of the IDE.

I will let you know.

Thank you very much in the meantime.

Tesla DeLorean · Answer

Likely related to the structuring of the .ELF file (STLDR), could perhaps review with things like OBJCOPY or FROMELFMX25L4006E_STM32WL5M-SUBG.stldr  loads at 0x20000004, but only takes about 11 KB

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded