FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problem flashing STM32WLE5J8I6, stuck at 97%

Cvan .7
Associate II

‎2022-05-04 01:37 AM

Hi all. I've got a problem when trying to flash the STM32WLE5J8I6.

I am trying to run a simple blinky code and blink an onboard LED on my custom pcb.

The program builds fine, connecting with the ST-Link (Nucleo-WL55JC1) and using SWD to connect to the STM32WLE5 works. However, when running or debugging, the program gets stuck at 97%. See picture.

0693W00000NpB6iQAF.png 

The following output is seen in the console:

STMicroelectronics ST-LINK GDB server. Version 6.1.0
Copyright (c) 2022, STMicroelectronics. All rights reserved.
 
Starting server with the following options:
        Persistent Mode            : Disabled
        Logging Level              : 1
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Disabled
        SWD Debug                  : Enabled
        InitWhile                  : Enabled
 
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.10.0                  
      -------------------------------------------------------------------
 
 
 
Log output file:   c:\users\cvan~1.aru\appdata\local\temp\stm32cubeprogrammer_a50996.log
ST-LINK SN  : 001D00083756501620303658
ST-LINK FW  : V3J9M3
Board       : NUCLEO-WL55JC
Voltage     : 3.28V
SWD freq    : 12000 KHz
Connect mode: Under Reset
Reset mode  : Hardware reset
Device ID   : 0x497
Revision ID : Rev Z
Device name : STM32WLxx

For some reason, when i terminate the console and thus the flashing, the console gets expanded to the following:

STMicroelectronics ST-LINK GDB server. Version 6.1.0
Copyright (c) 2022, STMicroelectronics. All rights reserved.
 
Starting server with the following options:
        Persistent Mode            : Disabled
        Logging Level              : 1
        Listen Port Number         : 61234
        Status Refresh Delay       : 15s
        Verbose Mode               : Disabled
        SWD Debug                  : Enabled
        InitWhile                  : Enabled
 
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
Debugger connected
Waiting for debugger connection...
      -------------------------------------------------------------------
                       STM32CubeProgrammer v2.10.0                  
      -------------------------------------------------------------------
 
 
 
Log output file:   c:\users\cvan~1.aru\appdata\local\temp\stm32cubeprogrammer_a50996.log
ST-LINK SN  : 001D00083756501620303658
ST-LINK FW  : V3J9M3
Board       : NUCLEO-WL55JC
Voltage     : 3.28V
SWD freq    : 12000 KHz
Connect mode: Under Reset
Reset mode  : Hardware reset
Device ID   : 0x497
Revision ID : Rev Z
Device name : STM32WLxx
Flash size  : 64 KBytes
Device type : MCU
Device CPU  : Cortex-M4
BL Version  : 0xc3
 
 
 
Memory Programming ...
Opening and parsing file: st-link_gdb_server_a50996.srec
  File          : st-link_gdb_server_a50996.srec
  Size          : 7.04 KB 
  Address       : 0x08000000 
 
 
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 3]
^CEncountered Error when opening C:\ST\STM32CubeIDE_1.8.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.200.202202231230\tools\bin\STM32_Programmer_CLI.exe
Error in STM32CubeProgrammer
Shutting down...
Exit.

Boot is pulled up, pulling it down makes it impossible to connect to the device using STM32CubeProgrammer.

Reset is internally pulled up. Only decoupled on the board itself.

Any hints into the right direction are highly appreciated.

edit:

See below for the generated log.

13:20:05:591       -------------------------------------------------------------------
13:20:05:592                        STM32CubeProgrammer v2.10.0                  
13:20:05:592       -------------------------------------------------------------------
 
13:20:05:592 
 
13:20:05:592 Log output file:   c:\users\cvan~1.aru\appdata\local\temp\stm32cubeprogrammer_a70928.log
13:20:05:592 Command line:  --connect port=SWD speed=fast mode=ur reset=hwrst --download "c:\users\cvan~1.aru\appdata\local\temp\st-link_gdb_server_a70928.srec" --log "c:\users\cvan~1.aru\appdata\local\temp\stm32cubeprogrammer_a70928.log"
13:20:05:592 
13:20:05:604 STLinkUSBDriver.dll loaded
13:20:05:604 STLinkUSBDriver.dll loaded
13:20:05:604 ST-LINK SN  : 001D00083756501620303658
13:20:05:604 ST-LINK FW  : V3J9M3
13:20:05:605 Board       : NUCLEO-WL55JC
13:20:05:605 Voltage     : 3.28V
13:20:05:613 SWD freq    : 12000 KHz
13:20:05:613 Connect mode: Under Reset
13:20:05:613 Reset mode  : Hardware reset
13:20:05:615 Device ID   : 0x497
13:20:05:616 Revision ID : Rev Z
13:20:05:622 Reading data...
13:20:05:622 r ap 0 @0x1FFF7550 0x00000004 bytes Data 0x000000FF
13:20:05:622 Database: Config 0 is active.
13:20:05:623 flash loader C:/ST/STM32CubeIDE_1.8.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.200.202202231230/tools/bin/FlashLoader/0x497.stldr is loaded
13:20:05:624 Reading data...
13:20:05:624 r ap 0 @0x1FFF7550 0x00000004 bytes Data 0x000000FF
13:20:05:624 Database: Config 0 is active.
13:20:05:624 Device name : STM32WLxx
13:20:05:624 Reading data...
13:20:05:625 r ap 0 @0x1FFF75E0 0x00000004 bytes Data 0xFFFF0040
13:20:05:625 Flash size  : 64 KBytes
13:20:05:625 Device type : MCU
13:20:05:625 Device CPU  : Cortex-M4
13:20:05:625 r ap 0 @0x1FFF3EFE 0x00000004 bytes Data 0x008800C3
13:20:05:625 BL Version  : 0xc3
13:20:05:625 
13:20:05:627 
 
