Cbuild setup complains about `trace` node under `debugger`

[jreineckearm]

Type: Bug Report

Describe the bug

• OS and Version: Windows 11 Enterprise
• VS Code Version: 1.104.2
• Extension Version: Internal build from main
• Target Device: Alif AE722F80F55D5LS
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is.

When I switch between a real HW device and an AVH target, I see some scenarios where refreshes seem to be missing.

To Reproduce
Steps to reproduce the behavior:

1. Clone https://github.com/Arm-Examples/cmsis-mlek-examples.git
2. Open subfolder Alif/AppKit_D3/MLEK_AV_DualCore in VS Code.
3. Update vcpkg-configuration.json to use CMSIS-Toolbox 2.11.0
4. Wait for setup to finish
5. Refresh through CMSIS view (...>Refresh (reload....) to get a valid cbuild-run file.
6. Open "Manage Solutions" dialog
7. Select "CMSIS-DAP" or "ULINKplus" (whatever gives you an active "Save" button) and click "Save"
   => This currently gives you a trace node under debugger. The following automatic refresh then complains during cbuild setup phase

Execute: cbuild setup ....\cmsis-mlek-examples\Alif\AppKit_D3\MLEK_AV_DualCore\mlek_dual.csolution.yml --active AE722F80F55D5LS --packs --update-rte
..../cmsis-mlek-examples/Alif/AppKit_D3/MLEK_AV_DualCore/out/mlek_dual+AE722F80F55D5LS.cbuild-run.yml:144:5 - error csolution: unexpected instance type

Completed: cbuild failed with exit code 1

Looks like a schema file needs updating? If I understand correctly, the debugger node should accept now any key-value pair.

Expected behavior

Code sample and logs

• Code sample
• tasks.json

Screenshots

Additional context

[brondani]

The vscode extension built from internal main uses the debug-adapter-registry also from main. Since its update Open-CMSIS-Pack/debug-adapter-registry#35 the trace node has a different structure than its placeholder in the cbuild-run schema released with the toolbox 2.11.0. It has been relaxed in Open-CMSIS-Pack/devtools#2218 and therefore the toolbox nightly build should cope with the issue.

Possible ways to re-synchronize the tools:

• change/rename trace in the debug-adapter-registry, impacting its handling in the extension.
• use the debug-adapter-registry from the installed toolbox instead of the main: maybe the best solution in the long run.
• release the toolbox together or right before the next vscode extension: probably the preferred solution for the time being.

[jkrech]

We are planning to release CMSIS-Toolbox 2.12.0 ahead of VSCode CMSIS Solution 1.62.
For the time being a manual installation of a nightly build of the CMSIS-Toolbox can be used

[jreineckearm]

Thanks, I tried in the meanwhile a nightly build and can confirm that this fixes the problem.

[ReinhardKeil]

@jreineckearm suggest to close this ticket, as (a) we will not promote trace for now, (b) the problem is fixed with Toolbox 2.12