Home
last modified time | relevance | path

Searched refs:recover (Results 1 – 25 of 61) sorted by relevance

123

/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/dfu/
Ddfu_srv_recovery.sh19 -- -argstest recover=0 expected-phase=2
24 -- -argstest recover=1 expected-phase=3
29 -- -argstest recover=1 expected-phase=4
34 -- -argstest recover=1 expected-phase=6
40 -- -argstest recover=1 expected-phase=8
46 -- -argstest recover=0 expected-phase=2
51 -- -argstest recover=1 expected-phase=3
56 -- -argstest recover=1 expected-phase=4
61 -- -argstest recover=1 expected-phase=6
67 -- -argstest recover=1 expected-phase=8
Ddfu_srv_recovery_verify_fail.sh16 -- -argstest recover=0 expected-phase=5
21 -- -argstest recover=1 expected-phase=6
27 -- -argstest recover=0 expected-phase=5
32 -- -argstest recover=1 expected-phase=6
/Zephyr-latest/scripts/west_commands/runners/
Dnrfjprog.py21 reset=True, tool_opt=None, force=False, recover=False, argument
25 tool_opt, force, recover)
43 recover=args.recover, qspi_ini=args.qspi_ini)
Dnrfutil.py21 reset=True, tool_opt=None, force=False, recover=False, argument
25 tool_opt, force, recover)
46 recover=args.recover,
Dnrf_common.py79 reset=True, tool_opt=None, force=False, recover=False): argument
90 self.recover = bool(recover)
575 if self.recover:
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_srv.rst80 will attempt to recover the transfer. When the Bluetooth Mesh subsystem is started (for instance by
82 the :c:member:`recover <bt_mesh_blob_srv_cb.recover>` callback if there is any. In the recover
83 callback, the user must provide a BLOB stream to use for the rest of the transfer. If the recover
85 If no recover callback is implemented, transfers are always abandoned after a reboot.
/Zephyr-latest/boards/nordic/nrf54l15dk/doc/
Dindex.rst117 ERROR: your device. Please use --recover to unlock the device.
120 To disable the readback protection, you must *recover* your device.
122 Enter the following command to recover the core::
124 west flash --recover
126 The ``--recover`` command erases the flash memory and then writes a small binary into
/Zephyr-latest/drivers/i2c/
DKconfig.mcux24 must be enabled to allow the driver to fully recover.
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig.defconfig10 # A workaround for HWMv2 to recover SOF arch/xtensa defaults overridden by arch/host.
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dblob_srv.h125 int (*recover)(struct bt_mesh_blob_srv *srv, member
Ddfu_srv.h152 int (*recover)(struct bt_mesh_dfu_srv *srv, member
/Zephyr-latest/scripts/west_commands/tests/
Dtest_nrf.py64 recover: bool
476 r = 'recover' if test_case.recover else 'no_recover'
565 recover=test_case.recover)
596 if test_case.recover:
/Zephyr-latest/doc/build/flashing/
Dconfiguration.rst41 An example flashing configuration for a ``soc.yml`` is shown below in which the ``--recover``
50 '--recover':
103 west flash --recover
/Zephyr-latest/boards/nordic/nrf5340_audio_dk/doc/
Dindex.rst81 protection is active, you will need to recover the chip before reflashing.
83 this command for more details on the related ``--recover`` option:
/Zephyr-latest/drivers/can/
Dcan_fake.c117 .recover = fake_can_recover,
Dcan_kvaser_pci.c147 .recover = can_sja1000_recover,
Dcan_mcux_mcan.c148 .recover = can_mcan_recover,
Dcan_nrf.c71 .recover = can_mcan_recover,
/Zephyr-latest/doc/hardware/peripherals/can/
Dshell.rst36 * :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE` enables the ``can recover`` subcommand.
259 The ``can recover`` subcommand can be used for initiating manual recovery from a CAN bus-off event
264 uart:~$ can recover can@0
271 The ``recover`` subcommand is only available if :kconfig:option:`CONFIG_CAN_MANUAL_RECOVERY_MODE`
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_dfu.c56 static bool recover; variable
85 .dest = &recover, in test_args_parse()
235 if (!recover) { in target_dfu_recover()
284 .recover = target_dfu_recover,
857 if (recover) { in dfu_cli_inputs_prepare()
1551 if (!recover) { in test_target_dfu_stop()
/Zephyr-latest/tests/subsys/logging/log_blocking/
DREAME.md92 automatically recover from a stall.
95 backends that are unable to recover from stalling the log processing thread.
/Zephyr-latest/subsys/bluetooth/mesh/
Ddfu_srv.c546 if (!srv->cb->recover || in blob_recover()
552 return srv->cb->recover(srv, &srv->imgs[srv->update.idx], io); in blob_recover()
558 .recover = blob_recover,
/Zephyr-latest/include/zephyr/drivers/
Dcan.h513 can_recover_t recover; member
1456 if (api->recover == NULL) { in z_impl_can_recover()
1460 return api->recover(dev, timeout); in z_impl_can_recover()
/Zephyr-latest/arch/posix/
DCMakeLists.txt175 zephyr_compile_options(-fsanitize-recover=all)
176 target_compile_options(native_simulator INTERFACE "-fsanitize-recover=all")
/Zephyr-latest/scripts/coccinelle/
Dms_timeout.cocci28 |can_(write|recover)

123