VSCode DEBUG PROBES window not loading (white line scrolling right).

[buff]

This is on OS X, VSC ver: 26.6.57.  The DEBUG PROBES window is not detecting any probes (Segger at the moment).  This is for a freeform project which was functioning before I performed an upgrade.  I am looking for suggestions as to what to examine.  The probes are functioning outside of the VSCode extension.  I also have run MCUXpresso Installer as well (though the PEMicro server install always shows a spinning wheel, it did succeed in extracting the tar into ~/.mcuxpressotools/pemicrogdbserver - just an aside).

Useful info would be what/how the extension is attempting to interact with the debug tools.  I have attempted to supply tool locations in the extension settings, etc.  

Is the Debug Probes view controlled by the debug-tracker-vscode dependency?

There is a message visible briefly when this loads, something about no provider found.

[Habib_MS]

Hello @buff,
When you mentioned, "This is for a freeform project which was functioning before I performed an upgrade," could you please clarify what was upgraded?

In order to try a pinpoint if this solves the issue, could you perform the following tests?

-In the Debug Probes window, click Clean-up Debug and then click the Refresh button.

-Update the MCUXpresso Installer to the latest available version. You can follow the steps described in the Package and Component Status, Version, and Updates section.

-Reinstall the SEGGER J-Link Software Pack from the MCUXpresso Installer.

Also, could you please provide me which device are you currently using? Is one of our EVKs or is a custom board?

BR
Habib

[buff]

I was able to use Installer to update the tools and components.  Restarting VSCode now shows the DEBUG PROBES window contents.  Note I did launch VSCoce from both spotlight and a shell, both worked.  

[buff]

I deleted ~/.mcuxpressotools and MCUXpresso Installer at least isn't spinning checking for updates.  I will re-install the dependencies now.

[buff]

MCUXpresso Installer is at v26.03.  I first noticed this after upgrading and running the install.  I see v26.06 is now current, I will install that and see what's what.

* I installed v26.06.117 and upon launching it, I just see the spinning icons.  I will

I relaunched Installer via /Applications/MCUXpressoInstaller.app/Contents/MacOS/MCUXpressoInstallerCLI

to get more info.  Launching from MCUXpressoInstallerCLI from my default environment I see this spinning behavior.  When I relaunched from the GUI (OS X) a subsequent time the installer shows component status (installed, update available) with the exception of PEMicro.  

-In the Debug Probes window, click Clean-up Debug and then click the Refresh button.

In the VSCode DEBUG PROBES window there is nothing to click.  The message which popped up indicated that there is no 'provider' for the window.  This message shows up in all the windows when first launched then goes away as MCUXpresso finishes loading (with the exception of the DEBUG PROBES windows).  I guess I could blow away the MCUXpresso for VSCode extension and reinstall.

MCUXpressoInstallerCLI output once had this, might be hint for PEMicro:

verbose: Checking if MCUXpresso for VS Code is already installed...
info: MCUXpresso for VS Code already installed. Version: 26.6.57
^Cverbose: Checking if PEmicro is already installed...
info: Executing "/Users/bruff/.mcuxpressotools/pemicrogdbserver/pegdbserver_console --version"
info: zsh -c "source /Users/bruff/.zprofile && /Users/bruff/.mcuxpressotools/pemicrogdbserver/pegdbserver_console --version"
error: Command /Users/bruff/.mcuxpressotools/pemicrogdbserver/pegdbserver_console exited with code 1.
stdout: "P&E GDB Server for Arm(R) devices, Version 10.02.00.00
Copyright 2025, P&E Microcomputer Systems Inc, All rights reserved

Loading library /Users/bruff/.mcuxpressotools/pemicrogdbserver/gdi/unit_ngs_arm_internal.so ... Done.

Command line arguments: --version"
stderr: "Exception EControlC in module libsystem_kernel.dylib at 00007FF80629B3CA.
Control-C hit."
info: PEmicro not found.
Error occurred in handler for 'versionReport': Error: Could not get browser window handle
at new o (/Applications/MCUXpressoInstaller.app/Contents/Resources/app.asar/main.js:2:312914)
at o.getInstance (/Applications/MCUXpressoInstaller.app/Contents/Resources/app.asar/main.js:2:313215)
at r (/Applications/MCUXpressoInstaller.app/Contents/Resources/app.asar/main.js:2:313676)
at Rc (/Applications/MCUXpressoInstaller.app/Contents/Resources/app.asar/main.js:2:519204)
at async Session.<anonymous> (node:electron/js2c/browser_init:2:114068)