Home
last modified time | relevance | path

Searched refs:firmware (Results 1 – 25 of 412) sorted by relevance

12345678910>>...17

/Zephyr-latest/modules/hal_infineon/wifi-host-driver/
DCMakeLists.txt60 # CYW43012 firmware
62 zephyr_include_directories(${hal_wifi_dir}/WiFi_Host_Driver/resources/firmware/COMPONENT_43012)
64 # firmware
66 set(cyw43xx_fw_bin ${hal_blobs_dir}/firmware/COMPONENT_43012/43012C0-mfgtest.bin)
67 zephyr_library_sources(${hal_wifi_dir_resources}/firmware/COMPONENT_43012/43012C0-mfgtest_bin.c)
69 set(cyw43xx_fw_bin ${hal_blobs_dir}/firmware/COMPONENT_43012/43012C0.bin)
70 zephyr_library_sources(${hal_wifi_dir_resources}/firmware/COMPONENT_43012/43012C0_bin.c)
74 # CYW4343W firmware
76 zephyr_include_directories(${hal_wifi_dir_resources}/firmware/COMPONENT_4343W)
78 # firmware
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfu.rst6 Bluetooth Mesh supports the distribution of firmware images across a mesh network. The Bluetooth
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
53 Target nodes and their firmware, and will control (and initiate) all firmware updates. The
83 phone or gateway (the Initiator). During the Upload stage, the Initiator transfers the firmware
85 stores the firmware image and its metadata persistently, and awaits further instructions from the
88 time-consuming Distribution stage. Once the firmware has been uploaded to the Distributor, the
93 accept the new firmware. Nodes that do not respond, or respond that they can't receive the new
[all …]
Ddfu_srv.rst8 receive the firmware image binary from the Distributor node.
11 all the required functionality for receiving firmware updates over the mesh network, but does not
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
25 own separate firmware ID.
44 firmware image metadata. The Firmware Update Server performs the transfer check by calling the
49 Distributor, and should indicate what effect the firmware update will have on the mesh state of the
61 :ref:`bluetooth_mesh_models_rpr_srv` is supported, the Composition Data of the new firmware image
[all …]
Ddfd_srv.rst8 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
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
33 firmware slot is stored internally, the application must provide a :ref:`bluetooth_mesh_blob_stream`
34 for reading and writing the firmware image.
/Zephyr-latest/doc/services/device_mgmt/
Dota.rst9 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-latest/modules/trusted-firmware-m/
DKconfig.tfm.partitions17 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 …]
/Zephyr-latest/doc/develop/manifest/external/
Dcannectivity.rst3 CANnectivity USB to CAN adapter firmware
9 `CANnectivity`_ is an open source firmware for Universal Serial Bus (USB) to Controller Area Network
12 The firmware implements the Geschwister Schneider USB/CAN device protocol (often referred to as
16 The firmware, which is based on Zephyr RTOS, allows turning your favorite microcontroller
24 The CANnectivity firmware repository is a Zephyr :ref:`module <modules>` which allows for reuse of
25 its components (i.e. the "gs_usb" protocol implementation) outside of the CANnectivity firmware
42 the CANnectivity firmware application by including its header:
/Zephyr-latest/boards/nxp/common/
Dopensda-debug.rst6 an :ref:`opensda-onboard-debug-probe`. The default firmware present on this
19 1. If the debug firmware has been modified, follow the instructions provided at
21 probe firmware on this board.
28 J-Link firmware, or a :ref:`jlink-external-debug-probe` can be attached to the
33 1. If the debug firmware has been modified, follow the instructions provided at
35 probe firmware on this board.
Drt1xxx-lpclink2-debug.rst6 an :ref:`lpc-link2-onboard-debug-probe`. The default firmware present on this
24 probe firmware on this board.
31 J-Link firmware, or a :ref:`jlink-external-debug-probe` can be attached to the
37 debug USB, as the J-Link firmware does not power the EVK via the
41 probe firmware on this board.
/Zephyr-latest/boards/raspberrypi/rpi_4b/doc/
Dindex.rst24 1. Download and place these firmware files:
26 …* `bcm2711-rpi-4-b.dtb <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/bcm2711…
27 …* `bootcode.bin <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/bootcode.bin>`_
28 * `start4.elf <https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/start4.elf>`_
/Zephyr-latest/boards/raytac/mdbt53_db_40/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
16 # For the non-secure version of the board, the firmware
23 # If the secure firmware is to be combined with a non-secure image
29 # For the non-secure version of the board, the firmware image SRAM is
/Zephyr-latest/boards/nordic/nrf5340_audio_dk/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
16 # For the non-secure version of the board, the firmware
23 # If the secure firmware is to be combined with a non-secure image
29 # For the non-secure version of the board, the firmware image SRAM is
/Zephyr-latest/boards/raytac/mdbt53v_db_40/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
16 # For the non-secure version of the board, the firmware
23 # If the secure firmware is to be combined with a non-secure image
29 # For the non-secure version of the board, the firmware image SRAM is
/Zephyr-latest/boards/nordic/nrf5340dk/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
16 # For the non-secure version of the board, the firmware
23 # If the secure firmware is to be combined with a non-secure image
29 # For the non-secure version of the board, the firmware image SRAM is
/Zephyr-latest/doc/develop/flash_debug/
Dprobes.rst30 the microcontroller the debug probe firmware runs on.
32 onboard debug probe microcontroller can support one or more types of firmware
34 OpenSDA microcontroller can be programmed with DAPLink firmware to communicate
35 with pyOCD or OpenOCD debug host tools, or with J-Link firmware to communicate
99 - :ref:`mcu-link-cmsis-onboard-debug-probe` (default firmware)
111 This is the default firmware installed on MCU-Link debug probes. The CMSIS-DAP
128 required to program the CMSIS-DAP firmware:
148 This debug probe firmware provides a JLink compatible debug interface,
154 These probes do not have JLink firmware installed by default, and must be
156 required to program the JLink firmware:
[all …]
/Zephyr-latest/boards/nordic/thingy53/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
16 # For the non-secure version of the board, the firmware
23 # If the secure firmware is to be combined with a non-secure image
29 # For the non-secure version of the board, the firmware image SRAM is
/Zephyr-latest/soc/nxp/rw/
Dfirmwares.ld7 /* For RW612, fw_cpu1 is used for wifi firmware.
9 * are placed next to each other, the firmware loader will detect the
/Zephyr-latest/subsys/dfu/
DKconfig59 Estimated size of update image data, which is used to prevent loading of firmware updates
71 bool "Erase flash progressively when receiving new firmware"
74 If enabled, flash is erased as necessary when receiving new firmware,
85 a new firmware. This is useful to avoid firmware reboot and test.
86 Another use is to ensure that firmware upgrade routines from internet
/Zephyr-latest/boards/actinius/icarus/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
15 # For the non-secure version of the board, the firmware
/Zephyr-latest/boards/norik/octopus_io_board/
DKconfig.defconfig6 # For the secure version of the board the firmware is linked at the beginning
8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # For the non-secure version of the board, the firmware
/Zephyr-latest/boards/norik/octopus_som/
DKconfig.defconfig6 # For the secure version of the board the firmware is linked at the beginning
8 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
11 # For the non-secure version of the board, the firmware
/Zephyr-latest/boards/actinius/icarus_bee/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
15 # For the non-secure version of the board, the firmware
/Zephyr-latest/boards/nordic/nrf9131ek/
DKconfig.defconfig8 # For the secure version of the board the firmware is linked at the beginning
10 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
13 # For the non-secure version of the board, the firmware
/Zephyr-latest/boards/actinius/icarus_som/
DKconfig.defconfig10 # For the secure version of the board the firmware is linked at the beginning
12 # be loaded by MCUboot. If the secure firmware is to be combined with a non-
15 # For the non-secure version of the board, the firmware
/Zephyr-latest/doc/
DLICENSING.rst18 * *Impact:* These files are used in Continuous Integration (CI) and never linked into the firmware.
31 into the firmware.
52 * *Impact:* This file is only linked into the firmware if :kconfig:option:`CONFIG_COVERAGE_GCOV` is
63 :zephyr:board:`kb1200_evb` board. It is never linked into the firmware.
73 * *Impact:* These files are only linked into the Thread-Metric RTOS Test Suite test firmware.
94 * *Impact:* These files are only linked into the firmware if :kconfig:option:`CONFIG_HDLC_RCP_IF` is
106 * *Impact:* These are only used for testing and never linked with the firmware.

12345678910>>...17