You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use dynamic Zephyr defines and switch to nrfutil tooling (#130)
Removes hardcoded Zephyr -D flags in favor of defines from the
zephyr_interface target. Replaces use of nrfjprog with nrfutil
in both documentation and example usage.
Copy file name to clipboardExpand all lines: nrfx-blink-sdk/README.md
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This example demonstrates how to integrate with the Zephyr SDK via CMake and how
11
11
- The West build system.
12
12
- A Python virtualenv for Zephyr.
13
13
- Zephyr SDK/toolchain.
14
-
- Host flash/debug tools for the board you're using. For example, for the nRF52840-DK board you'll need the [nRF Command Line Tools](https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools).
14
+
- Host flash/debug tools for the board you're using. For example, for the nRF52840-DK board you'll need the [nRF Util](https://www.nordicsemi.com/Products/Development-tools/nRF-Util).
15
15
16
16
- Before trying to use Swift with the Zephyr SDK, make sure your environment works and can build the provided C/C++ sample projects, in particular:
17
17
- Try building and running the "simple/blink" example from Zephyr written in C.
@@ -20,7 +20,8 @@ This example demonstrates how to integrate with the Zephyr SDK via CMake and how
20
20
21
21
- Make sure you have a recent nightly Swift toolchain that has Embedded Swift support.
22
22
- Build the program in the Zephyr virtualenv, specify the target board type via the `-DBOARD=...` CMake setting:
0 commit comments