Searched refs:reset (Results 1 – 18 of 18) sorted by relevance
39 bool "Check for device reset by pin"42 Checks if the module reset was caused by the reset pin and will
144 uint32_t reset; member239 ((void (*)(void))vt->reset)(); in do_boot()
184 bool "Check for device reset by pin"187 Checks if the module reset was caused by the reset pin and will
213 firmware. The clean-up sets these registers to their warm-reset681 but it doesn't relocate vector in its reset handler.873 bool "Verify reset address of image in secondary slot"879 Verify that the reset address in the image located in the secondary slot
23 mon reset 2
45 Now reset the target::47 $ pyocd commander -c reset62 $ pyocd commander -c reset
12 - `CONFIG_MCUBOOT_WATCHDOG`: If `CONFIG_WATCHDOG` is enabled, MCUboot shall reset the watchdog time…27 …d triggering the firmware update process for the next boot after a system reset. There is also the…
397 Flash the bootloader as following, with `--after no_reset` flag, so you can reset the device only498 reset the device.*850 mcumgr -c esp reset
28 so your SoC runs it out of reset. If there are multiple updateable images
52 - Use general flash operations to determine the flash reset vector. This
5 code, specifically testing untimely reset scenarios to make sure the
90 -c "init; reset init; program PATH_TO_APPLICATION.hex" \91 -c "resume; reset; exit"
185 -c "init; reset init; program PATH_TO_APPLICATION.hex" \186 -c "resume; reset; exit"
93 * Reset_Handler : Entry of reset handler
92 * Reset_Handler : Entry of reset handler
96 * Reset_Handler : Entry of reset handler
95 * Reset_Handler : Entry of reset handler
1564 for reset in &mut resets { in try_random_fails()1573 *reset = reset_counter; in try_random_fails()