@ -61,7 +61,7 @@ Set ``-DSHIELD=adafruit_2_8_tft_touch_v2`` when you invoke ``west build``. For e
@@ -61,7 +61,7 @@ Set ``-DSHIELD=adafruit_2_8_tft_touch_v2`` when you invoke ``west build``. For e
@ -43,7 +43,7 @@ Set ``-DSHIELD=arceli_eth_w5500`` when you invoke ``west build``. For example:
@@ -43,7 +43,7 @@ Set ``-DSHIELD=arceli_eth_w5500`` when you invoke ``west build``. For example:
@ -61,7 +61,7 @@ Set ``-DSHIELD=buydisplay_2_8_tft_touch_arduino`` when you invoke
@@ -61,7 +61,7 @@ Set ``-DSHIELD=buydisplay_2_8_tft_touch_arduino`` when you invoke
@ -63,7 +63,7 @@ Set ``-DSHIELD=buydisplay_3_5_tft_touch_arduino`` when you invoke
@@ -63,7 +63,7 @@ Set ``-DSHIELD=buydisplay_3_5_tft_touch_arduino`` when you invoke
@ -80,7 +80,7 @@ Set ``-DSHIELD=<shield designator>`` when you invoke ``west build``.
@@ -80,7 +80,7 @@ Set ``-DSHIELD=<shield designator>`` when you invoke ``west build``.
@ -92,7 +92,7 @@ Set ``-DSHIELD=ls013b7dh03`` when you invoke ``west build``. For example:
@@ -92,7 +92,7 @@ Set ``-DSHIELD=ls013b7dh03`` when you invoke ``west build``. For example:
@ -35,6 +35,6 @@ Set ``-DSHIELD=max7219_8x8`` when you invoke ``west build``. For example:
@@ -35,6 +35,6 @@ Set ``-DSHIELD=max7219_8x8`` when you invoke ``west build``. For example:
@ -54,7 +54,7 @@ Set ``-DSHIELD=st7735r_ada_160x128`` when you invoke ``west build``. For example
@@ -54,7 +54,7 @@ Set ``-DSHIELD=st7735r_ada_160x128`` when you invoke ``west build``. For example
@ -57,7 +57,7 @@ Set ``-DSHIELD=st7789v_tl019fqv01`` when you invoke ``west build``. For example:
@@ -57,7 +57,7 @@ Set ``-DSHIELD=st7789v_tl019fqv01`` when you invoke ``west build``. For example:
@ -63,7 +63,7 @@ Where ``<x>`` is either 1 for nRF51-based boards or 2 for nRF52-based boards
@@ -63,7 +63,7 @@ Where ``<x>`` is either 1 for nRF51-based boards or 2 for nRF52-based boards
@ -923,7 +923,7 @@ devices, for example:
@@ -923,7 +923,7 @@ devices, for example:
Any options marked as ``unknown`` need to be changed and set with the correct
values, in the above example the platform names, the products and the runners need
to be replaced with the correct values corresponding to the connected hardware.
In this example we are using a reel_board and an nrf52840dk_nrf52840:
In this example we are using a reel_board and an nrf52840dk/nrf52840:
..tabs::
@ -940,7 +940,7 @@ In this example we are using a reel_board and an nrf52840dk_nrf52840:
@@ -940,7 +940,7 @@ In this example we are using a reel_board and an nrf52840dk_nrf52840:
baud: 9600
- connected: true
id: 000683759358
platform: nrf52840dk_nrf52840
platform: nrf52840dk/nrf52840
product: J-Link
runner: nrfjprog
serial: /dev/cu.usbmodem0006837593581
@ -959,7 +959,7 @@ In this example we are using a reel_board and an nrf52840dk_nrf52840:
@@ -959,7 +959,7 @@ In this example we are using a reel_board and an nrf52840dk_nrf52840:
@ -319,7 +319,7 @@ On boards where a J-Link OB is present which has both CDC and MSC (virtual Mass
@@ -319,7 +319,7 @@ On boards where a J-Link OB is present which has both CDC and MSC (virtual Mass
Storage Device, also known as drag-and-drop) support, the MSD functionality can
prevent MCUmgr commands over the CDC UART port from working due to how USB
endpoints are configured in the J-Link firmware (for example on the
:ref:`Nordic nrf52840dk_nrf52840 board <nrf52840dk_nrf52840>`) because of
:ref:`Nordic nrf52840dk/nrf52840 board <nrf52840dk_nrf52840>`) because of
limiting the maximum packet size (most likely to occur when using image
management commands for updating firmware). This issue can be
resolved by disabling MSD functionality on the J-Link device, follow the
@ -13,13 +13,13 @@ The following are some of the boards that can be used with TF-M:
@@ -13,13 +13,13 @@ The following are some of the boards that can be used with TF-M:
@ -27,7 +27,7 @@ To build and flash the application (including the external memory part):
@@ -27,7 +27,7 @@ To build and flash the application (including the external memory part):
@ -67,11 +67,11 @@ To build and flash this sample for the :ref:`nrf52840dk_nrf52840`:
@@ -67,11 +67,11 @@ To build and flash this sample for the :ref:`nrf52840dk_nrf52840`:
..zephyr-app-commands::
:zephyr-app:samples/basic/blinky_pwm
:board:nrf52840dk_nrf52840
:board:nrf52840dk/nrf52840
:goals:build flash
:compact:
Change ``nrf52840dk_nrf52840`` appropriately for other supported boards.
Change ``nrf52840dk/nrf52840`` appropriately for other supported boards.
After flashing, the sample starts blinking the LED as described above. It also
@ -28,11 +28,11 @@ To build and flash this sample for the :ref:`nrf52840dk_nrf52840`:
@@ -28,11 +28,11 @@ To build and flash this sample for the :ref:`nrf52840dk_nrf52840`:
..zephyr-app-commands::
:zephyr-app:samples/basic/fade_led
:board:nrf52840dk_nrf52840
:board:nrf52840dk/nrf52840
:goals:build flash
:compact:
Change ``nrf52840dk_nrf52840`` appropriately for other supported boards.
Change ``nrf52840dk/nrf52840`` appropriately for other supported boards.
After flashing, the sample starts fading the LED as described above. It also
@ -17,8 +17,8 @@ documentation and are prefixed with :literal:`hci_` in their folder names.
@@ -17,8 +17,8 @@ documentation and are prefixed with :literal:`hci_` in their folder names.
..note::
If you want to run any bluetooth sample on the nRF5340 device (build using
``-DBOARD=nrf5340dk_nrf5340_cpuapp`` or
``-DBOARD=nrf5340dk_nrf5340_cpuapp_ns``) you must also build
``-DBOARD=nrf5340dk/nrf5340/cpuapp`` or
``-DBOARD=nrf5340dk/nrf5340/cpuapp/ns``) you must also build
and program the corresponding sample for the nRF5340 network core
:ref:`bluetooth-hci-ipc-sample` which implements the Bluetooth
@ -49,7 +49,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -49,7 +49,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -48,7 +48,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -48,7 +48,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -26,12 +26,12 @@ By default the application supports Angle of Arrival (AoA) and Angle of
@@ -26,12 +26,12 @@ By default the application supports Angle of Arrival (AoA) and Angle of
Departure (AoD) mode.
To use Angle of Arrival mode only, build this application as follows, changing
@ -18,7 +18,7 @@ Sample can be built and executed for the nRF52840 DK NRF52840 as follows:
@@ -18,7 +18,7 @@ Sample can be built and executed for the nRF52840 DK NRF52840 as follows:
..zephyr-app-commands::
:zephyr-app:samples/bluetooth/ipsp
:board:nrf52840dk_nrf52840
:board:nrf52840dk/nrf52840
:goals:build flash
:compact:
@ -27,7 +27,7 @@ To build a debug version, with logging and shell support, use the config file
@@ -27,7 +27,7 @@ To build a debug version, with logging and shell support, use the config file
..zephyr-app-commands::
:zephyr-app:samples/bluetooth/ipsp
:board:nrf52840dk_nrf52840
:board:nrf52840dk/nrf52840
:conf:prj_dbg.conf
:goals:build flash
:compact:
@ -43,7 +43,7 @@ Building and Running for Linux kernels released before 4.12
@@ -43,7 +43,7 @@ Building and Running for Linux kernels released before 4.12
@ -46,7 +46,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -46,7 +46,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -46,7 +46,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -46,7 +46,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -52,7 +52,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -52,7 +52,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -52,7 +52,7 @@ If you prefer to only build the application core image, you can do so by doing i
@@ -52,7 +52,7 @@ If you prefer to only build the application core image, you can do so by doing i
@ -73,7 +73,7 @@ The code can be found in :zephyr_file:`samples/boards/nrf/battery`.
@@ -73,7 +73,7 @@ The code can be found in :zephyr_file:`samples/boards/nrf/battery`.
Jamie McCrae
1 year ago
committed by
Carles Cufi