Lines Matching +full:analog +full:- +full:alt +full:- +full:mode
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)`
29 :alt: nRF52840 Dongle
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
117 2. Using MCUboot in serial recovery mode
118 3. Using an external :ref:`debug probe <debug-probes>`
123 Option 1: Using the Built-In Bootloader Only
124 --------------------------------------------
126 The board is factory-programmed with Nordic's bootloader from Nordic's nRF5
138 :alt: Location of RESET button and direction of push
143 #. Compile a Zephyr application; we'll use :zephyr:code-sample:`blinky`.
145 .. zephyr-app-commands::
152 .. code-block:: console
154 nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
155 --application build/zephyr/zephyr.hex \
156 --application-version 1 blinky.zip
161 .. code-block:: console
163 nrfutil dfu usb-serial -pkg blinky.zip -p /dev/ttyACM0
170 Option 2: Using MCUboot in Serial Recovery Mode
171 -----------------------------------------------
174 Zephyr applications. You need to do some one-time set-up to build and flash
176 applications using MCUboot's serial recovery mode. This process does not
177 overwrite the built-in Nordic bootloader, so you can always go back to using
181 available for signing your binary for MCUboot as described on :ref:`west-sign`.
183 Next, do the **one-time setup** to flash MCUboot. We'll assume you've cloned
191 .. zephyr-app-commands::
194 :build-dir: mcuboot
199 .. code-block:: console
201 nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
202 --application build/mcuboot/zephyr/zephyr.hex \
203 --application-version 1 mcuboot.zip
208 .. code-block:: console
210 nrfutil dfu usb-serial -pkg mcuboot.zip -p /dev/ttyACM0
213 recovery mode. We'll use the :zephyr:code-sample:`smp-svr` sample since it's ready to be
214 compiled for chain-loading by MCUboot (and itself supports firmware updates
217 #. Boot into MCUboot serial recovery mode by plugging the board in with the SW1
226 :file:`/dev/serial/by-id/usb-ZEPHYR_MCUBOOT_0.01-if00` should be created.
229 pressed. If it still doesn't appear, retry the one-time MCUboot setup.
233 .. zephyr-app-commands::
236 :build-dir: smp_svr
239 #. Sign ``smp_svr`` for chain-loading by MCUboot.
241 .. code-block:: console
243 west sign -t imgtool --bin --no-hex -d build/smp_svr \
244 -B smp_svr.signed.bin -- --key mcuboot/root-rsa-2048.pem
248 .. code-block:: console
250 mcumgr --conntype=serial --connstring='dev=/dev/ttyACM0,baud=115200' \
251 image upload -e smp_svr.signed.bin
255 .. code-block:: console
257 mcumgr --conntype=serial --connstring='dev=/dev/ttyACM0,baud=115200' reset
270 .. zephyr-app-commands::
273 :build-dir: blinky
275 :gen-args: -DCONFIG_BOOTLOADER_MCUBOOT=y
280 ---------------------------------------
282 If you have one, you can also use an external :ref:`debug probe <debug-probes>`
286 For Segger J-Link debug probes, follow the instructions in the
292 Edit the include directive to include "fstab-debugger" instead of "fstab-stock".
301 Here is an example for the :zephyr:code-sample:`blinky` application.
303 .. zephyr-app-commands::
304 :zephyr-app: samples/basic/blinky
313 The ``nrf52840dongle/nrf52840`` board does not have an on-board J-Link debug IC
324 * :zephyr:code-sample:`blinky`
333 .. target-notes::
336 https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52840-Dongle
339 .. _J-Link Software and documentation pack:
340 https://www.segger.com/jlink-software.html
344 https://github.com/NordicSemiconductor/pc-nrfutil
346 https://github.com/JuulLabs-OSS/mcuboot
348 https://github.com/apache/mynewt-mcumgr-cli