NUCLEO-WL33CC1 Connection to CubeIDE

[Dobry]

Hello,

I am using different ST MCUs from few years and already have a wide set of development boards, tools and JTAG emulators and so far did not experienced any troubles to attach new board (even custom made) to CuveIDE and to flash and debug my solutions... until this week.

I've deceded to get some more experience in low power SubGHz solutions from ST and ordered two NUCLEO-WL33CC1 development boards (Mouser store) and also some Chinese modules based on STM32WL33 (AliExpress).

Now I have few different STM32WL33 based boards and 3 different available debug interfaces - J-LINK (stand-alone), ST_LINK V2 (stand-alone) and ST_LINK V3 (embedded in NUCLEO-WL33CC1).

The problem is that there is no any combination of boards and JTAGs that can connect to STM32CubeIDE.

So far there is only one partial success - Using STM32CubeProgrammer + ST_LINK V2 and Chinese modile - I can connect, flash and verify some ELF file: 

08:47:13 : UR connection mode is defined with the HWrst reset mode
08:47:13 : ST-LINK SN : 16004A002933353739303541
08:47:13 : ST-LINK FW : V2J46S7
08:47:13 : Board : --
08:47:13 : Voltage : 3.20V
08:47:13 : SWD freq : 4000 KHz
08:47:13 : Connect mode: Under Reset
08:47:13 : Reset mode : Hardware reset
08:47:13 : Device ID : 0x027
08:47:13 : Revision ID : Rev A
08:47:13 : Debug in Low Power mode is not supported for this device.
08:47:14 : UPLOADING OPTION BYTES DATA ...
08:47:14 : Bank : 0x00
08:47:14 : Address : 0xf9f9f9f9
08:47:14 : Size : 4 Bytes
08:47:14 : UPLOADING ...
08:47:14 : Size : 32768 Bytes
08:47:14 : Address : 0x10040000
08:47:14 : Read progress:
08:47:14 : Data read successfully

The same attempts on STM32CubeIDE gives no success:

STMicroelectronics ST-LINK GDB server. Version 7.13.0

Copyright (c) 2026, 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.22.0

-------------------------------------------------------------------

Log output file: C:\Users\ddenchev\AppData\Local\Temp\STM32CubeProgrammer_a37840.log

ST-LINK SN : 16004A002933353739303541

ST-LINK FW : V2J47S7

Board : --

Voltage : 3.20V

Error: ST-LINK error (DEV_TARGET_RESET_ERR)

Encountered Error when opening F:\ST\STM32CubeIDE_1.19.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.400.202601091506\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Shutting down...

Exit.

Whentrying the same test with NUCLEO-WL33CC1 board, it still fails, but in slightly different way.

With Programmer: 

09:47:19 : UR connection mode is defined with the HWrst reset mode
09:47:19 : ST-LINK SN : 002C00413433511137363934
09:47:19 : ST-LINK FW : V3J17M10B6S1
09:47:19 : Board : NUCLEO-WL33CC
09:47:19 : Voltage : 3.29V
09:47:19 : Error: Unable to get core ID
09:47:19 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication

With CubeIDE:

With CubeIDE:STMicroelectronics ST-LINK GDB server. Version 7.13.0

Copyright (c) 2026, 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

Target no device found

Error in initializing ST-LINK device.

Reason: No device found on target.

A'we updated all tools to the latest available version - no improvements.

Tried also different FW versions of ST_LINK V2 and V3 - no improvements.

Also tried different connection speeds and reset behavior options - no any success to connect any of these boards to STM32CubeIDE.

The last tests that I did were to try the same on different computers and also on Linux Ubuntu OS - behavior is the same as on my Windows11 work machine.

I did not expected that official development board with embedded debug interface will not be able to connect to ofiicial developmen environment, so may be there is something specific for STM32WL33 MCU that I am missing and that blocking my work.

Any ideas or advices are very welcome.

Best Regards,

Dobry

[mƎALLEm]

Hello @Dobry ,

It seems that this was a known limitation and the workaround is to use ST-LINK (OpenOCD) option.

So in your project, change the Debug probe config from ST-LINK GDB server to ST-LINK OpenOCD setting:

Normally it should work .. I tested it. 

Home that helps.

[Dobry]

Hello mƎALLEm,

Thank you for these suggestions, but unfortunately these still does not resolving my connection problems.

I already did a lot of experiments with different debbuger options and ports, including test with different configuration scripts, but I am still unable to connect to NUCLEO-WL33CC boards.

When trying to connect in Cube IDE environment I am getting the following error message:

 ... so I tried again with the STM32Programmer tool... again without success. In Programmer tool there are no debug options, to choose, but it is clearly visible that the embedded ST_LINK V3 is unable to connect to the tartget. I am not sure is this meanigfull, but on every next attmpt to connect, the error messages alters:

 

In the same time, with my custom made board and ST_LINK V2 I am able to connect with STM32_Programmer and to flash my executable. The same still does not work with CubeIDE, but if I disable code download, I am able to start debug session with GDB and to trace the code flashed with Programmer tools:

 

