[VSC-1213] Enhance flash encryption

[radurentea]

Description

Added check for SDK config modifications for encryption.

Fixes #1067

Type of change

• Bug fix (non-breaking change which fixes an issue)
• This change requires a documentation update

Steps to test this pull request

1. Open a project
2. Use "ESP-IDF: SDK Configuration editor (menuconfig)
3. Enable "Enable flash encryption on boot (READ DOCS FIRST)"
4. Build and Flash project with UART
5. Flash should be successful and the task should contain the --encrypt flag
   EX:

Executing task: C:\xxxxx.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe c:\xxxxxx\esp-idf-v5.0.1\components\esptool_py\esptool\esptool.py -p COM5 -b 460800 --before default_reset --after no_reset --chip esp32s3 write_flash --flash_mode dio --flash_freq 80m --encrypt --flash_size 16MB 0x0 bootloader/bootloader.bin 0x20000 app.bin 0x8000 partition_table/partition-table.bin

Test Configuration:

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

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]

This PR is not ready to be tested / code reviewed:

• we need to add validation for JTAG flashing (by default when flash encryption is enabled, an efuse is burnt that will disable JTAG flashing on the device), in case JTAG is disabled and user tries to flash via JTAG we need to catch this error and handle it properly.
• we need to modify the flash encryption documentation

[github-actions]

Pull request has been marked as stale since there are no activities, and this will be closed in 5 days if there are no further activities

[radurentea]

Hi @brianignacio5, Please take another look for the new commits in regards to the error handling of JTAG Flash when efuses are burnt

[brianignacio5]

Some changes

[radurentea]

Hi @brianignacio5 PTAL, I've made the modifications you've requested

[brianignacio5]

Some changes regarding deprecating idf.adapterTargetName and moving to docs_espressif documentation.

[radurentea]

Hi @brianignacio5,

Thank you for the code review! I've done the changes you've requested.

Please take another look.

[brianignacio5]

The readSummary function takes some time to load and the user doesn't see any information until it is completed. Suggestion wrapping this function into

vscode.window.withProgress(
  {
    cancellable: true,
    location: ProgressLocation,
    title: "ESP-IDF: Checking encryption eFuse...",
  },
  async (
    progress: vscode.Progress<{
      message: string;
      increment: number;
    }>,
    cancelToken: vscode.CancellationToken
  ) => {}
);

Tested using esp32 Core board using esp-idf v5.4 with flash_encryption example.

Otherwise LGTM