Manage Solution dialog doesn't show per core telnet options (anymore)

[jreineckearm]

Type: Bug Report

Describe the bug

• OS and Version:
• VS Code Version:
• Extension Version: 1.62.2-81-g84039b4 (one of today's main builds)
• Target Device:
• Other extensions you installed (and if the issue persists after disabling them):
• A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Load example from here https://github.com/Arm-Examples/cmsis-mlek-examples/tree/main/Alif/AppKit_D3/MLEK_AV_DualCore
2. Open "Manage Solution Dialog"
3. I would have expected to see Telnet settings per core (here two). But I only see a single setting

See the same for all the CMSIS-DAP flavors I tried and for J-Link.
I am certain I had seen the per core selection in previous dev builds. Must have gotten lost somewhere late last week...or the debug-adapters.yml is broken. But I can't see anything obvious there.

Note: At the end, valid settings per core end up in *.cbuild-run.yml. And they all carry the same mode value as selected in GUI. But I cannot have different settings for different cores.

Expected behavior

Telnet (mode) settings per core (here two).

Code sample and logs

• Code sample
• tasks.json

Screenshots

Additional context

[jreineckearm]

Bit more investigation: it looks like this works better for other examples. For example an NXP FRDM-MCXN947 dual-core example.
Maybe related to the device specific parts in the not working example coming through board layer yml files?

[arneschmid]

Right now, we only look at the 'device:' tag within the projects referenced from the csolution.yml. We need to evaluate on how this information can be reliably merged from different locations.

[jkrech]

Note that the same is true for the display of the projects. There it is also not displayed which processor core a project is targeted for. The underlying reason is that the device: node from clayer.yml files are not considered for collecting used cores.