1- # Zephyr Example Application
1+ # nRF Connect SDK example application
22
3- <a href =" https://github.com/zephyrproject-rtos/ example-application/actions/workflows/build.yml?query=branch%3Amain " >
4- <img src =" https://github.com/zephyrproject-rtos/ example-application/actions/workflows/build.yml/badge.svg?event=push " >
3+ <a href =" https://github.com/nrfconnect/ncs- example-application/actions/workflows/build-using-docker .yml?query=branch%3Amain " >
4+ <img src =" https://github.com/nrfconnect/ncs- example-application/actions/workflows/build-using-docker .yml/badge.svg?event=push " >
55</a >
6- <a href =" https://github.com/zephyrproject-rtos/ example-application/actions/workflows/docs.yml?query=branch%3Amain " >
7- <img src =" https://github.com/zephyrproject-rtos/ example-application/actions/workflows/docs.yml/badge.svg?event=push " >
6+ <a href =" https://github.com/nrfconnect/ncs- example-application/actions/workflows/docs.yml?query=branch%3Amain " >
7+ <img src =" https://github.com/nrfconnect/ncs- example-application/actions/workflows/docs.yml/badge.svg?event=push " >
88</a >
9- <a href =" https://zephyrproject-rtos .github.io/example-application " >
9+ <a href =" https://nrfconnect .github.io/ncs- example-application " >
1010 <img alt =" Documentation " src =" https://img.shields.io/badge/documentation-3D578C?logo=sphinx&logoColor=white " >
1111</a >
12- <a href =" https://zephyrproject-rtos .github.io/example-application/doxygen " >
12+ <a href =" https://nrfconnect .github.io/ncs- example-application/doxygen " >
1313 <img alt =" API Documentation " src =" https://img.shields.io/badge/API-documentation-3D578C?logo=c&logoColor=white " >
1414</a >
1515
16- This repository contains a Zephyr example application. The main purpose of this
17- repository is to serve as a reference on how to structure Zephyr-based
18- applications. Some of the features demonstrated in this example are:
16+ This repository contains an nRF Connect SDK example application. The main
17+ purpose of this repository is to serve as a reference on how to structure nRF Connect
18+ SDK based applications. Some of the features demonstrated in this example are:
1919
2020- Basic [ Zephyr application] [ app_dev ] skeleton
2121- [ Zephyr workspace applications] [ workspace_app ]
@@ -29,12 +29,12 @@ applications. Some of the features demonstrated in this example are:
2929- Custom [ west extension] [ west_ext ]
3030- Doxygen and Sphinx documentation boilerplate
3131
32- This repository is versioned together with the [ Zephyr main tree] [ zephyr ] . This
33- means that every time that Zephyr is tagged, this repository is tagged as well
32+ This repository is versioned together with the [ nRF Connect SDK main tree] [ sdk-nrf ] . This
33+ means that every time that nRF Connect SDK is tagged, this repository is tagged as well
3434with the same version number, and the [ manifest] ( west.yml ) entry for ` zephyr `
35- will point to the corresponding Zephyr tag. For example, the ` example-application `
36- v2.6 .0 will point to Zephyr v2.6 .0. Note that the ` main ` branch always
37- points to the development branch of Zephyr , also ` main ` .
35+ will point to the corresponding nRF Connect SDK tag. For example, the ` ncs- example-application`
36+ v2.5 .0 will point to nRF Connect SDK v2.5 .0. Note that the ` main ` branch always
37+ points to the development branch of nRF Connect SDK , also ` main ` .
3838
3939[ app_dev ] : https://docs.zephyrproject.org/latest/develop/application/index.html
4040[ workspace_app ] : https://docs.zephyrproject.org/latest/develop/application/index.html#zephyr-workspace-app
@@ -43,25 +43,25 @@ points to the development branch of Zephyr, also `main`.
4343[ board_porting ] : https://docs.zephyrproject.org/latest/guides/porting/board_porting.html
4444[ bindings ] : https://docs.zephyrproject.org/latest/guides/dts/bindings.html
4545[ drivers ] : https://docs.zephyrproject.org/latest/reference/drivers/index.html
46- [ zephyr ] : https://github.com/zephyrproject-rtos/zephyr
46+ [ sdk-nrf ] : https://github.com/nrfconnect/sdk-nrf
4747[ west_ext ] : https://docs.zephyrproject.org/latest/develop/west/extensions.html
4848
49- ## Getting Started
49+ ## Getting started
5050
51- Before getting started, make sure you have a proper Zephyr development
52- environment. Follow the official
53- [ Zephyr Getting Started Guide ] ( https://docs.zephyrproject.org/ latest/getting_started/index .html ) .
51+ Before getting started, make sure you have a proper nRF Connect SDK development environment.
52+ Follow the official
53+ [ Installation guide ] ( https://developer.nordicsemi.com/nRF_Connect_SDK/doc/ latest/nrf/installation/install_ncs .html ) .
5454
5555### Initialization
5656
5757The first step is to initialize the workspace folder (`` my-workspace `` ) where
58- the `` example-application `` and all Zephyr modules will be cloned. Run the following
58+ the `` ncs- example-application`` and all nRF Connect SDK modules will be cloned. Run the following
5959command:
6060
6161``` shell
62- # initialize my-workspace for the example-application (main branch)
63- west init -m https://github.com/zephyrproject-rtos/ example-application --mr main my-workspace
64- # update Zephyr modules
62+ # initialize my-workspace for the ncs- example-application (main branch)
63+ west init -m https://github.com/nrfconnect/ncs- example-application --mr main my-workspace
64+ # update nRF Connect SDK modules
6565cd my-workspace
6666west update
6767```
@@ -77,9 +77,8 @@ west build -b $BOARD app
7777
7878where ` $BOARD ` is the target board.
7979
80- You can use the ` custom_plank ` board found in this
81- repository. Note that Zephyr sample boards may be used if an
82- appropriate overlay is provided (see ` app/boards ` ).
80+ You can use the ` custom_plank ` board found in this repository. Note that you can use
81+ Zephyr and nRF Connect SDK sample boards if an appropriate overlay is provided (see ` app/boards ` ).
8382
8483A sample debug configuration is also provided. To apply it, run the following
8584command:
0 commit comments