nRF Connect - How to alter the path used for J-Link scripts when executing flash command?

[cscase]

I'm using nRF Connect for Visual Studio Code, working on a project that has worked great in the past, but I'm getting error messages now when attempting to flash any board. I think it's because our IT department created a policy that disallows access to the Windows AppData directory, and I want to change the path used in the commands used to flash a board. Here is the error I'm getting, and it shows the path currently being used in App Data:

FATAL ERROR: command exited with status 1: 'C:\Program Files\SEGGER\JLink_V796i\JLink.exe' -USB 504500724 -nogui 1 -if swd -speed 4000 -device nRF52840_xxAA -CommanderScript 'C:\Users\scase\AppData\Local\Temp\tmpo8u6p4dijlink\runner.jlink' -nogui 1

My current understanding is that the nRF Connect plugin generates this command and presumably also the script being referenced. Can I make it so that the script is placed in, for example, the project directory, which is outside of AppData? If so, how can I go about this?

Thanks!

Scott

[Håkon Alseth]

Hi,

 

I would recommend that you contact your IT department related to the usage (or lack thereof) of the Appdata/Local/ directory.

As a workaround, you can use Segger Ozone for debugging at this time.

 

Kind regards,

Håkon