Hello all
we have recently recevied several NUCLEO-WL33CC1 boards, equipped with the brand new STM32WL33 wireless MCU.
The problem we are facing is very strange: we can't connect to the board after some operation.
we have created a new project with Cube MX 6.13 for STM32WL33CCVx, and then we configured only the clock tree.
The idea was to try different stop modes and measure the current consumpion using NUCLEO JP2 jumper.
We did these steps:
- created a new project in CubeMx selecting STM32WL33CCVx target
- enabled HSE oscillator and configured the clock tree in this way:
- thus we obtained this simple configuration:
- generated the code from the .ioc file
- opened the project with CubeIDE and start a debug session, which perfectly worked
- measured the current concumption in run, in pause and in reset
- modifyed the main.c to enter the deep stop mode (with deep_stop_mode_2 bit set), adding these only two lines just after the while(1):
MODIFY_REG_FIELD(PWR->DBGR, PWR_DBGR_DEEPSTOP2, 1); // enables debug while in Deep Stop Mode
HAL_PWR_EnterDEEPSTOPMode();
- compiled the new code and tried to start a new debug session, which didn't work.
Practically, from when we program the .ioc auto-generated code into the STM32WL33 MCU, we are not able to connect to the MCU no more. Not even with the CubeProgrammer, which gives us the following output:
15:57:07 : STM32CubeProgrammer API v2.18.0 | Windows-64Bits
15:57:08 : UR connection mode is defined with the HWrst reset mode
15:57:08 : ST-LINK SN : 004300413433511137363934
15:57:08 : ST-LINK FW : V3J15M7B5S1
15:57:08 : Board : NUCLEO-WL33CC
15:57:08 : Voltage : 3.31V
15:57:08 : Error: Unable to read device id from ROM table
15:57:08 : SWD freq : 8000 KHz
15:57:08 : Connect mode: Hot Plug
15:57:08 : Reset mode : Hardware reset
15:57:08 : Error: Unable to read device id from ROM table
15:57:08 : Error: Cannot identify the device
We tired the same steps with another board with the same result.
Any help will be extremely appreciated
thank you all
regards
Pierpaolo