For me it still looks like a big mess with used configuration scripts for Programmer and CubeIDE, but it is hard to prove it without investing huge effort to track down and understand all used scripts and parameters... Fortunately I found a semi working combination of debug interface and board configuration that proves that my boards are alive... And still can't believe that the official development board and official development environment does not work out of the box with official examples...

Do you know are there any planed release updates for CubeIDE and Programmer tools r1elated to WL33xx MCUs?

Best Regards,

Dobry. 

[mƎALLEm]

Hello,

I suspect you have a hardware issue ...which is not obvious for me to determine.

The workaround I suggested is proposed by the dev team and it worked from my side and I don't have issues with CubeProgrammer (with the latest version 2.22.0) at all.

Check your default jumpers, the solder bridges, etc .. Try also to update your STLINK firmware. Try the same thing with another PC ..

[Dobry]

Hello mƎALLEm,

The both NUCLEO-WL33CC dev boards that I have are ordered from Mouser e-store, so it is supposed to be authentic and verified. At one of these boards I've removed the MCU shield and verified the JTAG signals on the MCU pins - everyrhing seems to be correctly routed and the power supply is presented as well, but no any success with JTAG connection. 

Do you think there is some chance the both MCUs to be somehow locked during all these unsuccessfull JTAG connection problems?

I am planning to do another experiment - to remove MB2029B board and to try to use MB1801D as generic ST_LINK V3 debug interface and to connect to my custom STM32WL33 board. If this test succeed - will prove that the JTAG itself is functional and the connection problems are caused by MB2029B boards.

Unfortunately these tests will not help with the semi-functional CubeIDE - Currently it is used to build the project, flashing is done by STM32_Programmer tool and debugging is done again with CubeIDE, with desabled code dounload.

Best Regards,

Dobry. 

[Dobry]

Just did the proposed experiment - removed MB2029B board and connected jump wires to CN3 of MB1810D:

CN3-8 -> GND

CN3-9 -> SWDIO

CN3-11 -> SWCLK

With this configuration, the STM32_Programmer tool is able to connect to my custom STM32WL33 board, so there seems to be some problem(s) with MB2029B boards... Either some configuration related to te powering/clocking/resetting, either both MB2029B are somehow locked for JTAG connection, either the both MB2029B are damaged...

I did also experiment to use the MB1801 board as a ST_LINK V3 interface and to try to debug my custom STM32WL33KC board with CubeIDE. The weird think is that if I try to debud project for STM32WLCC I am able to connect and debug it:

Open On-Chip Debugger 0.12.0+dev-00645-g2306f32ee (2026-02-09-11:36) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J17M10B6S1 (API v3) VID:PID 0483:3753
Info : Target voltage: 3.295808
Info : clock speed 8000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x0bc11477
Info : [STM32WL33CCVx.cpu] Cortex-M0+ r0p1 processor detected
Info : [STM32WL33CCVx.cpu] target has 4 breakpoints, 2 watchpoints
Info : [STM32WL33CCVx.cpu] Examination succeed
Info : starting gdb server for STM32WL33CCVx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 (UNDEFINED) - target needs reset
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 (UNDEFINED) - target needs reset
Error: [STM32WL33CCVx.cpu] DP initialisation failed
[STM32WL33CCVx.cpu] halted due to breakpoint, current mode: Thread
xPSR: 0xf1000000 pc: 0x100017c0 msp: 0x20008000
Info : Padding image section 0 at 0x10041d48 with 8 bytes (bank write end alignment)
Error: [STM32WL33CCVx.cpu] DP initialisation failed
[STM32WL33CCVx.cpu] halted due to breakpoint, current mode: Thread
xPSR: 0xf1000000 pc: 0x100017c0 msp: 0x20008000

but if the project is for STM32WLKC, it is still failing:   

Open On-Chip Debugger 0.12.0+dev-00645-g2306f32ee (2026-02-09-11:36) [https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V3J17M10B6S1 (API v3) VID:PID 0483:3753
Info : Target voltage: 3.297405
Info : clock speed 8000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x0bc11477
Info : [STM32WL33KCVx.cpu] Cortex-M0+ r0p1 processor detected
Info : [STM32WL33KCVx.cpu] target has 4 breakpoints, 2 watchpoints
Info : [STM32WL33KCVx.cpu] Examination succeed
Info : starting gdb server for STM32WL33KCVx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 (UNDEFINED) - target needs reset
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 (UNDEFINED) - target needs reset
Error: [STM32WL33KCVx.cpu] DP initialisation failed
[STM32WL33KCVx.cpu] halted due to breakpoint, current mode: Thread
xPSR: 0xf1000000 pc: 0x100017c0 msp: 0x20008000
Info : Padding image section 0 at 0x10046234 with 12 bytes (bank write end alignment)
Error: timed out while waiting for target halted
Error: error waiting for target flash write algorithm
Error: error writing to flash at address 0x10040000 at offset 0x00000000
Error: [STM32WL33KCVx.cpu] DP initialisation failed
[STM32WL33KCVx.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x100017c0 msp: 0x20008000
Info : dropped 'gdb' connection
shutdown command invoked
Info : dropped 'gdb' connection

Best Regards,

Dobry.