| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 3 Device Firmware Update (DFU)
6 Bluetooth mesh supports the distribution of firmware images across a mesh network. The Bluetooth
7 mesh DFU subsystem implements the Bluetooth Mesh Device Firmware Update Model specification version
10 Bluetooth mesh DFU implements a distribution mechanism for firmware images, and does not put any
13 firmware validation and deployment to the application.
32 distribution of firmware images:
35 Target node is the receiver and user of the transferred firmware images. All its functionality is
41 node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
69 replace the Firmware Distribution Server model with a proprietary mechanism that will access the
[all …]
|
| D | dfd_srv.rst | 3 Firmware Distribution Server
6 The Firmware Distribution Server model implements the Distributor role for the
8 receive the firmware image binary from the Initiator node. It also instantiates a
9 :ref:`bluetooth_mesh_dfu_cli`, which it uses to distribute firmware updates throughout the mesh
14 Currently, the Firmware Distribution Server supports out-of-band (OOB) retrieval of firmware
17 The Firmware Distribution Server does not have an API of its own, but relies on a Firmware
21 Firmware slots
24 The Firmware Distribution Server is capable of storing multiple firmware images for distribution.
25 Each slot contains a separate firmware image with metadata, and can be distributed to other mesh
26 nodes in the network in any order. The contents, format and size of the firmware images are vendor
[all …]
|
| D | dfu_srv.rst | 3 Firmware Update Server
6 The Firmware Update Server model implements the Target node functionality of the
8 receive the firmware image binary from the Distributor node.
10 Together with the extended BLOB Transfer Server model, the Firmware Update Server model implements
11 all the required functionality for receiving firmware updates over the mesh network, but does not
14 Firmware images
17 The Firmware Update Server holds a list of all the updatable firmware images on the device. The full
20 started. Each firmware image in the image list must be independently updatable, and should have its
21 own firmware ID.
24 firmware update capabilities could have three entries in the firmware image list, each with their
[all …]
|
| D | dfu_cli.rst | 3 Firmware Update Client
6 The Firmware Update Client is responsible for distributing firmware updates through the mesh
7 network. The Firmware Update Client uses the :ref:`bluetooth_mesh_blob_cli` as a transport for its
|
| /Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/ |
| D | dfd.h | 17 * @defgroup bt_mesh_dfd Firmware Distribution models
22 /** Firmware distribution status. */
38 /** The requested firmware image is not stored on the Distributor. */
50 /** Another firmware image distribution is in progress. */
65 /** The Check Firmware OOB procedure did not find any new firmware. */
68 /** The suspension of the Distribute Firmware procedure failed. */
72 /** Firmware distribution phases. */
74 /** No firmware distribution is in progress. */
77 /** Firmware distribution is in progress. */
83 /** The Apply Firmware on Target Nodes procedure is being executed. */
[all …]
|
| D | dfd_srv.h | 9 * @defgroup bt_mesh_dfd_srv Firmware Distribution Server model
12 * @brief API for the Firmware Distribution Server model
85 * @brief Firmware Distribution Server model Composition Data entry.
95 /** Firmware Distribution Server callbacks: */
101 * @c io with a pointer to a writable BLOB stream for the Firmware Distribution
102 * Server to write the firmware image to.
104 * @param srv Firmware Distribution Server model instance.
115 /** @brief Firmware upload OOB start callback.
117 * Called at the start of an OOB firmware upload. The application must
118 * start a firmware check using an OOB mechanism, and then call
[all …]
|
| D | dfu.h | 20 * @defgroup bt_mesh_dfu Bluetooth Mesh Device Firmware Update
43 /** Ready to start a Receive Firmware procedure. */
49 /** The Receive Firmware procedure is being executed. */
52 /** The Verify Firmware procedure is being executed. */
55 /** The Verify Firmware procedure completed successfully. */
58 /** The Verify Firmware procedure failed. */
61 /** The Apply New Firmware procedure is being executed. */
64 /** Firmware transfer has been canceled. */
67 /** Firmware applying succeeded. */
70 /** Firmware applying failed. */
[all …]
|
| D | dfu_metadata.h | 9 * @defgroup bt_mesh_dfu_metadata Bluetooth mesh Device Firmware Update (DFU) metadata
28 /** Firmware version. */
30 /** Firmware major version. */
32 /** Firmware minor version. */
34 /** Firmware revision. */
36 /** Firmware build number. */
40 /** Firmware core type. */
50 /** Firmware metadata. */
52 /** New firmware version. */
54 /** New firmware size. */
[all …]
|
| D | dfu_srv.h | 9 * @defgroup bt_mesh_dfu_srv Firmware Update Server model
12 * @brief API for the Bluetooth mesh Firmware Update Server model
44 * @brief Firmware Update Server model entry.
53 /** @brief Firmware Update Server event callbacks. */
72 * @param srv Firmware Update Server instance.
87 * Called when the Firmware Update Server is ready to start a new DFU transfer.
97 * image, and there's no need to transfer it again. The Firmware Update model
102 * @param srv Firmware Update Server instance.
123 * firmware image, and call either @ref bt_mesh_dfu_srv_verified or
126 * If the transfer fails, the Firmware Update Server will be available for new
[all …]
|
| D | dfu_cli.h | 9 * @defgroup bt_mesh_dfu_cli Firmware Uppdate Client model
12 * @brief API for the Bluetooth mesh Firmware Update Client model
44 * @brief Firmware Update Client model Composition Data entry.
113 * @param cli Firmware Update Client model instance.
129 /** Firmware Update Client event callbacks. */
135 * @param cli Firmware Update Client model instance.
144 * @param cli Firmware Update Client model instance.
155 * @param cli Firmware Update Client model instance.
164 * @param cli Firmware Update Client model instance.
173 * @param cli Firmware Update Client model instance.
[all …]
|
| /Zephyr-Core-3.5.0/arch/arm/core/cortex_m/tz/ |
| D | Kconfig | 18 comment "Secure firmware"
21 comment "Non-secure firmware"
32 bool "Secure Firmware has Secure Entry functions"
35 Option indicates that ARM Secure Firmware contains
58 bool "Non-Secure Firmware uses Secure Entry functions"
61 Option indicates that ARM Non-Secure Firmware uses Secure
62 Entry functions provided by the Secure Firmware. The Secure
63 Firmware must be configured to provide these functions.
73 Firmware that contains secure entry functions, and allows
74 the Non-Secure Firmware to call into the Secure Firmware.
|
| /Zephyr-Core-3.5.0/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.partitions | 17 in the trusted-firmware-m repository for details regarding this
19 options are handled by the build system in the trusted-firmware-m
28 in the trusted-firmware-m repository for details regarding this
30 options are handled by the build system in the trusted-firmware-m
39 in the trusted-firmware-m repository for details regarding this
41 options are handled by the build system in the trusted-firmware-m
51 in the trusted-firmware-m repository for details regarding this
53 options are handled by the build system in the trusted-firmware-m
62 in the trusted-firmware-m repository for details regarding this
64 options are handled by the build system in the trusted-firmware-m
[all …]
|
| D | Kconfig.tfm | 56 string "Path to private key used to sign secure firmware images."
62 firmware images.
65 string "Path to private key used to sign non-secure firmware images."
71 firmware images.
191 versions of both the secure firmware and non-secure firmware. This sets
192 the secure firmware's version for rollback prevention.
199 versions of both the secure firmware and non-secure firmware. This sets
200 the non-secure firmware's version for rollback prevention.
225 The main one is the TF-M secure firmware. Optionally the TF-M
304 prompt "TF-M Firmware Framework model"
[all …]
|
| /Zephyr-Core-3.5.0/doc/services/device_mgmt/ |
| D | ota.rst | 9 Over-the-Air (OTA) Update is a method for delivering firmware updates to remote
13 infrastructure to host the firmware binary and implement a method of signaling
14 when an update is available. Security is a concern with OTA updates; firmware
17 The :ref:`dfu` section discusses upgrading Zephyr firmware using MCUboot. The
29 configured to observe your available firmware revisions on the Golioth Cloud.
32 TLS/DTLS, and the signed firmware binary is confirmed by MCUboot before the
43 REST api to detect firmware updates. When a new update is detected, the binary
45 upgrading the firmware.
56 signature before upgrading the firmware.
64 A Simple Management Protocol (SMP) server can be used to update firmware via
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/dma/ |
| D | dma_mcux_smartdma.h | 39 * @brief install SMARTDMA firmware
41 * Install a custom firmware for the smartDMA. This function allows the user
42 * to install a custom firmware into the smartDMA, which implements
43 * different API functions than the standard MCUX SDK firmware.
45 * @param firmware: address of buffer containing smartDMA firmware
46 * @param len: length of firmware buffer
48 void dma_smartdma_install_fw(const struct device *dev, uint8_t *firmware,
|
| /Zephyr-Core-3.5.0/drivers/dma/ |
| D | dma_mcux_smartdma.c | 178 * Initialize the SMARTDMA with firmware. The default firmware in dma_mcux_smartdma_init()
179 * from MCUX SDK is a display firmware, which has functions in dma_mcux_smartdma_init()
181 * user can install another firmware using `dma_smartdma_install_fw` in dma_mcux_smartdma_init()
205 * @brief install SMARTDMA firmware
207 * Install a custom firmware for the smartDMA. This function allows the user
208 * to install a custom firmware into the smartDMA, which implements
209 * different API functions than the standard MCUX SDK firmware.
211 * @param firmware: address of buffer containing smartDMA firmware
212 * @param len: length of firmware buffer
214 void dma_smartdma_install_fw(const struct device *dev, uint8_t *firmware, in dma_smartdma_install_fw() argument
[all …]
|
| /Zephyr-Core-3.5.0/samples/tfm_integration/ |
| D | tfm_integration.rst | 17 Trusted Firmware Platform Security Architecture (PSA) APIs are used for the
29 What is Trusted Firmware-M (TF-M)?
32 Trusted Firmware-M (TF-M) is the reference implementation of `Platform Security
39 supports firmware upgrade.
43 Trusted Firmware-M source code is available at
47 `<https://github.com/zephyrproject-rtos/trusted-firmware-m>`_.
|
| /Zephyr-Core-3.5.0/subsys/dfu/ |
| D | Kconfig | 64 bool "Erase flash progressively when receiving new firmware"
68 If enabled, flash is erased as necessary when receiving new firmware,
80 a new firmware. This is useful to avoid firmware reboot and test.
81 Another use is to ensure that firmware upgrade routines from internet
|
| /Zephyr-Core-3.5.0/boards/arm/nrf5340_audio_dk_nrf5340/ |
| D | Kconfig.defconfig | 13 # For the secure version of the board the firmware is linked at the beginning
15 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
19 # For the non-secure version of the board, the firmware
26 # If the secure firmware is to be combined with a non-secure image
32 # For the non-secure version of the board, the firmware image SRAM is
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/mesh/shell/ |
| D | Kconfig | 84 bool "Support for Firmware Distribution Server shell commands"
88 Firmware Distribution Server shell support.
91 bool "Support for Firmware Update Client shell commands"
95 Firmware Update Client shell support.
98 bool "Support for Firmware Update Server shell commands"
102 Firmware Update Server shell support.
|
| /Zephyr-Core-3.5.0/doc/develop/flash_debug/ |
| D | probes.rst | 29 microcontroller can support one or more types of firmware that communicate with
31 be programmed with DAPLink firmware to communicate with pyOCD or OpenOCD debug
32 host tools, or with J-Link firmware to communicate with J-Link debug host
83 CMSIS-DAP MCU-Link firmware, which is already installed by default. NXP
107 These probes do not have JLink firmware installed by default, and must be
136 LPC-Link2 firmware. Download and install `LPCScrypt`_ to get the firmware and
139 .. note:: Verify the firmware supports your board by visiting `Firmware for LPCXpresso`_
161 LPC-Link2 firmware. Download and install `LPCScrypt`_ to get the firmware and
164 .. note:: Verify the firmware supports your board by visiting `Firmware for LPCXpresso`_
188 OpenSDA firmware. NXP provides `OpenSDA DAPLink Board-Specific Firmwares`_.
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53v_db_40_nrf5340/ |
| D | Kconfig.defconfig | 27 # For the secure version of the board the firmware is linked at the beginning
29 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
33 # For the non-secure version of the board, the firmware
40 # If the secure firmware is to be combined with a non-secure image
46 # For the non-secure version of the board, the firmware image SRAM is
|
| /Zephyr-Core-3.5.0/boards/arm/nrf5340dk_nrf5340/ |
| D | Kconfig.defconfig | 28 # For the secure version of the board the firmware is linked at the beginning
30 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
34 # For the non-secure version of the board, the firmware
41 # If the secure firmware is to be combined with a non-secure image
47 # For the non-secure version of the board, the firmware image SRAM is
|
| /Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53_db_40_nrf5340/ |
| D | Kconfig.defconfig | 28 # For the secure version of the board the firmware is linked at the beginning
30 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
34 # For the non-secure version of the board, the firmware
41 # If the secure firmware is to be combined with a non-secure image
47 # For the non-secure version of the board, the firmware image SRAM is
|
| /Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/boards/ |
| D | nrf9160dk_nrf9160_ns.overlay | 8 * for the Secure (TF-M) firmware for the configuration that is
12 /* Increase the size of the Secure Firmware (TF-M).
21 /* Decrease the size of the Non-Secure Firmware (Zephyr),
|
