I was able to program two Nucleo-WBA52CG using STM32CubeIDE and the on board ST-Link. I programmed them with the BLE_HeartRateThreadX example application. When I power them I can see the BLE_HeartRateThreadX BLE traffic on my phone. However, I can not reprogram them again using the same setup. I suspect the problem is simple but I really have no idea what is wrong. Any help is appreciated. I get the error below when I try to program them.
------ Switching to STM32CubeProgrammer -----
[36m[01m -------------------------------------------------------------------
[39;49m[36m[01m STM32CubeProgrammer v2.13.0
[39;49m[36m[01m -------------------------------------------------------------------
[39;49m[39;49m
[39;49m[39;49mLog output file: /tmp/STM32CubeProgrammer_dw6pY8.log
[39;49m[00;31mError: Unable to connect to the target device, Access port is not valid.
[39;49mEncountered Error when opening /home/blue/.eclipse/com.st.stm32cube.ide.mcu.rcp.product_1.10.1_139059409_linux_gtk_x86_64/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.linux64_2.0.600.202301161003/tools/bin/STM32_Programmer_CLI
------ Switching context -----
Error in STM32CubeProgrammer
GDB session terminated: Client connection lost
GdbSessionManager, session terminated: 1
GDB session terminated: Client connection lost
GdbSessionManager, session terminated: 2
GdbSrv, last session terminated, signal dispose
Stopping port 61234
Received stop for port 61234, not accepting new connections.
GdbSrv, deInit entry.
Shutting down...
GdbSessionManager, deInit entry.
GDB session disposed: 2
GDB session disposed: 1
GdbSessionManager, deInit exit
SwvSrv deInit entry
Stopping port 61235
Received stop for port 61235, not accepting new connections.
SwvSrv deInit exit
Stm32Device, closeDevice() entry
Stm32Device, closeDevice() exit
Stm32Device, deInit success
GdbSrv, deInit exit.
Exit.
