Dear All,
I am sharing the log from STM32cubeide and STM32cubeprogrammer. I need your help to figure out what went wrong. after debugging
I face this problem of not being able to connect to stm32wl. So I "full chip erase" is only option, then I being able to connect. Using ST Link V2 and STM32WLxx MCU.
I'm just using these toolchain for 1 week only.
-------------------------------------------------------------------
STM32CubeProgrammer v2.14.0
-------------------------------------------------------------------
Log output file: C:\Users\hp\AppData\Local\Temp\STM32CubeProgrammer_a17580.log
ST-Link Server is running on port : 7184
ST-LINK SN : 13002900130000544141514E
ST-LINK FW : V2J42S7
Board : --
Voltage : 3.24V
SWD freq : 950 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x497
Revision ID : Rev Y
Device name : STM32WLxx
Flash size : 256 KBytes
Device type : MCU
Device CPU : Cortex-M4
BL Version : 0xC4
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a17580.srec
File : ST-LINK_GDB_server_a17580.srec
Size : 76.78 KB
Address : 0x08000000
Erasing memory corresponding to segment 0:
Erasing internal memory sectors [0 38]
Erasing memory corresponding to segment 1:
Erasing internal memory sector 124
Download in Progress:
File download complete
Time elapsed during download operation: 00:00:03.634
STMCubeProgrammer Log:
11:01:04 : UR connection mode is defined with the HWrst reset mode
11:01:04 : ST-LINK SN : 13002900130000544141514E
11:01:04 : ST-LINK FW : V2J42S7
11:01:04 : Board : --
11:01:04 : Voltage : 3.25V
11:01:04 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
