#SEGGER EMBEDDED STUDIO FLASH PLACEMENT UPDATE#

#SEGGER EMBEDDED STUDIO FLASH PLACEMENT UPDATE#

vscode/tasks.json, update the current working directory cwd and command as required (ie. vscode/launch.json, update executable and armToolchainPath as required vscode/c_cpp_properties.json, update defines, includePath, and compilerPath as required

Board/component configurations in sdk_config.h.

Source and header files for new components.

SDK_ROOT is pointed to where is located.

GCC path is set in /components/toolchain/gcc/Makefile.posix.

When using any editor + terminal for nRF52 development, the things to remember are:

However, they can easily be replicated in Windows as long as installation paths and environment variables are set correctly. The Nordic toolchain is cross-platform, but the instructions below are specifically for Linux. The template project discussed in this post can be found on Github. Since I’ve also been developing on the Nordic nRF52, I thought I’d share another tutorial to show how a project can be set up, flashed, and debugged using Visual Studio Code. A few years ago, I created a tutorial on setting up Visual Studio Code for development with the STM32.

Segger embedded studio flash placement