In this exercise, we will create a custom board definition for a board that is based on a Nordic SiP/SoC that has TF-M support. In other words, we will create a custom board with multiple board targets. We will use the nRF9151 SiP as an example, but the instructions will be very similar to other SiPs/SoCs in the nRF91, the nRF53 , or the nRF54L Series. We will develop a custom board called DevAcademyL3E2.
One key difference is that we will not create the new custom board template using the Create new board GUI in nRF Connect for VS Code. Instead, we will pick an existing board that is similar to the DevAcademyL3E2. (i.e., it uses the same SiP/SoC and has a similar schematic, which will be the nRF9151 DK). Then, we will copy the board files into a new folder and rename it to match the new board. Once done, this will serve as the template for our new board “DevAcademyL3E2,” which we can modify to match exactly the schematic/desired software configurations of our new board.
Exercise steps
Preparing the template
1. Create a new directory on your root directory and name it my_boards.
In this directory (for example C:\my_boards), we will store our custom board definitions.
2. Make a copy of the similar DK folder.
Since our custom board is based on the nRF9151 SiP, we will make a copy of the nRF9151 DK folder that we are basing our custom board file on, located in <install_path>\zephyr\boards\nordic\nrf9151dk into your custom board directory.
Important
If your custom board uses a different System on Chip (SoC) or System in Package (SiP) than the nRF9151 SiP, you need to copy the board folder from the development kit that corresponds to the SoC or SiP you are using. For example, if your custom board is based on the nRF5340 SoC, make a copy of the “nrf5340dk” board folder.
3. Point the build system to the custom board root directory.
By default, the build system in nRF Connect goes to specific folders to look for board definitions. Namely,<install_path>/zephyr/boards/nordic/ and <install_path>/nrf/boards/nordic/.
We need to tell the build system to look at the directory we created in Step 1. To do that, we have three different options:
Option 1: Inside the application CMake file, CMakeLists.txt.
This is done by defining the BOARD_ROOTbefore pulling in the Zephyr boilerplate with find_package(Zephyr ...). When specifying BOARD_ROOT in a CMakeLists.txt, then an absolute path must be provided, for example list(APPEND BOARD_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-board-root>). When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 2: At build time.
We can build an application targeting a custom board by specifying the location of the custom board information with the -DBOARD_ROOT parameter to the build system. This can be done both using CLI (west) or using the Add build configuration GUI. Ex: Using CLI
Copy
west build -b <board name> -- -DBOARD_ROOT=<path to boards>
When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 3: From within VS Code.
This is the method that we will demonstrate here. Navigate to the Settings of nRF Connect Extension. This can be done by navigating to File -> Preferences -> Settings -> Extensions -> nRF Connect -> Board Roots, then add the directory defined in Step 1.
4. Name your new custom board.
Naming should be done according to the rules discussed in the theory part of this lesson. We will name the custom board DevAcademyL3E2 (Human readable name), devacademyl3e2 (machine readable name). This means that the board will have two board targets devacademyl3e2/nrf9151 and devacademyl3e2/nrf9151/ns.
5. Rename existing board definitions.
5.1 Rename folder. Rename the newly copied folder to devacademyl3e2. This folder will contain both board targets.
5.2 Rename files. Open the devacademyl3e2 in VS Code. (File -> Open Folder). Make sure that your VS Code contains only one directory in the workspace which is the opened folder devacademyl3e2.
Press (F2) or right-click on each file and select rename. Rename the files from the old name that is prefixed with nrf9151dk_****_**** to the new name devacademyl3e2_****_****. Also, make sure to rename Kconfig.nrf9151dk to Kconfig.devacademyl3e2 .
To:
5.3 Delete the doc folder as it contains documentation information for the old hardware (nRF9151 DK)
5.4 Rename content inside the files; this includes identifiers, and include files.
5.4.1 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the old DK name in small letters nrf9151dk in the Search field. Make sure to select Match Case. In the Replace field, put the new board name in small letters devacademyl3e2. This will change the board name in board.yml , update the include files to match the new board name, and also update the Twister metadata files for both board targets.
Press on Replace All. Make sure there is no space after the words.
5.4.2 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the normalized old board name NRF9151DK in the Search field. Make sure to select Match Case. In the Replace field, put the normalized new board name DEVACADEMYL3E2. This will change the content in Kconfig.defconfig, Kconfig.devacademyl3e2 , and the debug/flash board.cmake files to match the new normalized board name. Make sure to press on Replace All.
5.4.3 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the string nRF9151 DK, which represents the human-readable name of the old DK, in the Search field. In the Replace field, put the string DevAcademyL3E2. This changes the comments and Kconfig string descriptors to reflect the new board name.
Adjusting the template to match your schematic /Software Configration
6. Now, we have the template ready in the custom board folder. If the new board (ex: DevAcademyL3E2) has hardware differences from the board template we copied (nRF9151 DK), this must be reflected in the Devicetree files. The same applies to the software configurations. Basically, you use the same concepts and practices we covered in earlier topics.
Testing
7. Build and flash the application to your board.
In this part, we will build and flash different samples on the custom board DevAcademyL3E2 for testing purposes. You can see the custom board from the Add Build Configuration Window.
Note that you should see two board targets for the (DevAcademyL3E2) available in the Custom board. devacademyl3e2/nrf9151_ns (with TF-M) and devacademyl3e2_nrf9151 (without TF-M).
Simple samples like (Hello World and Blinky) will be runnable on both build targets. Samples with Cellular IoT connections will only run on the devacademyl3e2_nrf9151_ns (built with TF-M) as they are designed that way.
7.1 Test Serial Console/UART.
Create a new application based on the Hello World sample. Build the application for the new custom board the same way we did in Exercise 1.
You should see the following output on the terminal once the build is complete. Notice how the TF-M is included as a child image
Flash the application to the board. Flashing to the board will write the merged hex that contains both images for the application and TF-M. You should see the following output on the serial terminal:
The Hello World sample should run on both targets. However, as mentioned before applications with cellular IoT connectivity needs to run on the devacademyl3e2/nrf9151/ns build target.
7.2 Test LEDs and buttons.
Build the “Button” Sample for the target devacademyl3e2/nrf9151/ns and flash it to your board . You should see that every time you press Button 1 on the DK , LED 1 is turned on. Also you should see the following output on the terminal.
*** Booting nRF Connect SDK ***Set up button at gpio@50000000 pin 11Set up LED at gpio@50000000 pin 13Press the buttonButton pressed at 219119Button pressed at 242602Button pressed at 269271Button pressed at 273719
Terminal
7.3 Test PWM.
Build the “PWM LED ” Sample for the target devacademyl3e2/nrf9151/ns and flash it to your board. You should see that LED 1 is turned on and off and then gradually start fading. Also, you should see the following output on the terminal.
Note: Not all Cycle periods are supported on all hardware.
7.4 Test the Cellular Modem (application must run on the /ns variant).
Build the AT Client or the AT Monitor sample for the target devacademyl3e2/nrf9151/ns and flash it to your board. Test the selected sample as specified in the document.
Important
For more advanced samples like the Cellular: nRF Cloud multi-service , and other samples that have dedicated application devicetree overlays/Kconfig fragments, you would need to create an application’s devicetree overlay/Kconfig fragments that match your custom board name for these applications/samples to work.
This is done by copying existing overlay/Kconfig fragment(s) and renaming it to match the build target. So, for the case of the DevAcademyE3L2, you would copy these files nrf9151dk_nrf9151_ns.overlay and nrf9151dk_nrf9151_ns.conf and name the new copies devacademyl3e2_nrf9151_ns.conf and devacademyl3e2_nrf9151_ns.overlay.
7.5 Test I2C and SPI.
To test I2C or SPI you would need external components. You could follow the instructions in these lessons for I2C and SPI.
The solution for this exercise can be found in the GitHub repository, l3/l3_e2_sol of whichever version you are using.
v3.0.0
In this exercise, we will create a custom board definition for a board that is based on a Nordic SiP/SoC that has TF-M support. In other words, we will create a custom board with multiple board targets. We will use the nRF9151 SiP as an example, but the instructions will be very similar to other SiPs/SoCs in the nRF91, the nRF53 , or the nRF54L Series. We will develop a custom board called DevAcademyL3E2.
One key difference is that we will not create the new custom board template using the Create new board GUI in nRF Connect for VS Code. Instead, we will pick an existing board that is similar to the DevAcademyL3E2. (i.e., it uses the same SiP/SoC and has a similar schematic, which will be the nRF9151 DK). Then, we will copy the board files into a new folder and rename it to match the new board. Once done, this will serve as the template for our new board “DevAcademyL3E2,” which we can modify to match exactly the schematic/desired software configurations of our new board.
Exercise steps
Preparing the template
1. Create a new directory on your root directory and name it my_boards.
In this directory (for example C:\my_boards), we will store our custom board definitions.
2. Make a copy of the similar DK folder.
Since our custom board is based on the nRF9151 SiP, we will make a copy of the nRF9151 DK folder that we are basing our custom board file on, located in <install_path>\zephyr\boards\nordic\nrf9151dk into your custom board directory.
Important
If your custom board uses a different System on Chip (SoC) or System in Package (SiP) than the nRF9151 SiP, you need to copy the board folder from the development kit that corresponds to the SoC or SiP you are using. For example, if your custom board is based on the nRF5340 SoC, make a copy of the “nrf5340dk” board folder.
3. Point the build system to the custom board root directory.
By default, the build system in nRF Connect goes to specific folders to look for board definitions. Namely,<install_path>/zephyr/boards/nordic/ and <install_path>/nrf/boards/nordic/.
We need to tell the build system to look at the directory we created in Step 1. To do that, we have three different options:
Option 1: Inside the application CMake file, CMakeLists.txt.
This is done by defining the BOARD_ROOTbefore pulling in the Zephyr boilerplate with find_package(Zephyr ...). When specifying BOARD_ROOT in a CMakeLists.txt, then an absolute path must be provided, for example list(APPEND BOARD_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-board-root>). When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 2: At build time.
We can build an application targeting a custom board by specifying the location of the custom board information with the -DBOARD_ROOT parameter to the build system. This can be done both using CLI (west) or using the Add build configuration GUI. Ex: Using CLI
Copy
west build -b <board name> -- -DBOARD_ROOT=<path to boards>
When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 3: From within VS Code.
This is the method that we will demonstrate here. Navigate to the Settings of nRF Connect Extension. This can be done by navigating to File -> Preferences -> Settings -> Extensions -> nRF Connect -> Board Roots, then add the directory defined in Step 1.
4. Name your new custom board.
Naming should be done according to the rules discussed in the theory part of this lesson. We will name the custom board DevAcademyL3E2 (Human readable name), devacademyl3e2 (machine readable name). This means that the board will have two board targets devacademyl3e2/nrf9151 and devacademyl3e2/nrf9151/ns.
5. Rename existing board definitions.
5.1 Rename folder. Rename the newly copied folder to devacademyl3e2. This folder will contain both board targets.
5.2 Rename files. Open the devacademyl3e2 in VS Code. (File -> Open Folder). Make sure that your VS Code contains only one directory in the workspace which is the opened folder devacademyl3e2.
Press (F2) or right-click on each file and select rename. Rename the files from the old name that is prefixed with nrf9151dk_****_**** to the new name devacademyl3e2_****_****. Also, make sure to rename Kconfig.nrf9151dk to Kconfig.devacademyl3e2 .
To:
5.3 Delete the doc folder as it contains documentation information for the old hardware (nRF9151 DK)
5.4 Rename content inside the files; this includes identifiers, and include files.
5.4.1 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the old DK name in small letters nrf9151dk in the Search field. Make sure to select Match Case. In the Replace field, put the new board name in small letters devacademyl3e2. This will change the board name in board.yml , update the include files to match the new board name, and also update the Twister metadata files for both board targets.
Press on Replace All. Make sure there is no space after the words.
5.4.2 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the normalized old board name NRF9151DK in the Search field. Make sure to select Match Case. In the Replace field, put the normalized new board name DEVACADEMYL3E2. This will change the content in Kconfig.defconfig, Kconfig.devacademyl3e2 , and the debug/flash board.cmake files to match the new normalized board name. Make sure to press on Replace All.
5.4.3 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the string nRF9151 DK, which represents the human-readable name of the old DK, in the Search field. In the Replace field, put the string DevAcademyL3E2. This changes the comments and Kconfig string descriptors to reflect the new board name.
Adjusting the template to match your schematic /Software Configration
6. Now, we have the template ready in the custom board folder. If the new board (ex: DevAcademyL3E2) has hardware differences from the board template we copied (nRF9151 DK), this must be reflected in the Devicetree files. The same applies to the software configurations. Basically, you use the same concepts and practices we covered in earlier topics.
Testing
7. Build and flash the application to your board.
In this part, we will build and flash different samples on the custom board DevAcademyL3E2 for testing purposes. You can see the custom board from the Add Build Configuration Window.
Note that you should see two board targets for the (DevAcademyL3E2) available in the Custom board. devacademyl3e2/nrf9151_ns (with TF-M) and devacademyl3e2_nrf9151 (without TF-M).
Simple samples like (Hello World and Blinky) will be runnable on both build targets. Samples with Cellular IoT connections will only run on the devacademyl3e2_nrf9151_ns (built with TF-M) as they are designed that way.
7.1 Test Serial Console/UART.
Create a new application based on the Hello World sample. Build the application for the new custom board the same way we did in Exercise 1.
You should see the following output on the terminal once the build is complete. Notice how the TF-M is included as a child image
Flash the application to the board. Flashing to the board will write the merged hex that contains both images for the application and TF-M. You should see the following output on the serial terminal:
The Hello World sample should run on both targets. However, as mentioned before applications with cellular IoT connectivity needs to run on the devacademyl3e2/nrf9151/ns build target.
7.2 Test LEDs and buttons.
Build the “Button” Sample for the target devacademyl3e2/nrf9151/ns and flash it to your board . You should see that every time you press Button 1 on the DK , LED 1 is turned on. Also you should see the following output on the terminal.
*** Booting nRF Connect SDK ***Set up button at gpio@50000000 pin 11Set up LED at gpio@50000000 pin 13Press the buttonButton pressed at 219119Button pressed at 242602Button pressed at 269271Button pressed at 273719
Terminal
7.3 Test PWM.
Build the “PWM LED ” Sample for the target devacademyl3e2/nrf9151/ns and flash it to your board. You should see that LED 1 is turned on and off and then gradually start fading. Also, you should see the following output on the terminal.
Note: Not all Cycle periods are supported on all hardware.
7.4 Test the Cellular Modem (application must run on the /ns variant).
Build the AT Client or the AT Monitor sample for the target devacademyl3e2/nrf9151/ns and flash it to your board. Test the selected sample as specified in the document.
Important
For more advanced samples like the Cellular: nRF Cloud multi-service , and other samples that have dedicated application devicetree overlays/Kconfig fragments, you would need to create an application’s devicetree overlay/Kconfig fragments that match your custom board name for these applications/samples to work.
This is done by copying existing overlay/Kconfig fragment(s) and renaming it to match the build target. So, for the case of the DevAcademyE3L2, you would copy these files nrf9151dk_nrf9151_ns.overlay and nrf9151dk_nrf9151_ns.conf and name the new copies devacademyl3e2_nrf9151_ns.conf and devacademyl3e2_nrf9151_ns.overlay.
7.5 Test I2C and SPI.
To test I2C or SPI you would need external components. You could follow the instructions in these lessons for I2C and SPI.
The solution for this exercise can be found in the GitHub repository, l3/l3_e2_sol of whichever version you are using.
v3.0.0
Important
This exercise tab is for nRF Connect SDK v2.6.2 – v2.5.2, where Hardware model 1 (HWMv1) is used. HWMv1 is deprecated and will be removed in nRF Connect SDK v3.0.0.
Use HWMv2 for all new designs (other tab).
In this exercise, we will create a custom board definition for a board that is based on a Nordic SiP/SoC that has TF-M support. We will use the nRF9161 SiP as an example, but the instructions will be very similar to other SiPs/SoCs in the nRF91 Series or the nRF53 Series. We will develop a custom board called DevAcademy nRF9161.
One key difference is that we will not create the new custom board template using the Create new board GUI in nRF Connect for VS Code. Instead, we will pick an existing board that is similar to the DevAcademy nRF9161. (i.e., it uses the same SiP/SoC and has a similar schematic, which will be the nRF9161 DK). Then, we will copy the board files into a new folder and rename it to match the new board. Once done, this will serve as the template for our new board “DevAcademy nRF9161,” which we can modify to match exactly the schematic/desired software configurations of our new board.
Exercise steps
Preparing the template
1. Create a new directory on your root directory and name it my_boards.
In this directory (for example C:\my_boards), we will store our custom board definitions.
2. Make a copy of the nRF9161 DK folder.
Make a copy of the nRF9161 DK folder that we are basing our custom board file on, located in <install_path>\zephyr\boards\arm\nrf9161dk_nrf9161 into your custom board directory.
3. Point the build system to the custom board root directory.
By default, the build system in nRF Connect goes to specific folders to look for board definitions. Namely, /zephyr/boards/arm/ and /nrf/boards/arm/.
We need to tell the build system to look at the directory we created in Step 1. To do that, we have three different options:
Option 1: Inside the application CMake file, CMakeLists.txt.
This is done by defining the BOARD_ROOTbefore pulling in the Zephyr boilerplate with find_package(Zephyr ...). When specifying BOARD_ROOT in a CMakeLists.txt, then an absolute path must be provided, for example list(APPEND BOARD_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/<extra-board-root>). When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 2: At build time.
We can build an application targeting a custom board by specifying the location of the custom board information with the -DBOARD_ROOT parameter to the build system. This can be done both using CLI (west) or using the Add build configuration GUI. Ex: Using CLI
Copy
west build -b <board name> -- -DBOARD_ROOT=<path to boards>
When using -DBOARD_ROOT=<board-root> both absolute and relative paths can be used. Relative paths are treated relatively to the application directory.
Option 3: From within VS Code.
This is the method that we will demonstrate here. Navigate to the Settings of nRF Connect Extension. This can be done by navigating to File -> Preferences -> Settings -> Extensions -> nRF Connect -> Board Roots, then add the directory defined in Step 1.
4. Name your new custom board.
Naming should be done according to the rules discussed in the theory part of this lesson. We will name the custom board DevAcademy nRF9161 (Human Readable name). This means that the board will have two build targets devacademy_nrf9161 and devacademy_nrf9161_ns and two Kconfig Symbols BOARD_DEVACADEMY_NRF9161 and BOARD_DEVACADEMY_NRF9161_NS .
5. Rename existing board definitions.
5.1 Rename folder. Rename the newly copied folder to devacademy_nrf9161. This folder will contain both build targets.
5.2 Rename files. Open the devacademy_nrf9161 in VS Code. (File -> Open Folder). Make sure that your VS Code contains only one directory in the workspace which is the opened folder devacademy_nrf9161.
Press (F2) or right-click on each file and select rename. Rename the files from the old name that is prefixed with nrf9161dk_nrf9161_**** to the new name devacademy_nrf9161_****.
Old Names
To:
New Names
5.3 Delete the doc folder as it contains documentation information for the old hardware (nRF9161 DK)
5.4 Rename content inside the files; this includes identifiers, build targets, and include files.
5.4.1 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the old build target nrf9161dk_nrf9161 in the Search field. Make sure to select Match Case. In the Replace field, put the new build target devacademy_nrf9161. Note that we will change both build targets (the non-secure and secure) in one go. Also the included files will be renamed to match the changes we have made in step 3.2.
Press on Replace All.
5.4.2 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the old Kconfig symbol NRF9161DK_NRF9161 in the Search field. Make sure to select Match Case. In the Replace field, put the Kconfig symbol devacademy_nrf9161. Note that we will change both the non-secure and secure in one go. Make sure to press on Replace All.
5.4.3 From the Edit menu open, click Replace in Files (Ctrl+Shift+H) and type the string nRF9161 DK in the Search field. Make sure to select Match Case. In the Replace field, put the string DevAcademy. This changes the comments and Kconfig string descriptors to reflect the new board name.
Adjusting the template to match your schematic /Software Configration
6. Now, we have the template ready in the custom board folder. If the new board (ex: DevAcademy nRF9161) has hardware differences from the board template we copied (nRF9161 DK), this must be reflected in the Devicetree files. The same applies to the software configurations. Basically, you use the same concepts and practices we covered in earlier topics.
Testing
7. Build and flash the application to your board.
In this part, we will build and flash different samples on the custom board DevAcademy nRF9161 for testing purposes. You can see the custom board from the Add Build Configuration Window.
Note that you should see two build targets for the (DevAcademy nRF9161) available in the Custom board. devacademy_nrf9161_ns (with TF-M) and devacademy_nrf9161 (without TF-M).
Simple samples like (Hello World and Blinky) will be runnable on both build targets. Samples with Cellular IoT connections will only run on the devacademy_nrf9161_ns (built with TF-M) as they are designed that way.
7.1 Test Serial Console/UART.
Create a new application based on the Hello World sample. Build the application for the new custom board the same way we did in Exercise 1.
You should see the following output on the terminal once the build is complete. Notice how the TF-M is included as a child image
Flash the application to the board. Flashing to the board will write the merged hex that contains both images for the application and TF-M. You should see the following output on the serial terminal:
The Hello World sample should run on both targets. However, as mentioned before applications with cellular IoT connectivity needs to run on the devacademy_nrf9161_ns build target.
7.2 Test LEDs and buttons.
Build the “Button” Sample for the target devacademy_nrf9161_ns and flash it to your board . You should see that every time you press Button 1 on the DK , LED 1 is turned on. Also you should see the following output on the terminal.
*** Booting nRF Connect SDK 2.6.1-3758bcbfa5cd ***Set up button at gpio@50000000 pin 11Set up LED at gpio@50000000 pin 13Press the buttonButton pressed at 219119Button pressed at 242602Button pressed at 269271Button pressed at 273719
Terminal
7.3 Test PWM.
Build the “PWM LED ” Sample for the target devacademy_nrf9161_ns and flash it to your board. You should see that LED 1 is turned on and off and then gradually start fading. Also, you should see the following output on the terminal.
7.4 Test the Cellular Modem (application must run on the _ns build target).
Build the “AT Client” or the AT Monitor sample for the target devacademy_nrf9161_ns and flash it to your board. Test the selected sample as specified in the document.
Important
For applications like the Asset Tracker V2, and other samples that have dedicated application devicetree overlays/Kconfig fragments, you would need to create an application’s devicetree overlay/Kconfig fragments that match your custom board name for these applications/samples to work.
This is done by copying existing overlay/Kconfig fragment(s) and renaming it to match the build target. So, for the case of the DevAcademy nRF9161, you would copy these files nrf9161dk_nrf9161_ns.overlay and nrf9161dk_nrf9161_ns.conf and name the new copies devacademy_nrf9161_ns.conf and devacademy_nrf9161_ns.overlay.
7.5 Test I2C and SPI.
To test I2C or SPI you would need external components. You could follow the instructions in these lessons for I2C and SPI.
The solution for this exercise can be found in the GitHub repository, l3/l3_e2_sol of whichever version you are using.
Nordic Developer Academy Privacy Policy
1. Introduction
In this Privacy Policy you will find information on Nordic Semiconductor ASA (“Nordic Semiconductor”) processes your personal data when you use the Nordic Developer Academy.
References to “we” and “us” in this document refers to Nordic Semiconductor.
2. Our processing of personal data when you use the Nordic Developer Academy
2.1 Nordic Developer Academy
Nordic Semiconductor processes personal data in order to provide you with the features and functionality of the Nordic Developer Academy. Creating a user account is optional, but required if you want to track you progress and view your completed courses and obtained certificates. If you choose to create a user account, we will process the following categories of personal data:
Email
Name
Password (encrypted)
Course progression (e.g. which course you have completely or partly completed)
Certificate information, which consists of name of completed course and the validity of the certificate
Course results
During your use of the Nordic Developer Academy, you may also be asked if you want to provide feedback. If you choose to respond to any such surveys, we will also process the personal data in your responses in that survey.
The legal basis for this processing is GDPR article 6 (1) b. The processing is necessary for Nordic Semiconductor to provide the Nordic Developer Academy under the Terms of Service.
2.2 Analytics
If you consent to analytics, Nordic Semiconductor will use Google Analytics to obtain statistics about how the Nordic Developer Academy is used. This includes collecting information on for example what pages are viewed, the duration of the visit, the way in which the pages are maneuvered, what links are clicked, technical information about your equipment. The information is used to learn how Nordic Developer Academy is used and how the user experience can be further developed.
2.2 Newsletter
You can consent to receive newsletters from Nordic from within the Nordic Developer Academy. How your personal data is processed when you sign up for our newsletters is described in the Nordic Semiconductor Privacy Policy.
3. Retention period
We will store your personal data for as long you use the Nordic Developer Academy. If our systems register that you have not used your account for 36 months, your account will be deleted.
4. Additional information
Additional information on how we process personal data can be found in the Nordic Semiconductor Privacy Policy and Cookie Policy.
Nordic Developer Academy Terms of Service
1. Introduction
These terms and conditions (“Terms of Use”) apply to the use of the Nordic Developer Academy, provided by Nordic Semiconductor ASA, org. nr. 966 011 726, a public limited liability company registered in Norway (“Nordic Semiconductor”).
Nordic Developer Academy allows the user to take technical courses related to Nordic Semiconductor products, software and services, and obtain a certificate certifying completion of these courses. By completing the registration process for the Nordic Developer Academy, you are agreeing to be bound by these Terms of Use.
These Terms of Use are applicable as long as you have a user account giving you access to Nordic Developer Academy.
2. Access to and use of Nordic Developer Academy
Upon acceptance of these Terms of Use you are granted a non-exclusive right of access to, and use of Nordic Developer Academy, as it is provided to you at any time. Nordic Semiconductor provides Nordic Developer Academy to you free of charge, subject to the provisions of these Terms of Use and the Nordic Developer Academy Privacy Policy.
To access select features of Nordic Developer Academy, you need to create a user account. You are solely responsible for the security associated with your user account, including always keeping your login details safe.
You will able to receive an electronic certificate from Nordic Developer Academy upon completion of courses. By issuing you such a certificate, Nordic Semiconductor certifies that you have completed the applicable course, but does not provide any further warrants or endorsements for any particular skills or professional qualifications.
Nordic Semiconductor will continuously develop Nordic Developer Academy with new features and functionality, but reserves the right to remove or alter any existing functions without notice.
3. Acceptable use
You undertake that you will use Nordic Developer Academy in accordance with applicable law and regulations, and in accordance with these Terms of Use. You must not modify, adapt, or hack Nordic Developer Academy or modify another website so as to falsely imply that it is associated with Nordic Developer Academy, Nordic Semiconductor, or any other Nordic Semiconductor product, software or service.
You agree not to reproduce, duplicate, copy, sell, resell or in any other way exploit any portion of Nordic Developer Academy, use of Nordic Developer Academy, or access to Nordic Developer Academy without the express written permission by Nordic Semiconductor. You must not upload, post, host, or transmit unsolicited email, SMS, or \”spam\” messages.
You are responsible for ensuring that the information you post and the content you share does not;
contain false, misleading or otherwise erroneous information
infringe someone else’s copyrights or other intellectual property rights
contain sensitive personal data or
contain information that might be received as offensive or insulting.
Such information may be removed without prior notice.
Nordic Semiconductor reserves the right to at any time determine whether a use of Nordic Developer Academy is in violation of its requirements for acceptable use.
Violation of the at any time applicable requirements for acceptable use may result in termination of your account. We will take reasonable steps to notify you and state the reason for termination in such cases.
4. Routines for planned maintenance
Certain types of maintenance may imply a stop or reduction in availability of Nordic Developer Academy. Nordic Semiconductor does not warrant any level of service availability but will provide its best effort to limit the impact of any planned maintenance on the availability of Nordic Developer Academy.
5. Intellectual property rights
Nordic Semiconductor retains all rights to all elements of Nordic Developer Academy. This includes, but is not limited to, the concept, design, trademarks, know-how, trade secrets, copyrights and all other intellectual property rights.
Nordic Semiconductor receives all rights to all content uploaded or created in Nordic Developer Academy. You do not receive any license or usage rights to Nordic Developer Academy beyond what is explicitly stated in this Agreement.
6. Liability and damages
Nothing within these Terms of Use is intended to limit your statutory data privacy rights as a data subject, as described in the Nordic Developer Academy Privacy Policy. You acknowledge that errors might occur from time to time and waive any right to claim for compensation as a result of errors in Nordic Developer Academy. When an error occurs, you shall notify Nordic Semiconductor of the error and provide a description of the error situation.
You agree to indemnify Nordic Semiconductor for any loss, including indirect loss, arising out of or in connection with your use of Nordic Developer Academy or violations of these Terms of Use. Nordic Semiconductor shall not be held liable for, and does not warrant that (i) Nordic Developer Academy will meet your specific requirements, (ii) Nordic Developer Academy will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of Nordic Developer Academy will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through Nordic Developer Academy will meet your expectations, or that (v) any errors in Nordic Developer Academy will be corrected.
You accept that this is a service provided to you without any payment and hence you accept that Nordic Semiconductor will not be held responsible, or liable, for any breaches of these Terms of Use or any loss connected to your use of Nordic Developer Academy. Unless otherwise follows from mandatory law, Nordic Semiconductor will not accept any such responsibility or liability.
7. Change of terms
Nordic Semiconductor may update and change the Terms of Use from time to time. Nordic Semiconductor will seek to notify you about significant changes before such changes come into force and give you a possibility to evaluate the effects of proposed changes. Continued use of Nordic Developer Academy after any such changes shall constitute your acceptance of such changes. You can review the current version of the Terms of Use at any time at https://academy.nordicsemi.com/terms-of-service/
8. Transfer of rights
Nordic Semiconductor is entitled to transfer its rights and obligation pursuant to these Terms of Use to a third party as part of a merger or acquisition process, or as a result of other organizational changes.
9. Third Party Services
To the extent Nordic Developer Academy facilitates access to services provided by a third party, you agree to comply with the terms governing such third party services. Nordic Semiconductor shall not be held liable for any errors, omissions, inaccuracies, etc. related to such third party services.
10. Dispute resolution
The Terms of Use and any other legally binding agreement between yourself and Nordic Semiconductor shall be subject to Norwegian law and Norwegian courts’ exclusive jurisdiction.
