Hello everyone,
I’m currently facing a blocking issue with SWD programming on an STM32U575VIT6Q placed on a custom PCB.
Until today everything worked correctly: I use a CLI-based flashing procedure that programs a set of binary files (around a dozen) using commands like the following:
%CLI_EXEC% -vb %VERBOSITY% -c port=swd dLPM -w "filename" %address% -v
The entire flashing sequence has always completed successfully, but during the last programming cycle I suddenly received the following error:
Error: Cannot connect to access port 0!
If you are trying to connect to a device with TrustZone enabled please try to connect with HotPlug mode.
If you are trying to connect to H5 device and your target is already locked with password or certificate, please open your device using Debug Authentication.
Since that moment, I have been completely unable to connect to the MCU with my ST-Link V2 in any mode.
I tried:
Normal
Under Reset
Hot Plug
Power-down
Unfortunately, all attempts fail with the same error.
A few details that may help:
TrustZone was never enabled on this device.
I never configured PCROP or any type of Flash/OB protection.
The same programming script works flawlessly on an STM32U585 placed on another custom PCB (pretty much similar to the current one).
- STM32CubeProgrammer v2.19.0
At this point the device seems completely inaccessible over SWD.
Has anyone experienced similar behavior, or can suggest how to recover the MCU?
What would be the recommended procedure when Debug Authentication is mentioned even though no protection was intentionally set?
Any help would be greatly appreciated.
Thanks in advance.
