Searched full:recovery (Results 1 – 25 of 95) sorted by relevance
1234
| /Zephyr-Core-3.5.0/tests/boot/mcuboot_recovery_retention/ |
| D | testcase.yaml | 24 bootloader.mcuboot.recovery.retention:
29 - recovery
30 bootloader.mcuboot.recovery.retention.mem:
40 - recovery
|
| /Zephyr-Core-3.5.0/drivers/can/ |
| D | Kconfig | 71 bool "Automatic recovery from bus-off"
74 This option enables the automatic bus-off recovery according to
75 ISO 11898-1 (recovery after 128 occurrences of 11 consecutive
76 recessive bits). When this option is enabled, the recovery API is not
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/src/ |
| D | test_iv_index.c | 67 /* Start recovery */ in test_ivu_recovery()
72 /* Start recovery before minimum delay */ in test_ivu_recovery()
87 /* Start recovery */ in test_ivu_recovery()
92 /* Start recovery before minimum delay */ in test_ivu_recovery()
161 TEST_CASE(ivu, recovery, "IVI: IV recovery procedure"),
|
| /Zephyr-Core-3.5.0/dts/bindings/i2c/ |
| D | nxp,imx-lpi2c.yaml | 24 GPIO to which the I2C SCL signal is routed. This is only needed for I2C bus recovery
30 GPIO to which the I2C SDA signal is routed. This is only needed for I2C bus recovery
|
| D | st,stm32-i2c-v1.yaml | 27 I2C bus recovery support.
33 I2C bus recovery support.
|
| D | st,stm32-i2c-v2.yaml | 51 I2C bus recovery support.
57 I2C bus recovery support.
|
| /Zephyr-Core-3.5.0/drivers/i2c/ |
| D | Kconfig.stm32 | 48 bool "Bus recovery support"
51 Enable STM32 driver bus recovery support via GPIO bitbanging.
|
| D | Kconfig | 23 The I2C shell supports scanning, bus recovery, I2C read and write
156 bool "Bus recovery support"
160 Enable LPI2C driver bus recovery support via GPIO bitbanging.
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/dfu/ |
| D | dfu_srv_persistence.sh | 14 # Test cases are designed to be run using single target. `dfu_cli_stop` test case in recovery part
47 # To test recovery from Verify Fail begin new distribution that will end there,
93 # To test recovery from Verify Fail begin new distribution that will end there,
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/ace/include/intel_ace15_mtpm/ |
| D | adsp_boot.h | 29 * DSP Boot / Recovery
31 * These registers are added by Intel outside of the Tensilica Core for boot / recovery
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/ace/include/intel_ace20_lnl/ |
| D | adsp_boot.h | 29 * DSP Boot / Recovery
31 * These registers are added by Intel outside of the Tensilica Core for boot / recovery
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/iv_index/ |
| D | iv_recovery.sh | 7 # test IV index recovery procedure
|
| /Zephyr-Core-3.5.0/samples/sensor/max17262/ |
| D | app.overlay | 18 recovery-voltage = <3880>;
|
| /Zephyr-Core-3.5.0/dts/bindings/regulator/ |
| D | regulator.yaml | 159 Recovery actions should be initiated. Zero can be passed to disable
185 Recovery actions should be initiated. Zero can be passed to disable
213 damaged. Recovery actions should be initiated. Zero can be passed to
239 damaged. Recovery actions should be initiated. Zero can be passed to
|
| /Zephyr-Core-3.5.0/dts/bindings/sensor/ |
| D | maxim,max17262.yaml | 39 recovery-voltage:
|
| /Zephyr-Core-3.5.0/tests/kernel/tickless/tickless_concept/src/ |
| D | main.c | 78 /**TESTPOINT: verify system clock recovery after exiting tickless idle*/ in ZTEST()
86 /**TESTPOINT: verify system clock recovery after exiting tickful idle*/ in ZTEST()
|
| /Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/ |
| D | chromebooks_adsp.rst | 31 hit the power key to enter recovery mode. Note: the touchscreen and
32 pad don't work in recovery mode, use the arrow keys to navigate.
44 Make a Recovery Drive
47 You will at some point wreck your device and need a recovery stick.
48 Install the Chromebook Recovery Utility from the Google Web Store and
54 Tiger Lake board). Note that recovery, when it happens, will not
216 about requiring a drive wipe on system recovery!*)
|
| /Zephyr-Core-3.5.0/subsys/retention/ |
| D | Kconfig | 51 e.g. button-less bootloader serial recovery mode entering from the
|
| D | blinfo_mcuboot.c | 94 /* Allowed keys are mode, signature_type, recovery, running_slot, bootloader_version in blinfo_handle_get()
101 } else if (settings_name_steq(name, "recovery", &next) && !next) { in blinfo_handle_get()
|
| /Zephyr-Core-3.5.0/doc/services/retention/ |
| D | blinfo.rst | 109 * ``blinfo/recovery`` The recovery type enabled in MCUboot
|
| D | index.rst | 146 example is to have a buttonless way of entering mcuboot's serial recovery
189 boot mode functions. If using mcuboot with serial recovery, it can be built
191 which will allow rebooting directly into the serial recovery mode by using:
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_srv.rst | 76 Transfer recovery
91 The BLOB Transfer Client sending the transfer must support transfer recovery for the transfer to
|
| /Zephyr-Core-3.5.0/boards/arm/efr32_thunderboard/ |
| D | efr32bg22_brd4184.dtsi | 17 /* If enabled, MCUboot uses this for recovery mode entrance */
|
| /Zephyr-Core-3.5.0/subsys/usb/device/class/dfu/ |
| D | Kconfig | 63 Make sure there is some kind of recovery mechanism.
|
| /Zephyr-Core-3.5.0/include/zephyr/retention/ |
| D | bootmode.h | 36 /** Bootloader boot mode (e.g. serial recovery for MCUboot) */
|
1234
