Searched refs:recovery (Results 1 – 25 of 60) sorted by relevance
123
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig.ambiq | 31 bool "Bus recovery support"
34 Enable AMBIQ driver bus recovery support via GPIO bitbanging.
|
| D | Kconfig.stm32 | 47 bool "Bus recovery support"
50 Enable STM32 driver bus recovery support via GPIO bitbanging.
|
| D | Kconfig | 22 The I2C shell supports scanning, bus recovery, I2C read and write
212 bool "Bus recovery support"
216 Enable LPI2C driver bus recovery support via GPIO bitbanging.
|
| /Zephyr-latest/samples/sensor/max17262/ |
| D | app.overlay | 18 recovery-voltage = <3880>;
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/ |
| D | Kconfig.nrfwifi | 647 bool "RPU recovery mechanism"
654 Enable the RPU recovery mechanism to recover from an RPU (nRF70) hang.
657 the recovery process, and it is the application's responsibility to
662 int "RPU recovery propagation delay in milliseconds"
666 before powering it up. This delay is required to ensure that the recovery
675 int "RPU recovery power save active timeout in milliseconds"
678 Power save active timeout in milliseconds, after which the RPU recovery
691 bool "RPU recovery debug logs"
693 Enable RPU recovery debug logs to help debug the RPU recovery mechanism.
696 int "RPU recovery quiet period in milliseconds"
[all …]
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig | 92 bool "Manual bus-off recovery support"
94 Enable support for manual (non-automatic) recovery from bus-off state. Not all CAN
95 controllers support manual recovery mode.
|
| /Zephyr-latest/boards/silabs/dev_kits/sltb010a/ |
| D | sltb010a.dts | 20 /* If enabled, MCUboot uses this for recovery mode entrance */
|
| /Zephyr-latest/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-latest/boards/silabs/dev_kits/xg27_dk2602a/ |
| D | xg27_dk2602a.dts | 24 /* If enabled, MCUboot uses this for recovery mode entrance */
|
| /Zephyr-latest/subsys/retention/ |
| D | Kconfig | 51 e.g. button-less bootloader serial recovery mode entering from the
|
| /Zephyr-latest/subsys/fs/nvs/ |
| D | Kconfig | 41 bool "Non-volatile Storage bad memory region recovery"
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | test_iv_index.c | 161 TEST_CASE(ivu, recovery, "IVI: IV recovery procedure"),
|
| /Zephyr-latest/subsys/usb/device/class/dfu/ |
| D | Kconfig | 63 Make sure there is some kind of recovery mechanism.
|
| /Zephyr-latest/doc/build/flashing/ |
| D | configuration.rst | 98 both applications and will only perform a single device recovery operation when programming the
105 If the above was ran without the flashing configuration, the recovery process would be ran twice
|
| /Zephyr-latest/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
|
| D | blob_cli.rst | 72 groups. This can lead to longer recovery periods at the end of each block, and increases the risk of
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | shell.rst | 19 sending and receiving of CAN frames, and bus recovery.
259 The ``can recover`` subcommand can be used for initiating manual recovery from a CAN bus-off event
267 The subcommand accepts an optional bus recovery timeout in milliseconds. If no timeout is specified,
268 the command will wait indefinitely for the bus recovery to succeed.
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
| D | index.rst | 117 2. Using MCUboot in serial recovery mode
176 applications using MCUboot's serial recovery mode. This process does not
213 recovery mode. We'll use the :zephyr:code-sample:`smp-svr` sample since it's ready to be
217 #. Boot into MCUboot serial recovery mode by plugging the board in with the SW1
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 29 hit the power key to enter recovery mode. Note: the touchscreen and
30 pad don't work in recovery mode, use the arrow keys to navigate.
45 You will at some point wreck your device and need a recovery stick.
52 Tiger Lake board). Note that recovery, when it happens, will not
214 about requiring a drive wipe on system recovery!*)
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | hci_nxp_setup.c | 713 bool recovery = false; in fw_upload_change_speed() local
749 if (recovery) { in fw_upload_change_speed()
764 recovery = true; in fw_upload_change_speed()
|
| /Zephyr-latest/drivers/i3c/ |
| D | Kconfig | 24 The I3C shell supports info, bus recovery, CCC, I3C read and
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.7.rst | 305 * Support for manual bus-off recovery was reworked (:github:`69460`):
307 * Automatic bus recovery will always be enabled upon driver initialization regardless of Kconfig
308 options. Since CAN controllers are initialized in "stopped" state, no unwanted bus-off recovery
312 … option enables support for the :c:func:`can_recover()` API function and a new manual recovery mode
317 recovery mode via the :c:func:`can_get_capabilities` API function. The application can then
318 either fail initialization or rely on automatic bus-off recovery. Having this as a mode
319 furthermore allows CAN controller drivers not supporting manual recovery mode to fail early in
|
| /Zephyr-latest/samples/subsys/usb/dfu/ |
| D | README.rst | 125 For example via a debugger or Mcuboot's recovery mode.
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 44 all updates need to be performed using MCUboot serial recovery.
|
123
