Can't program/connect STM32WL55CC unless Hot Plug, why?

Hi @LEdou.1​,

seeing the OB values would help with accurate reply. STM32WL is dual core, with some aspects of the TrustZone features (not really TrustZone, but quite a lot in common). In this sense, the M4 core is regarded as non-secure and the M0+ core is the "secure". If the product is configured for secure boot with M0+ core, it's impossible to connect normally, only hot-plug. Then the M0+ security protection will also prevent mass erase.

But you may still attempt regression to wipe the MCU.

BR,

J

Ok thanks !

Here this what I have on OB Menu. RDP is set to 00, on SDK we have AA.

If i try to change to AA, STM32CubeProgrammer get stuck and crash on Linux (version v2.12.0) and STLIN-V3MINIE (version V3J10M3 STM32 Debug + VCP)

I have never program it, and all my board are in this state.

Hi @LEdou.1​,

the OB don't look healthy. It looks like the tools read all zeroes, which is not a default state and not even a valid state.

You are correctly trying to get the RDP to 0xAA value, this should normally trigger the regression and put the product to RDP0. Reading 0 in the RDP OB should be interpreted as RDP level 1, which should allow regression. I'm not aware of any exception.

I never encountered a situation where the STM32CubeProgrammer would crash, so this is really unknown territory for me. In your place it'd probably try using alternative tools. For example STlink v2, Windows machine, even the legacy ST-link Utility, the predecessor of STM32CubeProgrammer should support STM32WL (but probably not stlink v3).

Then there is possibility that you received defective or even counterfeit parts.

BR,

J