...
2. Preparing Host
2.1. Installing the nRF Connect SDK
Go to ncs/nrf installation subdirectory git remote set-url originSOM-NRF9151 application repository - https://github.com/EmcraftSystems/
| Info |
|---|
The application and nRF Connect SDK URLs were changedare available as follows:
Make sure to change the remote URLs in existing local repositories accordingly. The SDK can be also updated via |
| Code Block |
2.1. Installing the nRF Connect SDK
Set up the nRF Connect SDK on a Linux PC as described in the Nordic documentation for the corresponding version. The instruction for v2.8.0 nRF Connect SDK can be found here:
...
Note that Emcraft maintains forks of the nRF Connect SDK and Zephyr OS on GitHub, where additional improvements are made for the nRF91xx and nRF5340 devices:
https://githubvoxelbotics.atlassian.comnet/EmcraftSystems/sdk-nrfhttps://github.com/EmcraftSystems/sdk-zephyr wiki/spaces/SOMnRF9151/pages/804093953/Understanding+Zephyr+BSP+for+SOM-NRF9151#2.-Customized-nRF-Connect-SDK
In order to use the Emcraft SDK and Zephyr forks, adjust the SDK initialization command from the SDK installation document as follows:
...
The SOM-NRF9151 Zephyr application is maintained in the separate GitHub repository:
https://github.com/EmcraftSystems/som-nrf9151-app
Just clone Clone it in the same directory where west was initialized:
...
During the nightly and release build, Buildbot adjusts the application version and build type (either debug or release) in the prj.conf file:
...
3.2. Understanding Automated Build
Emcraft maintains the Buildbot based automated build of the SOM-NRF9151 Applicationapplication, which is triggered by every change in the application repository. The subscribers receive an email from the Buildbot containing the references to the pre-built application binaries that can be downloaded from a cloud, for example:
Build status: |
|
Tag/Revision: | 98.98-12 / cca7ddffe272797acafb0a4dfb5e0d887b801ccb |
Steps: | |
0: worker_preparation |
|
1: Evaluate release tag |
|
2: Owners |
|
3: Upload |
|
4: Checkout build scripts |
|
5: Build firmware |
|
Files: | |
Image #1: asset_tracker_v2_on_nrf9151som_v98.98-12-01171742_release.hex | |
Image #2: asset_tracker_v2_on_nrf9151som_v98.98-12-01171742_debug.hex | |
Note that both debug (CONFIG_APP_VERSION_DEBUG=y) and release (CONFIG_APP_VERSION_DEBUG=n) images are generated for every application.
...
| Code Block |
|---|
cd som-nrf9151-app/asset_tracker_v2/ |
The SOM-NRF9151 board is using uses an out-of-tree board configuration, since it’s it is not supported in Zephyr:
https://githubvoxelbotics.atlassian.comnet/EmcraftSystems/som-nrf9151-app/tree/main/boards/emcraft/nrf9151somwiki/spaces/SOMnRF9151/pages/804093953/Understanding+Zephyr+BSP+for+SOM-NRF9151#3.1.-SOM-NRF9151-Board-Configuration
Build the application for the nRF9151 on the SOM-NRF9151 using the following command:
| Code Block |
|---|
west build -b nrf9151som/nrf9151/ns |
The resulting resultant image is build/merged.hex.