13:20:05:627 Memory Programming ...
13:20:05:627 Opening and parsing file: st-link_gdb_server_a70928.srec
13:20:05:627   File          : st-link_gdb_server_a70928.srec
13:20:05:627   Size          : 6.91 KB 
13:20:05:627   Address       : 0x08000000 
13:20:05:627 
 
13:20:05:627 Erasing Segment <0> Address <0x08000000> Size <7076>Bytes
13:20:05:627 Erasing memory corresponding to segment 0:
13:20:05:627 Memory erase...
13:20:05:629 halt ap 0 
13:20:05:629 w ap 0 reg 15 PC   (0x20000000)  
13:20:05:630 w ap 0 reg 17 MSP  (0x20000500)  
13:20:05:630 w ap 0 reg 16 xPSR (0x01000000)  
13:20:05:632 w ap 0 @0x20001380 0x00000200 bytes Data 0x00000000
13:20:05:633 w ap 0 @0x20000000 0x00000004 bytes Data 0x0000BE00
13:20:05:641 w ap 0 @0x20000004 0x00000F54 bytes Data 0x0001B510
13:20:05:641 Erasing internal memory sectors [0 3]
13:20:05:641 Init flashloader...
13:20:05:642 halt ap 0 
13:20:05:643 w ap 0 reg 0 R0   0x00000001
13:20:05:643 w ap 0 reg 1 R1   0x00000000
13:20:05:644 w ap 0 reg 2 R2   0x00000000
13:20:05:644 w ap 0 reg 3 R3   0x00000000
13:20:05:644 w ap 0 reg 4 R4   0x00000000
13:20:05:645 w ap 0 reg 5 R5   0x00000000
13:20:05:645 w ap 0 reg 6 R6   0x00000000
13:20:05:645 w ap 0 reg 7 R7   0x00000000
13:20:05:646 w ap 0 reg 8 R8   0x00000000
13:20:05:646 w ap 0 reg 9 R9   0x00000000
13:20:05:647 w ap 0 reg 10 R10  0x00000000
13:20:05:647 w ap 0 reg 11 R11  0x00000000
13:20:05:647 w ap 0 reg 12 R12  0x00000000
13:20:05:648 w ap 0 reg 13 SP   0x00000000
13:20:05:648 w ap 0 reg 14 LR   0x20000001
13:20:05:648 w ap 0 reg 15 PC   0x2000002F
13:20:05:649 w ap 0 reg 16 xPSR 0x01000000
13:20:05:649 w ap 0 reg 17 MSP  0x20001354
13:20:05:649 w ap 0 reg 18 PSP  0x00000000
13:20:05:650 run ap 0 
13:20:05:650 halt ap 0 
13:20:05:651 r ap 0 reg 0 R0   0x00000001
13:20:05:651 Loader sector erase...
13:20:05:651 w ap 0 reg 0 R0   0x08000000
13:20:05:652 w ap 0 reg 1 R1   0x08001800
13:20:05:652 w ap 0 reg 2 R2   0x00000002
13:20:05:652 w ap 0 reg 3 R3   0x00000000
13:20:05:653 w ap 0 reg 4 R4   0x00000000
13:20:05:653 w ap 0 reg 5 R5   0x00000000
13:20:05:653 w ap 0 reg 6 R6   0x00000000
13:20:05:654 w ap 0 reg 7 R7   0x00000000
13:20:05:654 w ap 0 reg 8 R8   0x00000000
13:20:05:655 w ap 0 reg 9 R9   0x00000000
13:20:05:655 w ap 0 reg 10 R10  0x00000000
13:20:05:655 w ap 0 reg 11 R11  0x00000000
13:20:05:656 w ap 0 reg 12 R12  0x00000000
13:20:05:656 w ap 0 reg 13 SP   0x00000000
13:20:05:656 w ap 0 reg 14 LR   0x20000001
13:20:05:657 w ap 0 reg 15 PC   0x200007E9
13:20:05:657 w ap 0 reg 16 xPSR 0x01000000
13:20:05:658 w ap 0 reg 17 MSP  0x20001354
13:20:05:658 w ap 0 reg 18 PSP  0x00000000
13:20:05:658 run ap 0

Labels:
0 Kudos
3 REPLIES 3
Louis AUDOLY
ST Employee

‎2022-05-10 01:51 AM

Hello @Cvan .7​ ,

Do you have CubeProgrammer stand alone? If so, do you experience a problem with it?

If you look in C:\ST\STM32CubeIDE_1.8.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.200.202202231230\tools\bin\STM32_Programmer_CLI.exe directory, is the CLI.exe placed here ?

Best regards

Louis

0 Kudos
Cvan .7
Associate II
In response to Louis AUDOLY

‎2022-05-10 02:05 AM

Hi Louis,

First off, thanks for your help.

The ...CLI.exe is placed there.

0 Kudos
Louis AUDOLY
ST Employee
In response to Cvan .7

‎2022-05-12 02:49 AM

Hello @Cvan .7​ ,

Have you the same behavior with CubeProgrammer in stand alone ?

Regards

0 Kudos
Top