Home
last modified time | relevance | path

Searched refs:device (Results 1 – 25 of 30) sorted by relevance

12

/mcuboot-latest/sim/src/
Dlib.rs147 let device = match args.flag_device { in main() localVariable
152 status.run_single(device, align, 0xff); in main()
188 pub fn run_single(&mut self, device: DeviceName, align: usize, erased_val: u8) { in run_single()
189 warn!("Running on device {} with alignment {}", device, align); in run_single()
191 let run = match ImagesBuilder::new(device, align, erased_val) { in run_single()
194 warn!("Skipping {}: {}", device, msg); in run_single()
/mcuboot-latest/scripts/
Djgdb.sh8 JLinkGDBServer -if swd -device $SOC -speed auto
Djl.sh7 JLinkExe -speed auto -si SWD -device $SOC
Dflash.sh18 JLinkExe -device $SOC -si SWD -speed auto \
Dmcubin.bt32 // trying to view an image captured from a device, you can either
/mcuboot-latest/docs/release-notes.d/
Dfix-stuck-revert.md1 - Fixed issue for swap using move whereby a device could get
/mcuboot-latest/boot/zephyr/
Dserial_adapter.c58 static struct device const *uart_dev;
132 boot_uart_fifo_callback(const struct device *dev, void *user_data) in boot_uart_fifo_callback()
219 #error No serial recovery device selected in boot_uart_fifo_init()
DKconfig.firmware_loader22 the one used to place the device in bootloader mode.
39 bool "Check for device reset by pin"
DKconfig.serial_recovery25 prompt "Serial device"
33 The serial device to use will be fist selected via chosen
36 the "zephyr,uart-mcumgr" points to the same device as
74 memory access when data is written to a device with memory alignment
152 the one used to place the device in bootloader mode.
184 bool "Check for device reset by pin"
Dshared_data.c23 static const struct device *bootloader_info_dev =
Dflash_map_extended.c43 static const struct device *flash_dev = DEVICE_DT_GET(FLASH_DEVICE_NODE);
DKconfig104 When possible to map storage device, at least for read operations,
300 and requires the hash of the public key to be provisioned to the device
638 be used later by runtime services (e.g. by a device attestation service).
735 the one used to place the device in bootloader mode.
771 bool "Turns on LED indication when device is in DFU"
774 Device device activates the LED while in bootloader mode.
775 mcuboot-led0 alias must be set in the device's .dts
941 The size of a secondary buffer used for writing decompressed data to the storage device.
950 # Hidden selector for device-specific settings
985 # override USB device name
/mcuboot-latest/samples/zephyr/hello-world/
DCMakeLists.txt19 # This string ends up getting printed in the device console
/mcuboot-latest/boot/zephyr/include/mcuboot_config/
Dmcuboot_config.h408 const struct device* wdt = \
417 const struct device* wdt = \
/mcuboot-latest/docs/
Dreadme-nuttx.md15 …end.h>`, for enabling MCUboot to manage the application firmware image slots in the device storage.
21 … storage device. This is achieved by means of the `BCH` and `FTL` subsystems, which enable MCUboot…
52 …king-safe. NuttX implementation manages the MTD partitions via character device drivers. As file-d…
Dreadme-espressif.md121 2. Flash MCUboot in your device:
149 The output contains device information and its flash size:
163 3. Reset your device
306 role for ensuring that only authorized code will be executed on the device. This is done through
373 *Once the device makes its first full boot, these configurations cannot be reverted*
395 *Once the bootloader is flashed and the device resets, the **first boot will enable Secure Boot**
401 Flash the bootloader as following, with `--after no_reset` flag, so you can reset the device only
414 On its **first boot** the Secure Boot is not enabled on the device eFuses yet, neither the key nor
452 When enabling the Flash Encryption, the user can encrypt the content either using a **device
455 burning on the device, all read and write operations are decrypted/encrypted in runtime.
[all …]
DPORTING.md83 uniquely tied to region characterized by device, offset and size.
94 uint8_t fa_device_id; /** The device id (usually there's only one) */
107 /*< Obtains ID of a device the flash area `fa` described region resides on */
109 /*< Obtains offset, from the beginning of a device, the flash area described
/mcuboot-latest/ci/fih_test_docker/
Dfi_tester_gdb.sh77 -device loader,file=$TFM_IMAGE_PATH,addr=0x10080000 \
/mcuboot-latest/boot/mbed/
Dmcuboot_imgtool.cmake24 …E STRING "Path to key file (.pem) used to sign firmware updates for your device. The public key wi…
36 …TRING "Path to key file (.pem) used to encrypt firmware updates for your device. The private key w…
122 # This initial image is what should be flashed to a blank device (along with the bootloader).
158 # This image is what should be flashed to the secondary block device and passed to
/mcuboot-latest/boot/cypress/MCUBootApp/
DExternalMemory.md7 The demonstration device is CY8CPROTO-062-4343W board which is PSoC6 device with 2M of Flash availa…
DREADME.md5 Given solution demonstrates operation of MCUboot on Cypress' PSoC6 device.
83 Multi-image operation considers upgrading and verification of more then one image on the device.
97 This ensures two dependent applications can be accepted by device only in case both images are vali…
192 …ssing `SW3 MODE` button until `LED2 STATUS` blinks fast and mass storage device appeared in OS. Dr…
DMCUBootApp.ld64 * where 'xx' is the device group; for example, 'cy8c6xx7_cm4_dual.ld'.
77 /* The following regions define device specific memory regions and must not be changed. */
286 * device startup.
/mcuboot-latest/boot/cypress/platforms/PSOC_062_2M/CM0P/GCC_ARM/
Dcy8c6xxa_cm0plus.ld64 * where 'xx' is the device group; for example, 'cy8c6xx7_cm4_dual.ld'.
76 /* The following regions define device specific memory regions and must not be changed. */
266 * device startup.
/mcuboot-latest/boot/cypress/BlinkyApp/linker/
DBlinkyApp_template.ld68 * where 'xx' is the device group; for example, 'cy8c6xx7_cm0plus.ld'.
80 /* The following regions define device specific memory regions and must not be changed. */
265 * device startup.
/mcuboot-latest/boot/cypress/platforms/PSOC_062_2M/CM4/GCC_ARM/
Dcy8c6xxa_cm4_dual.ld67 * where 'xx' is the device group; for example, 'cy8c6xx7_cm0plus.ld'.
79 /* The following regions define device specific memory regions and must not be changed. */
276 * device startup.

12