OPENOCD not being closed after flash (VSC-1823)

[arturv2000]

OS

Windows

Operating System version

Windows 11

Visual Studio Code version

1.107.1

ESP-IDF version

5.4.1

Python version

3.11.2

Doctor command output

report.zip

Extension

esp_idf_vsc_ext.zip

Description

According to Pull Request #1601 after flashing device via JTAG, openOCD should close/terminate. That is not happening.

Log from the ESP.IDF output:

Info : PROF: Wrote 4096 bytes in 288.716 ms (data transfer time included)

** Programming Finished in 639 ms **
** Flashing done for phy_init_data.bin in 639 ms **
** Total programming time 32521 ms **

0

[/OpenOCD]
[Flash]
⚡️ Flashed Successfully (JTAG)
Flash has finished. You can monitor your device with 'ESP-IDF: Monitor command'
[/Flash]
[OpenOCD]
Info : [esp32s3.cpu0] Debug controller was reset.
Info : [esp32s3.cpu0] Core was reset.
Info : [esp32s3.cpu1] Debug controller was reset.
Info : [esp32s3.cpu1] Core was reset.
Info : [esp32s3.cpu0] Target halted, PC=0x40056F5C, debug_reason=00000000
Info : [esp32s3.cpu0] Reset cause (21) - (USB UART reset)
Info : [esp32s3.cpu1] Target halted, PC=0x40041A76, debug_reason=00000000
Info : [esp32s3.cpu1] Reset cause (21) - (USB UART reset)

Same behaviour using the Flash Device button or Build, Flash and Monitor button.

If using command palete to select ESP-IDF: Flash (with JTAG) output log slightly different but same behaviour (OpenOCD continues open/running):

** Programming Finished in 642 ms **
** Flashing done for phy_init_data.bin in 642 ms **
** Total programming time 
32605 ms **
0

[/OpenOCD]
[Flash]
⚡️ Flashed Successfully (JTAG)
Flash has finished. You can monitor your device with 'ESP-IDF: Monitor command'

Debug Message

Info : PROF: Wrote 4096 bytes in 290.413 ms (d
ata transfer time included)

** Programming Finished in 624 ms **

[/OpenOCD]
[Flash]
⚡️ Flashed Successfully (JTAG)
Flash has finished. You can monitor your device with 'ESP-IDF: Monitor command'
[/Flash]
[OpenOCD]
** Flashing done for phy_init_data.bin in 625 ms **
** Total programming time 32455 ms **
0

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.