Where is the "Debug Authentication" ?

[MQi.1]

I used a MB2032-WB09-B02 on MB1801D for several times, flash in CubeIDE was always OK, though debug prompted error read data every time, then the next day when I used it again, it didn't work, I couldn't flash image into neither in IDE nor Prog, the prompt:

my question is: how to discovery using Debug Authentication?

[Imen.D]

Hello @MQi.1 ,

Check the solder-bridges and jumpers positions (JP2 ON, JP1 on USB_STLK [1-2] on the MB1801 board.)

Switch SW1 should be on the 3V3 power supply (switch on position [1-2]) on the MB1801 board.

Make sure to follow the settings described in the UM3345 STM32WB09 Nucleo-64 board (MB1801 and MB2032) in Getting started section and Table 12. Solder bridges for MB1801.

[MQi.1]

In page 9 of "UM3345 STM32WB09 Nucleo-64 board (MB1801 and MB2032)", when MB2032 is upper (Type-C under Reset key), JP1 is on [1, ?], this the default location when I got this board kit (MB1801 + MB2032), while the note is "5V_STLK" not "USB_STLK", and there is also a "VBUS_STLK" on right side, is that right ? I mean is there an error in UM3345 ? Since when I could flash before, I have never find the board before Bluetooth pairing stably, I changed the TX power to MAX (0x1F) as it was told here - page 167 of AN5207 (Tx power level).

[MQi.1]

I identified the settings described in UM3345, the first 2 items is OK, for item 3 and 5, I didn't use ST Bluetooth® Low Energy sensor mobile application on a Bluetooth® Low Energy compatible mobile device from the App Store or Google Play, I just turn on Bluetooth on the mobile phone and want to find the WB09KE, did this matter?

[MQi.1]

On page 39 of UM3345:

Jumper connects 2 and 1: The bootloader is activated and the user can download a new application.

I got this:

[Imen.D]

Hi @MQi.1 

Please update and try with the latest release of STM32CubeProgrammer.

Check that you are using the pins that are supported by the bootloader, as described in AN2606 : STM32 microcontroller system memory boot mode - Application note.

Try to mass erase the device with STM32CubeProgrammer before debug.