Unable to detect my device with on-board Nu-Link2-Me debugger

[ucSec]

Type: Bug Report

Describe the bug

• OS and Version: Windows 11
• VS Code Version: 1.96.4
• Extension Version: 1.13.1 updated in 2024-12-21
• Target Device: NuMaker UNO with chip NUC131SD2AE and on-board Nu-Link2-Me debugger
• Other extensions: Arm Keil Studio Pack
• Description: Plug in the board, but no devices found in Device Manager. Reboot and reload of VSCode and workplace tried. No other IDEs or related software open when testing. Device works fine with Keil uVision. Firmware of the debugger is updated. The device is detected as COM7 in Windows' Device Manager. Other devices with CMSIS DAP works fine.

To Reproduce
Steps to reproduce the behavior:

1. Create a new project for chip NUC131SD2AE with Arm Keil Studio Pack.
2. Build the project
3. Go to Device Manager in sidebar.
4. See error

Screenshots

Additional context
Assuming that the Nuvoton Nu-Link2-Me is not supported. Not sure where to check supported debuggers.

[thegecko]

Thanks for raising this issue.

Would you mind outlining the following:

• Is the picker empty when you click Add Device (with your board attached)?
• What happens if you change the allow all devices option in the settings for the device manager extension?
• Can you share the PID and VID of your device?

[ucSec]

Hi! Thanks for your reply.

• After I have my board connected, when I click Add Device:
  

• After check Manage All Devices:
  
  Which is obviously not my device.

• PID and VID shown in Windows' Device Manager:
  

• Considering a few issues about the unsupported J-Link, I wonder whether Nu-Link2-Me, which is the debugger I use, are supported.

[thegecko]

We can detect Nu-Link devices, but it seems in this case it isn't being detected correctly.
This isn't a target we actively support, so don't have access to devices for testing either.

I'll add the enhancement label to this issue for further invesrigation.

cc @jreineckearm @jkrech @KeilChris