Lines Matching +full:ncs +full:- +full:line
9 The nRF7002 DK (PCA10143) is a single-board development kit for evaluation and development on
10 the nRF7002, a Wi-Fi companion IC to Nordic Semiconductor's nRF5340 System-on-Chip (SoC) host
11 processor. It is certified for the Wi-Fi Alliance® `Wi-Fi Certification program`_ in the
12 Connectivity, Security, and Optimization categories. See `UG Wi-Fi certification`_ for detailed
15 The nRF7002 is an IEEE 802.11ax (Wi-Fi 6) compliant solution that implements the Wi-Fi physical
16 layer and Medium Access Control (MAC) layer protocols. It implements the nRF Wi-Fi driver
19 The nRF5340 host is a dual-core SoC based on the Arm® Cortex®-M33 architecture.
22 * A full-featured Arm Cortex-M33F core with DSP instructions, FPU, and Armv8-M Security Extension,
24 * A secondary Arm Cortex-M33 core, with a reduced feature set, running at a fixed 64 MHz,
51 * Micro-USB 2.0 cable
54 ------------------
58 +-----------+------------+----------------------+
61 | ADC | on-chip | adc |
62 +-----------+------------+----------------------+
63 | CLOCK | on-chip | clock_control |
64 +-----------+------------+----------------------+
65 | FLASH | on-chip | flash |
66 +-----------+------------+----------------------+
67 | GPIO | on-chip | gpio |
68 +-----------+------------+----------------------+
69 | I2C(M) | on-chip | i2c |
70 +-----------+------------+----------------------+
71 | MPU | on-chip | arch/arm |
72 +-----------+------------+----------------------+
73 | NVIC | on-chip | arch/arm |
74 +-----------+------------+----------------------+
75 | PWM | on-chip | pwm |
76 +-----------+------------+----------------------+
77 | RTC | on-chip | system clock |
78 +-----------+------------+----------------------+
80 +-----------+------------+----------------------+
81 | RADIO | nrf7002 | Wi-Fi 6 (802.11ax) |
82 +-----------+------------+----------------------+
83 | QSPI | on-chip | qspi |
84 +-----------+------------+----------------------+
85 | SPI(M/S) | on-chip | spi |
86 +-----------+------------+----------------------+
87 | SPU | on-chip | system protection |
88 +-----------+------------+----------------------+
89 | UARTE | on-chip | serial |
90 +-----------+------------+----------------------+
91 | USB | on-chip | usb |
92 +-----------+------------+----------------------+
93 | WDT | on-chip | watchdog |
94 +-----------+------------+----------------------+
98 +-----------+------------+----------------------+
101 | CLOCK | on-chip | clock_control |
102 +-----------+------------+----------------------+
103 | FLASH | on-chip | flash |
104 +-----------+------------+----------------------+
105 | GPIO | on-chip | gpio |
106 +-----------+------------+----------------------+
107 | I2C(M) | on-chip | i2c |
108 +-----------+------------+----------------------+
109 | MPU | on-chip | arch/arm |
110 +-----------+------------+----------------------+
111 | NVIC | on-chip | arch/arm |
112 +-----------+------------+----------------------+
113 | RADIO | on-chip | Bluetooth, |
115 +-----------+------------+----------------------+
116 | RTC | on-chip | system clock |
117 +-----------+------------+----------------------+
119 +-----------+------------+----------------------+
120 | SPI(M/S) | on-chip | spi |
121 +-----------+------------+----------------------+
122 | UARTE | on-chip | serial |
123 +-----------+------------+----------------------+
124 | WDT | on-chip | watchdog |
125 +-----------+------------+----------------------+
132 -------------------
149 Wi-Fi control
161 -------------------
168 secure and non-secure memory maps. By default, the entire memory space
169 (Flash, SRAM, and peripheral address space) is defined to be secure-accessible only.
176 The nRF5340 application core supports the Armv8-M Security Extension.
180 The nRF5340 network core does not support the Armv8-M Security Extension.
182 attribute set. This allows to build and run secure-only applications on the nRF5340 SoC.
184 Building Secure/Non-Secure Zephyr applications with Arm |reg| TrustZone |reg|
187 Applications on the nRF5340 may contain a Secure and a Non-Secure firmware
189 Zephyr or `Trusted Firmware M`_ (TF-M). Non-Secure firmware
194 By default, SPE for the nRF5340 application core is built using TF-M.
196 Building the Secure firmware with TF-M
197 --------------------------------------
199 The process to build the Secure firmware image using TF-M and the Non-Secure
202 1. Build the Non-Secure Zephyr application
203 for the application core using ``-DBOARD=nrf7002dk/nrf5340/cpuapp/ns``.
204 To invoke the building of TF-M the Zephyr build system requires the
206 default when building Zephyr as a Non-Secure application.
209 * Build the Non-Secure firmware image as a regular Zephyr application
210 * Build a TF-M (secure) firmware image
216 Depending on the TF-M configuration, an application DTS overlay may be
217 required, to adjust the Non-Secure image Flash and SRAM starting address
221 ``-DBOARD=nrf7002dk/nrf5340/cpunet``.
224 -----------------------------------------
226 The process to build the Secure and the Non-Secure firmware images
230 using ``-DBOARD=nrf7002dk/nrf5340/cpuapp`` and
233 2. Build the Non-Secure Zephyr application for the application core
234 using ``-DBOARD=nrf7002dk/nrf5340/cpuapp/ns``.
237 ``-DBOARD=nrf7002dk/nrf5340/cpunet``.
239 When building a Secure/Non-Secure application for the nRF5340 application core,
241 Non-Secure access to all CPU resources utilized by the Non-Secure application
242 firmware. SPU configuration shall take place before jumping to the Non-Secure
249 and :ref:`application_run`), using ``-DBOARD=nrf7002dk/nrf5340/cpuapp`` for
251 ``-DBOARD=nrf7002dk/nrf5340/cpunet`` for the firmware running
265 The nRF5340 has a flash read-back protection feature. When flash read-back
267 If you are flashing with :ref:`west <west-build-flash-debug>`, run
268 this command for more details on the related ``--recover`` option:
270 .. code-block:: console
272 west flash -H -r nrfjprog --skip-rebuild
277 upgrading the nRF Command Line Tools to version 10.12.0. Further
278 information on how to install the nRF Command Line Tools can be
281 Here is an example for the :zephyr:code-sample:`hello_world` application running on the
286 .. code-block:: console
288 $ minicom -D <tty_device> -b 115200
295 .. zephyr-app-commands::
296 :zephyr-app: samples/hello_world
315 * `Wi-Fi`_ documentation for information related to Wi-Fi protocol and Wi-Fi modes of operation.
320 .. target-notes::
322 .. _Wi-Fi Certification program:
323 https://www.wi-fi.org/certification
324 .. _UG Wi-Fi certification:
325 …https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/wifi/wifi_certification.html#ug-w…
327 https://developer.arm.com/docs/100690/latest/attribution-units-sau-and-idau
329 https://www.nordicsemi.com/Products/Development-hardware/nrf7002-dk
333 https://www.trustedfirmware.org/projects/tf-m/
335 https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/installation.html#installation
337 …https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/config_and_build/index.html#configu…
339 …https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/device_guides/nrf70/index.html#ug-n…
340 .. _Wi-Fi:
341 https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/wifi/index.html#ug-wifi