| /Zephyr-latest/dts/common/espressif/ |
| D | partitions_0x1000_default_8M.dtsi | 20 label = "image-0";
25 label = "image-1";
35 label = "image-scratch";
|
| /Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 12 .. image:: images/version-info.jpg
27 .. image:: images/perspective-choose-other.jpg
33 .. image:: images/perspective-choose-ds.jpg
42 .. image:: images/create-new-configuration-database.jpg
48 .. image:: images/create-new-configuration-database_database-name.jpg
54 .. image:: images/create-new-configuration-database_shown-in-project-explorer.jpg
63 .. image:: images/create-new-model-configuration.jpg
73 .. image:: images/create-new-model-configuration_model-path.jpg
80 .. image:: images/create-new-model-configuration_model-use-V8R64-Generic.jpg
89 .. image:: images/create-new-launch-configuration_context-menu.jpg
[all …]
|
| /Zephyr-latest/soc/nordic/ |
| D | sysbuild.cmake | 20 set(image "vpr_launcher") variable
23 APPLICATION ${image}
30 sysbuild_cache_set(VAR ${image}_SNIPPET APPEND REMOVE_DUPLICATES ${launcher_snippet})
|
| /Zephyr-latest/soc/nxp/common/ |
| D | Kconfig.rom_loader | 5 bool "Create output image that NXP ROM can load from FlexSPI to ram"
9 Builds an output image that the BootROM can load from the
10 FlexSPI boot device into RAM region. The image will be loaded
|
| /Zephyr-latest/samples/subsys/usb/dfu/ |
| D | README.rst | 17 class provided by the Zephyr project depends on DFU image manager and
49 Build and sign a second application image e.g. :zephyr:code-sample:`hello_world`,
50 which will be used as an image for the update.
63 image.
65 Use the following command to backup the SLOT-0 image:
84 I: Primary image: magic=good, swap_type=0x3, copy_done=0x1, image_ok=0x1
85 I: Secondary image: magic=good, swap_type=0x2, copy_done=0x3, image_ok=0x3
89 I: Jumping to the first image slot
101 I: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
102 I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 10 upgrade the image of a Zephyr-based application at run time. It currently
16 The DFU subsystem deals with image management, but not with the transport
17 or management protocols themselves required to send the image to the target
26 The flash image API as part of the Device Firmware Upgrade (DFU) subsystem
28 image chunks to flash.
41 application images. It allows to select application image and boot type
58 `MCUboot boot loader`_. It interfaces with MCUboot and is aware of the image
82 to flash the Zephyr application image at the correct offset (right after the
|
| /Zephyr-latest/tests/drivers/flash/common/boards/ |
| D | b_u585i_iot02a_stm32u585xx_ns.overlay | 15 /* Non-secure image primary slot */
17 label = "image-0-nonsecure";
|
| /Zephyr-latest/modules/trusted-firmware-a/ |
| D | Kconfig | 11 additionally generate a TF-A image for the Secure Execution
12 environment, along with the Zephyr image. The Zephyr image
|
| /Zephyr-latest/boards/makerdiary/nrf52840_mdk_usb_dongle/ |
| D | fstab-debugger.dtsi | 24 label = "image-0";
28 label = "image-1";
32 label = "image-scratch";
|
| /Zephyr-latest/tests/boot/test_mcuboot/ |
| D | README.rst | 4 Tests MCUBoot's image swap support. This application is built in three parts
6 application is the main sysbuild target, and will request an image swap
9 that MCUBoot swaps to when the image swap is requested.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | dfu.rst | 41 node in the Upload Firmware procedure, then it distributes the uploaded image to other Target
47 image to the Target nodes.
58 :alt: Graphic overview of the DFU roles mesh nodes can have during the process of image
82 First, the image is uploaded to a Distributor in a mesh network by an external entity, such as a
84 image and all its metadata to the Distributor node inside the mesh network. The Distributor
85 stores the firmware image and its metadata persistently, and awaits further instructions from the
86 Initiator. The time required to complete the upload process depends on the size of the image.
97 Before the firmware image can be distributed, the Initiator transfers the list of Target nodes
98 and their designated firmware image index to the Distributor. Next, it tells the Distributor to
100 mesh network perform other duties. Once the firmware image has been transferred to the Target
[all …]
|
| /Zephyr-latest/drivers/video/ |
| D | Kconfig.ov7670 | 5 bool "OV7670 CMOS digital image sensor"
10 Enable driver for OV7670 CMOS digital image sensor device.
|
| D | Kconfig.ov5640 | 7 bool "OV5640 CMOS digital image sensor"
12 Enable driver for OV5640 CMOS digital image sensor device
|
| D | Kconfig.gc2145 | 5 bool "GC2145 CMOS digital image sensor"
10 Enable driver for GC2145 CMOS digital image sensor device.
|
| D | Kconfig.ov7725 | 7 bool "OV7725 CMOS digital image sensor"
12 Enable driver for OV7725 CMOS digital image sensor device.
|
| D | Kconfig.mt9m114 | 7 bool "MT9M114 Aptina CMOS digital image sensor"
12 Enable driver for MT9M114 CMOS digital image sensor device.
|
| D | Kconfig.ov2640 | 7 bool "OV2640 CMOS digital image sensor"
12 Enable driver for OV2640 CMOS digital image sensor device.
|
| /Zephyr-latest/include/zephyr/mgmt/mcumgr/grp/img_mgmt/ |
| D | img_mgmt_callbacks.h | 65 const uint8_t image; member
81 const uint8_t image; member
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/ |
| D | Kconfig.defconfig | 17 # secure image (TRUSTED_EXECUTION_SECURE=y), the secure FW image shall always
27 # If the secure firmware is to be combined with a non-secure image
28 # (TRUSTED_EXECUTION_SECURE=y), the secure FW image SRAM shall always
29 # be restricted to the secure image SRAM partition (sram-secure-partition).
31 # may be used by the image.
33 # For the non-secure version of the board, the firmware image SRAM is
|
| /Zephyr-latest/soc/nordic/nrf92/ |
| D | CMakeLists.txt | 10 # Ensure that image size aligns with 16 bytes so that MRAMC finalizes all writes
11 # for the image correctly
|
| /Zephyr-latest/subsys/bindesc/ |
| D | Kconfig.build_time | 28 The year the image was compiled, such as 2023
33 The month the image was compiled, such as 5 (May)
38 The day of the month the image was compiled, such as 9
43 The hour of the day the image was compiled, such as 13 in 13:34:52
48 The minute the image was compiled, such as 34 in 13:34:52
53 The second the image was compiled, such as 52 in 13:34:52
58 The UNIX time at which the image was compiled. This is an integer
82 This can also be used to set a specific time, when trying to reproduce an image. For
96 This can also be used to set a specific time, when trying to reproduce an image. For
108 This can also be used to set a specific time, when trying to reproduce an image. For
|
| /Zephyr-latest/samples/subsys/ipc/ipc_service/static_vrings/ |
| D | Kconfig | 10 Include remote build header files. Can be used if primary image
11 needs to be aware of size or base address of secondary image
|
| /Zephyr-latest/samples/subsys/ipc/openamp/ |
| D | Kconfig | 10 Include remote build header files. Can be used if primary image
11 needs to be aware of size or base address of secondary image
|
| /Zephyr-latest/samples/drivers/mbox_data/ |
| D | Kconfig | 10 Include remote build header files. Can be used if primary image
11 needs to be aware of size or base address of secondary image
|
| /Zephyr-latest/samples/drivers/ipm/ipm_mcux/ |
| D | Kconfig | 10 Include remote build header files. Can be used if primary image
11 needs to be aware of size or base address of secondary image
|
