ST-LINK utility connects normally and the target reacts as expected to its Run / Halt / System Reset buttons.
Clicking Run or Debug from Workbench causes the target to become unresponsive. The target recovers by subsequently reopening/connecting ST-LINK utility.
Reproducible using other targets and ST-LINK/V2s.
Is it known what can cause this?
ST-LINK utility output:
12:53:21 : ST-LINK SN : 54FF71067880565222080767
12:53:21 : ST-LINK Firmware version : V2J29S7
12:53:21 : Connected via SWD.
12:53:21 : SWD Frequency = 4,0 MHz.
12:53:21 : Connection mode : HotPlug.
12:53:21 : Debug in Low Power mode enabled.
12:53:22 : Device ID:0x442
12:53:22 : Device flash Size : 256KBytes
12:53:22 : Device family :STM32F091xB-xC/F098xC/F030xC
Workbench debug output:
Debug: 271 31 transport.c:239 handle_transport_init(): handle_transport_init
Debug: 272 31 hla_transport.c:152 hl_transport_init(): hl_transport_init
Debug: 273 31 hla_transport.c:169 hl_transport_init(): current transport hla_swd
Debug: 274 31 hla_interface.c:42 hl_interface_open(): hl_interface_open
Debug: 275 31 hla_layout.c:40 hl_layout_open(): hl_layout_open
Debug: 276 31 stlink_usb.c:2467 stlink_usb_open(): stlink_usb_open
Debug: 277 31 stlink_usb.c:2484 stlink_usb_open(): transport: 1 vid: 0x0483 pid: 0x3748 serial:
Error: 278 2560 stlink_usb.c:2555 stlink_usb_open(): read version failed
Debug: 279 2560 hla_layout.c:47 hl_layout_open(): failed
Debug: 280 2560 command.c:626 run_command(): Command failed with error code -4
User : 281 2560 command.c:687 command_run_line(): in procedure 'init'
in procedure 'ocd_bouncer'
Debug: 282 2560 command.c:626 run_command(): Command failed with error code -4
