Build and flash your first nRF Connect SDK application
In this exercise, we will program a simple application based on the blinky template to toggle an LED on our board. Again, any Nordic Semiconductor development board will work (nRF52, nRF53, nRF91 Series). The idea is to make sure that all the tools needed to build and flash a sample are set up correctly. The focus is to learn how to create an application from a template, build the application, and flash it on a Nordic-powered board.
Basically, we will walk you through the three short videos below to:
Create a new application based on a template.
Build an application.
Flash an application to a board.
Either watch the videos or follow the steps below.
1. Create a folder close to your root directly that will hold all the exercises that we will be working on throughout this course.
We will create that folder on the C drive in C:\nordic\myapps.
2. In VS Code. Click on the nRF Connect Extension. In the Welcome window (panel), click on Create a new application from sample.
3. In the New application window, do the following:
3.1. Select a Freestanding application. This will link and use an already installed nRF Connect SDK.
The other type of application is the Workspace application, which will have a dedicated SDK instance for each application. Workspace applications are out of the scope of this course.
3.2. Select the directory to store your application folder, nordic\myapps.
3.3. Name your application fund_less1_exer1 as this is the naming convention that we will use for exercises throughout this course. Note that this will create a folder for your application called fund_less1_exer1.
3.4. Select the version of nRF Connect SDK to compile and build your application with. The nRF Connect toolchain should match the version of the SDK.
The list contains versions already installed on your machine. If you want to install a version that is not already present on your machine, press on the install button. This invokes the Toolchain Manager, where you can download different versions of the SDK.
3.5. Chose the template to base your application on. This will make a copy of the template and store it in the directory you specified in step 3.2 and name it as you specified in step 3.3.
The SDK contains a rich set of templates. In the context of templates, Samples are simple and showcase a single feature or library (e.g. SHA256 sample, UART sample, PWM sample, etc.), whileApplications are complex and include a variety of libraries to implement a specific use case (e.g. Asset tracker application, Keyboard application, Mouse application).
We will base our first application on the blinky sample. Type blinky in the application template box and select the one that says zephyr\samples\basic\blinky . This is simply the relative path directly within the nRF Connect SDK where the template is stored.
The Select.. button in the Application template line
allows you to filter templates by several criteria including Wireless Communication Protocol, Device (SoC or SiP), and more (crypto, drivers, etc.) and also gives you access to the documentation of templates.
3.6. Finally, click on the Create Application button.
This will add an unbuilt application to VS Code as shown below:
4. Add a build configuration.
One of the many advantages of nRF Connect SDK is the high decoupling between an application source code and the software configuration/hardware description, making it extremely easy to switch the build for a new hardware or software configuration.
In this step, we will specify which development board or custom board (hardware) we want to build the application for. We will also select the software configuration (*.conf and possible overlays) to be used in the build.
Click on the small Add Build Configuration icon next to the application name.
This will open the Add Build Configuration window shown below:
4.1. Select the board you want to flash your application on, using the board ID. See the table below for an overview of board ID’s for Nordic devices.
In the screenshot, we select the nRF52833 DK by specifying its ID, nrf52833dk_nrf52833. You can also create your own board and define your own board ID, however this is beyond the scope of this course.
4.2. Depending on the template you chose in step 3, you will be presented with at least one application configuration prj.conf. Some templates contain more than one application configuration file (eg: prj.conf, prj_minimal.conf, prj_cdc.conf). These different configurations, if found in the template, are explained in the template documentation. The blinky template has only one option.
4.3. The Kconfig Fragments field will list the Kconfig overlays (aka Kconfig Fragments) that are available in the template or have been added in the application folder. These are modifiers to the application configuration file (covered in Lesson 3). The blinky template has none.
4.4. The Extra CMake arguments field allows you to pass arguments to the build system if needed. We will leave that blank for this demo.
4.5. The Build directory name field gives you the option to manually name the build directory where the final binary files and temporary build files will be stored. We will leave this to be the default name specified by the tool, which is build.
4.6. Leave the Build after generating configuration option selected to trigger the build process after clicking on the Build Configuration button.
4.7. Select the Enable debug options to enable debugging of the application.
4.8. Click on the Build Configuration button to create the configuration and initiate the build process.
The build process will take some time to finish. Open the Terminal (View->Terminal) to see the progress of the build.
A successful build is indicated by displaying the memory usage of the application as shown in the screenshot above.
A key component in the build process is West, which is a core command-line utility in nRF Connect SDK/Zephyr. West provides several services like repository management, building applications, and flashing, and is internally invoked by nRF Connect for VS Code.
You can also issue these commands manually in the command line prompt if you prefer to work in the terminal.
Type west help in the nRF Connect terminal if you are interested in learning how to use the command-line interface with the nRF Connect SDK. Alternatively, you could checkout this short video.
If you switch to the explorer in VS Code or browse to the application directory, you will notice that there is a new subdirectory created from the build process called build. This folder contains the build output including the binary file that we will flash on the board in the next step.
5. Make sure that your development kit is connected to your computer and that it is switched on. It should be listed in the Connected Devices window in the nRF Connect for VS Code extension.
If you don’t see your board listed, press on the Refresh connected device icon in the connected devices window.
6. From the Actions window, press on the Flash to flash the application to the board. You can open the terminal view to see the progress of the flashing as shown below.
The difference between “Flash” and “Erase and flash” is that the latter erases the whole device, including all data the application has saved.
For example, if the device is added to a mesh network, “Erase and flash” will make the device forget this.
LED1 on your board should be blinking now in 1-second intervals.
If you are using a Thingy:91, the flash procedure is different. Please check it here.
7. Just for the sake of this demonstration, change the value of the SLEEP_TIME_MS (line 13 in main.c, which you can locate in Source Files->Applications or through the Explorer panel of Visual Studio Code) which controls the interval at which the LED is blinking. Change the macro from 1000 to 100.
#define SLEEP_TIME_MS 100
8. Rebuild and re-flash the application on your board. You should observe that the LED is now blinking at a higher frequency.
In Lesson 2, we will take an in-depth look at the source code of this application to understand how it works.