Forum Replies Created
-
Posts
-
Ok, got it. I was thinking about existing projects, especially hard-realtime designs, on which it is not possible to replace the debug framework – any semihosting is way more intrusive and orders of magnitude slower. But yes, that’s probably something in charge of Segger as a plugin for VS (not VSCode, that already supports it).
Talking about Segger’s jlink, however, I am experimenting an apparently weird behavior of the Quick Debug setup. In order to debug an existing CMake project, I have to check “The debugged device is not listed. Configure the debug method manually.” and specify all the debug connection details for J-link. If instead I select the device (MXIMRT1061xxxxA) from the list, then “Debug using:” shows “No compatible USB device found” – although the package Segger J-Link 5.9 is installed. Is this by design?
Thanks, register definition file is now correctly loaded. However, using the new version the plugin does not initialize correctly: when Visual Studio 2022 starts and the CMake project is opened, in the Debug menu there’s only “Quick Debug Cmake Scripts” (no “Quick Debug With GDB” entry).
Note that the Clang IntelliSense dialog is not shown at startup (although “Show this dialog when Visual Studio starts” is checked).
“Quick Debug With GDB” is shown only after I somehow “force” the plugin to start (I suppose), i.e., by clicking on any menu entry under Tools->Visual GDB (and at this point the Clang IntelliSense dialog is shown before the dialog related to the selected command).
Best regards,
StefanoBtw, trying to load the file as XML (i.e., not changing the extension) still produces the error mentioned earlier in another post. FYI.
Regards,
Stefano
