2025-10-09 3:04 PM
The "Discover" button on the STM32CubeProgrammer fails to connect to my my STM32H56x (STM32H562VGT6) in the Closed state (0x72). The instructions I followed for enabling password security are in the "How to enable RDP-like product state flash protection in STM32H5 microcontrollers" post. No errors came up in following these steps. To summarize my steps:
1. Installed STM32CubeProgrammer and STM32TrustedPackage Creator
2. Generated OBKey and password.bin files from DA_ConfigWithPassword.xml
3. Set PRODUCT_STATE to Provisioning (0x17) and executed "Start Provisioning" with the generated .obk file
4. Set PRODUCT_STATE to Closed (0x72)
The issue arises when going to perform a regression. In the Debug Authentication window, clicking the "Discover" button does not prompt me to select a password file and throws an error that states "Failed to communicate with target !". The Debug Authentication sequence does not start.
The same error occurs whether or not my ST-Link V2 is physically attached to the board, so I've confirmed that the error does happens when the debugger is connected to the MCU. I've additionally done the same methods on a second board and found the same problem with a second board.
Does anyone know how I can fix this error and use debug authentication to connect my boards? Any assistance would be appreciated.
2025-10-14 2:03 AM - edited 2025-10-14 2:04 AM
Hello @mmtimmerman and welcome to the Community,
Please share more details: the log file and STM32CubeProgrammer version used.
Maybe you have installed 32 bits version of STM32CubeProgrammer!
As mentioned in the STM32CubeProgrammer errata 2.20.x, Debug authentication is not supported on Windows 32 bits. Could you check with 64 bits version?
You can also refer to this application note that may help you: Getting started with debug authentication (DA) for STM32 MCUs
2025-10-15 7:34 AM
Hello,
In addition to what @Imen pointed out, make sure reset pin is properly connected between ST-LINK and target.
Aziz