You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
("device_guides/nrf53/features_nrf53", "app_dev/device_guides/nrf53/features_nrf53"), # Features of nRF53 Series
221
221
("device_guides/nrf53/building_nrf53", "app_dev/device_guides/nrf53/building_nrf53"), # Building and programming with nRF53 Series
222
222
("device_guides/nrf53/fota_update_nrf5340", "app_dev/device_guides/nrf53/fota_update_nrf5340"), # FOTA updates with nRF5340 DK
223
223
("device_guides/nrf53/multi_image_nrf5340", "app_dev/device_guides/nrf53/multi_image_nrf5340"), # Multi-image builds on the nRF5340 DK using child and parent images
224
224
("device_guides/nrf53/simultaneous_multi_image_dfu_nrf5340", "app_dev/device_guides/nrf53/simultaneous_multi_image_dfu_nrf5340"), # Simultaneous multi-image DFU with nRF5340 DK
225
225
("device_guides/nrf53/serial_recovery", "app_dev/device_guides/nrf53/serial_recovery"), # MCUboot’s serial recovery of the networking core image
226
226
("device_guides/nrf53/logging_nrf5340", "app_dev/device_guides/nrf53/logging_nrf5340"), # Getting logging output with nRF5340 DK
227
-
("device_guides/nrf53/thingy53_application_guide", "app_dev/device_guides/nrf53/thingy53_application_guide"), # Application guide for Thingy:53
227
+
("device_guides/nrf53/thingy53_application_guide", "app_dev/device_guides/thingy53/thingy53_application_guide"), # Application guide for Thingy:53
("device_guides/working_with_nrf/nrf53/qspi_xip_guide", "app_dev/device_guides/nrf53/qspi_xip_guide_nrf5340"), # External execute in place (XIP) configuration on the nRF5340 SoC
The |NCS| uses :ref:`ug_multi_image` for Thingy:53 by default.
178
-
When you choose ``thingy53/nrf5340/cpuapp`` or ``thingy53/nrf5340/cpuapp/ns`` as the board target when building a sample or application, you will generate firmware for both the application core and network core:
179
-
180
-
* The application core firmware consists of MCUboot bootloader and an application image.
181
-
* The network core firmware consists of network core bootloader (B0n) and application firmware of the network core.
182
-
183
-
The build process generates firmware in two formats:
184
-
185
-
* Intel Hex file (:file:`merged.hex` and :file:`merged_CPUNET.hex`) - Used with an external debug probe.
186
-
These file contains bootloaders and applications for each core.
187
-
* Binary files (:file:`zephyr.signed.bin`), containing signed application firmwares for the application and network core, respectively.
188
-
For convenience, the binary files are bundled in :file:`dfu_application.zip`, together with a manifest that describes them.
189
-
You can use the binary files or the combined zip archive to update application firmware for both cores, with either MCUboot serial recovery or OTA DFU using Bluetooth LE.
190
-
191
-
For more information about files generated as output of the build process, see :ref:`app_build_output_files`.
192
-
193
-
See the following sections for details regarding building and programming the firmware for Thingy:53 in various environments.
194
-
See :ref:`thingy53_app_update` for more detailed information about updating firmware on Thingy:53.
195
-
196
-
.. _thingy53_build_pgm_targets_wifi:
197
-
198
-
Building Wi-Fi applications on Thingy:53
199
-
----------------------------------------
200
-
201
-
.. building_wi_fi_applications_on_thingy_53_start
202
-
203
-
You can use the Nordic Thingy:53 with the nRF7002 Expansion Board (EB) for Wi-Fi development.
204
-
Connect the nRF7002 EB to the **P9** connector on Thingy:53.
205
-
206
-
To build for the nRF7002 EB with Thingy:53, use the ``thingy53/nrf5340/cpuapp`` board target with the CMake ``SHIELD`` variable set to ``nrf7002eb``.
207
-
For example, you can use the following command when building on the command line:
208
-
209
-
.. code-block::
210
-
211
-
west build -b thingy53/nrf5340/cpuapp -- -DSHIELD=nrf7002eb
212
-
213
-
.. building_wi_fi_applications_on_thingy_53_end
214
-
215
-
For the compatible Wi-Fi samples in the |NCS|, see the :ref:`wifi_samples` section.
216
-
217
-
.. _thingy53_build_pgm_vscode:
218
-
219
-
Building and programming using |VSC|
220
-
====================================
221
-
222
-
Complete the following steps to build and program using the |nRFVSC|:
.. |vsc_sample_board_target_line| replace:: select ``thingy53/nrf5340/cpuapp`` as the board target
227
-
228
-
.. include:: /includes/vsc_build_and_run.txt
229
-
230
-
3. Program the sample or application:
231
-
232
-
a. Connect the Nordic Thingy:53 to the debug out port on a 10-pin external debug probe, for example nRF5340 DK, using a 10-pin JTAG cable.
233
-
#. Connect the external debug probe to the PC using a USB cable.
234
-
#. Make sure that the Thingy:53 and the external debug probe are powered on.
235
-
#. Click :guilabel:`Flash` in the :guilabel:`Actions View`.
236
-
237
-
.. _thingy53_build_pgm_command_line:
238
-
239
-
Building and programming on the command line
240
-
============================================
241
-
242
-
You must :ref:`build_environment_cli` before you start building an |NCS| project on the command line.
243
-
244
-
To build and program the source code from the command line, complete the following steps:
245
-
246
-
1. |open_terminal_window_with_environment|
247
-
#. Go to the specific directory for the sample or application.
248
-
249
-
For example, the directory path is :file:`ncs/nrf/applications/machine_learning` when building the source code for the :ref:`nrf_machine_learning_app` application.
250
-
251
-
#. Make sure that you have the required version of the |NCS| repository by pulling the ``sdk-nrf`` repository on GitHub as described in :ref:`dm-wf-get-ncs` and :ref:`dm-wf-update-ncs` sections.
252
-
#. Get the rest of the dependencies using west:
253
-
254
-
.. code-block:: console
255
-
256
-
west update
257
-
258
-
#. Build the sample or application code as follows:
259
-
260
-
.. parsed-literal::
261
-
:class: highlight
262
-
263
-
west build -b *board_target* -d *destination_directory_name*
264
-
265
-
The board target should be ``thingy53/nrf5340/cpuapp`` or ``thingy53/nrf5340/cpuapp/ns`` when building samples for the application core.
266
-
The proper child image for ``thingy53/nrf5340/cpunet`` will be built automatically.
267
-
See :ref:`thingy53_build_pgm_targets` for details.
268
-
269
-
#. Program the sample or application:
270
-
271
-
a. Connect the Nordic Thingy:53 to the debug out port on a 10-pin external debug probe, for example nRF5340 DK, using a 10-pin JTAG cable.
272
-
#. Connect the external debug probe to the PC using a USB cable.
273
-
#. Make sure that the Nordic Thingy:53 and the external debug probe are powered on.
274
-
#. Use the following command to program the sample or application to the device:
275
-
276
-
.. code-block:: console
277
-
278
-
west flash
279
-
280
-
The device resets and runs the programmed sample or application.
The nRF5340 PDK has been deprecated with the introduction of the production-level nRF5340 DK.
@@ -46,10 +41,6 @@ It is meant for use with for :ref:`nrf53_audio_app`, which integrate the LE Audi
46
41
Given their complexity, the applications use custom building and programming procedures.
47
42
Refer to their documentation for more information.
48
43
49
-
The Nordic Thingy:53 is a battery-operated prototyping platform for IoT Systems.
50
-
The Nordic Thingy:53 integrates the nRF5340 SoC that supports Bluetooth® Low Energy, IEEE 802.15.4 based protocols and Near Field Communication (NFC).
51
-
The nRF5340 is augmented with the nRF21540 RF FEM (Front-end Module) Range extender that has an integrated power amplifier (PA)/low-noise amplifier (LNA) and nPM1100 Power Management IC (PMIC) that has an integrated dual-mode buck regulator and battery charger.
52
-
53
44
.. toctree::
54
45
:maxdepth:2
55
46
:caption:Subpages:
@@ -61,5 +52,4 @@ The nRF5340 is augmented with the nRF21540 RF FEM (Front-end Module) Range exten
0 commit comments