Searched refs:recover (Results 26 – 50 of 61) sorted by relevance
123
| /Zephyr-latest/drivers/can/ |
| D | can_sam.c | 137 .recover = can_mcan_recover,
|
| D | can_sam0.c | 175 .recover = can_mcan_recover,
|
| D | can_esp32_twai.c | 237 .recover = can_sja1000_recover,
|
| D | can_stm32h7_fdcan.c | 208 .recover = can_mcan_recover,
|
| D | can_numaker.c | 173 .recover = can_mcan_recover,
|
| D | can_stm32_fdcan.c | 521 .recover = can_mcan_recover,
|
| D | can_mcux_flexcan.c | 1271 .recover = mcux_flexcan_recover,
1314 .recover = mcux_flexcan_recover,
|
| D | can_tcan4x5x.c | 726 .recover = can_mcan_recover,
|
| D | can_shell.c | 1105 recover, &dsub_can_device_name,
|
| D | can_rcar.c | 1164 .recover = can_rcar_recover,
|
| D | can_renesas_ra.c | 982 .recover = can_renesas_ra_recover,
|
| D | can_stm32_bxcan.c | 1077 .recover = can_stm32_recover,
|
| /Zephyr-latest/boards/raytac/mdbt53_db_40/doc/ |
| D | index.rst | 214 protection is active, you will need to recover the chip before reflashing.
216 this command for more details on the related ``--recover`` option:
|
| /Zephyr-latest/drivers/i2c/ |
| D | i2c_shell.c | 356 SHELL_CMD_ARG(recover, &dsub_device_name,
|
| /Zephyr-latest/samples/boards/espressif/flash_encryption/ |
| D | README.rst | 12 recover most flash contents. This is a hardware feature that can be enabled in MCUboot build process
|
| /Zephyr-latest/boards/pine64/pinetime_devkit0/doc/ |
| D | index.rst | 152 $ nrfjprog -f NRF52 --recover
|
| /Zephyr-latest/boards/nordic/nrf5340dk/doc/ |
| D | index.rst | 266 protection is active, you will need to recover the chip before reflashing.
268 this command for more details on the related ``--recover`` option:
|
| /Zephyr-latest/boards/nordic/nrf7002dk/doc/ |
| D | index.rst | 266 protection is active, you will need to recover the chip before reflashing.
268 this command for more details on the related ``--recover`` option:
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | lwm2m.rst | 622 LwM2M engine cannot recover and have stopped.
626 where it cannot recover.
637 …- Try to recover network connection. Then restart the client by calling :c:func:`lwm2m_rd_client_s…
671 …- Try to recover network connection. Then restart the client by calling :c:func:`lwm2m_rd_client_s…
|
| /Zephyr-latest/samples/shields/x_nucleo_iks02a1/microphone/ |
| D | README.rst | 105 The dos2unix command is used to recover the situation in which the character 0x0a is
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | blob_srv.c | 914 if (srv->cb && srv->cb->recover) { in blob_srv_start()
916 err = srv->cb->recover(srv, &srv->state.xfer, &srv->io); in blob_srv_start()
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/doc/ |
| D | index.rst | 357 read-back protection is active, you will need to recover the chip
360 details on the related ``--recover`` option:
|
| /Zephyr-latest/tests/ztest/error_hook/ |
| D | README.txt | 92 test case, we do not recover it so far.
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 131 (recover) the last written ATE (Allocation Table Entry).
384 - Add a recovery function that can recover a storage partition if something went wrong
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 105 to the bus. Nodes in the bus-off state may recover after receiving 128
|
123
