[VSC-1596] add idf.jtagFlashCommandExtraArgs to modify jtag flash behaviour

[brianignacio5]

Description

Add idf.jtagFlashCommandExtraArgs configuration setting to allow customization of OpenOCD JTAG flash command.

Please review https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/api-guides/jtag-debugging/index.html#upload-application-for-debugging for possible arguments to use.

Fixes #1437

Type of change

• New feature (non-breaking change which adds functionality)

Steps to test this pull request

Provide a list of steps to test changes in this PR and required output

1. Open a ESP-IDF project and set in .vscode/settings.json a new setting idf.jtagFlashCommandExtraArgs; ["verify", "reset"] or using the vscode settings UI.
2. Execute ESP-IDF: Flash (with JTag). The flashing arguments should be used in the Flash task.
3. Observe results.

• Expected behaviour:

JTAG flash arguments can be customized.

• Expected output:

OpenOCD command will include customize JTAG flash arguments.

How has this been tested?

Test Configuration:

• ESP-IDF Version: 5.3.1
• OS (Windows,Linux and macOS): macOS

Checklist

• PR Self Reviewed
• Applied Code formatting
• Added Documentation
• Added Unit Test
• Verified on all platforms - Windows,Linux and macOS

[github-actions]

Download the artifacts for this pull request:
You can test these changes by installing this VSIX by click menu View -> Command Palette..., type Install from VSIX and then select downloaded esp-idf-extension.vsix file to install the extension.

• esp-idf-extension.vsix.zip
  Espressif documentation preview

[radurentea]

LGTM

[Fabricio-ESP]

The parameters are correctly being added to the flash command.
Noticed that when using "exit", Open OCD is correctly closed after flash is completed, but an error is displayed in VSCode, it might be needed to better handle the process termination.

Error from error log:
{"user":true,"message":"Failed to flash the device (JTag), please try again [got response: '', expecting: '0']","stack":"Error: JTAG_FLASH_FAILED\n at Ba (\dist\extension.js:2:1692958)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at jp (\dist\extension.js:2:1923417)\n at \dist\extension.js:2:1916893","level":"error","timestamp":"2025-03-13T18:49:50.963Z"}

[erhankur]

There are two ways to handle flash programming completion:
1 - with exit option.

if {$exit == 1} {
    shutdown    # OpenOCD process ends, telnet connection closes
}
return 0

• OpenOCD main() returns 0
• Extension needs to start new OpenOCD process for the next operation

2- Using return 0 (without exit):

if {$exit == 1} {
    shutdown
} 
return 0  # OpenOCD continues running, telnet connection stays open. This is the case you covered.

I think, to cover exit, you also need to check if OpenOCD is still alive and if the process return code is zero.

[brianignacio5]

I've fixed the exit command handle @Fabricio-ESP PTAL again.

[Fabricio-ESP]

Looks good now!
Thanks.