...
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://voxelbotics.atlassian.net/wiki/spaces/SOMnRF9151/pages/804093953/Understanding+Zephyr+BSP+for+SOM-nRF9151#2NRF9151#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:
...
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.
...
The SOM-NRF9151 board uses an out-of-tree board configuration, since it is not supported in Zephyr:
https://voxelbotics.atlassian.net/wiki/spaces/SOMnRF9151/pages/804093953/Understanding+Zephyr+BSP+for+SOM-nRF9151#3NRF9151#3.1.-SOM-nRF9151NRF9151-Board-Configuration
Build the application for the nRF9151 on the SOM-NRF9151 using the following command:
...