Lines Matching +full:directory +full:- +full:to +full:- +full:scan
10 Semiconductor nRF52840 ARM Cortex-M4F CPU and the following devices:
12 * :abbr:`ADC (Analog to Digital Converter)`
16 * :abbr:`I2C (Inter-Integrated Circuit)`
23 * :abbr:`UART (Universal asynchronous receiver-transmitter)`
51 +-----------+------------+----------------------+
54 | ADC | on-chip | adc |
55 +-----------+------------+----------------------+
56 | CLOCK | on-chip | clock_control |
57 +-----------+------------+----------------------+
58 | FLASH | on-chip | flash |
59 +-----------+------------+----------------------+
60 | GPIO | on-chip | gpio |
61 +-----------+------------+----------------------+
62 | I2C(M) | on-chip | i2c |
63 +-----------+------------+----------------------+
64 | MPU | on-chip | arch/arm |
65 +-----------+------------+----------------------+
66 | NVIC | on-chip | arch/arm |
67 +-----------+------------+----------------------+
68 | PWM | on-chip | pwm |
69 +-----------+------------+----------------------+
70 | RADIO | on-chip | Bluetooth, |
72 +-----------+------------+----------------------+
73 | RTC | on-chip | system clock |
74 +-----------+------------+----------------------+
75 | SPI(M/S) | on-chip | spi |
76 +-----------+------------+----------------------+
77 | UART | on-chip | serial |
78 +-----------+------------+----------------------+
79 | USB | on-chip | usb |
80 +-----------+------------+----------------------+
81 | WDT | on-chip | watchdog |
82 +-----------+------------+----------------------+
92 ---
100 ------------
116 1. Using the built-in bootloader only
118 3. Using an external :ref:`debug probe <debug-probes>`
121 root directory of your :term:`west installation`.
123 Option 1: Using the Built-In Bootloader Only
124 --------------------------------------------
126 The board is factory-programmed with Nordic's bootloader from Nordic's nRF5
127 SDK. With this option, you'll use Nordic's `nrfutil`_ program to create
128 firmware packages supported by this bootloader and flash them to the
132 * The ``nrf5sdk-tools`` command is installed within ``nrfutil``.
137 that the button does not face up. You will have to push it from the outside
146 #. Compile a Zephyr application; we'll use :zephyr:code-sample:`blinky`.
148 .. zephyr-app-commands::
155 .. code-block:: console
157 nrfutil nrf5sdk-tools pkg generate \
158 --hw-version 52 \
159 --sd-req=0x00 \
160 --application build/zephyr/zephyr.hex \
161 --application-version 1 \
167 .. code-block:: console
169 nrfutil nrf5sdk-tools dfu usb-serial -pkg blinky.zip -p /dev/ttyACM0
177 -----------------------------------------------
179 It is also possible to use the MCUboot bootloader with this board to flash
180 Zephyr applications. You need to do some one-time set-up to build and flash
183 overwrite the built-in Nordic bootloader, so you can always go back to using
187 available for signing your binary for MCUboot as described on :ref:`west-sign`.
189 Next, do the **one-time setup** to flash MCUboot. We'll assume you've cloned
190 the `MCUboot`_ repository into the directory ``mcuboot``, and that it is next
191 to the zephyr repository on your computer.
197 .. zephyr-app-commands::
200 :build-dir: mcuboot
205 .. code-block:: console
207 nrfutil nrf5sdk-tools pkg generate \
208 --hw-version 52 \
209 --sd-req=0x00 \
210 --application build/mcuboot/zephyr/zephyr.hex \
211 --application-version 1 \
217 .. code-block:: console
219 nrfutil nrf5sdk-tools dfu usb-serial -pkg mcuboot.zip -p /dev/ttyACM0
221 You can now flash a Zephyr application to the board using MCUboot's serial
222 recovery mode. We'll use the :zephyr:code-sample:`smp-svr` sample since it's ready to be
223 compiled for chain-loading by MCUboot (and itself supports firmware updates
233 appear under "Other Devices" in the Device Manager (in addition to the usual
235 :file:`/dev/serial/by-id/usb-ZEPHYR_MCUBOOT_0.01-if00` should be created.
238 pressed. If it still doesn't appear, retry the one-time MCUboot setup.
242 .. zephyr-app-commands::
245 :build-dir: smp_svr
248 #. Sign ``smp_svr`` for chain-loading by MCUboot.
250 .. code-block:: console
252 west sign -t imgtool --bin --no-hex -d build/smp_svr \
253 -B smp_svr.signed.bin -- --key mcuboot/root-rsa-2048.pem
255 #. Flash the application to the MCUboot serial port using ``mcumgr``:
257 .. code-block:: console
259 mcumgr --conntype=serial --connstring='dev=/dev/ttyACM0,baud=115200' \
260 image upload -e smp_svr.signed.bin
264 .. code-block:: console
266 mcumgr --conntype=serial --connstring='dev=/dev/ttyACM0,baud=115200' reset
268 You should now be able to scan for Bluetooth devices using a smartphone or
276 is set when building your application. For example, to compile blinky for
279 .. zephyr-app-commands::
282 :build-dir: blinky
284 :gen-args: -DCONFIG_BOOTLOADER_MCUBOOT=y
289 ---------------------------------------
291 If you have one, you can also use an external :ref:`debug probe <debug-probes>`
292 to flash and debug Zephyr applications, but you need to solder an SWD header
295 For Segger J-Link debug probes, follow the instructions in the
296 :ref:`nordic_segger` page to install and configure all the necessary
300 This file requires a small modification to use a different partition table.
301 Edit the include directive to include "fstab-debugger" instead of "fstab-stock".
303 In addition, the Kconfig file in the same directory must be modified by setting
304 ``BOARD_HAS_NRF5_BOOTLOADER`` to be default ``n``, otherwise the code will be
310 Here is an example for the :zephyr:code-sample:`blinky` application.
312 .. zephyr-app-commands::
313 :zephyr-app: samples/basic/blinky
322 The ``nrf52840dongle/nrf52840`` board does not have an on-board J-Link debug IC
324 :ref:`nordic_segger` page also apply to this board, with the additional step
330 There are 2 samples that allow you to test that the buttons (switches) and LEDs on
333 * :zephyr:code-sample:`blinky`
335 You can build and program the examples to make sure Zephyr is running correctly
342 .. target-notes::
345 https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52840-Dongle
348 .. _J-Link Software and documentation pack:
349 https://www.segger.com/jlink-software.html
353 https://www.nordicsemi.com/Products/Development-tools/nrf-util
355 https://github.com/JuulLabs-OSS/mcuboot
357 https://github.com/apache/mynewt-mcumgr-cli