VSCode J-link settings file and startup command

[Greenhal]

Hi,

I am facing problems with debugging code using J-link and VSCode extension with iMXRT117x. I am using a custom board without flash - only external RAM is available. With MCUXpresso I was able to establish proper debugging session but with VSCode I have troubles. 

First thing that is not working fully correct for me is that J-link settings file is loaded from default location which is in the "build" directory. I can change the settings in the file but my environment work in the way that when I clean project the build directory is deleted so I need to change settings file every time I clean the build. Is it possible to set custom path to the settings J-link file?

Second thing is that to be able properly debug the code I need to add the memory settings. In the MCUXpresso it is done in the way presented below

How can I add this settings to the VSCode debugger?

Best regards

[EdwinHz]

Hi @Greenhal,

Unfortunately, the two features that you are looking for are not available on the current version of VS Code. Please continue using standalone MCUXpresso IDE instead.

BR,
Edwin.

[Jamie309Perez]

Hello!

You're facing two key issues with J-Link and VSCode on your iMXRT117x custom board. First, to avoid losing your J-Link settings file when cleaning the build directory, you can set a custom path in launch.json using the -settingsfile argument, pointing to a stable location like ${workspaceFolder}/jlink_settings.ini. Second, to enable proper debugging with external RAM, replicate MCUXpresso’s memory settings by adding a memoryMap entry in launch.json, specifying the RAM’s start address, size, and access type. This ensures the debugger knows where valid memory is for breakpoints and variable inspection.