Searched refs:error (Results 1101 – 1125 of 1189) sorted by relevance
1...<<4142434445464748
| /Zephyr-latest/doc/develop/west/ |
| D | manifest.rst | 429 older versions of west will fail with an error message that explains the
441 # fail with an error message saying that west v0.10.0 or
520 that release. This may result in error messages that are harder to understand
1311 It's an error to set ``import`` to either ``true`` or ``false`` inside
2216 or fails with an error:
2222 The error message can help diagnose errors.
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/ |
| D | ace-link.ld | 167 * page-aligned or it will throw an error, not sure why since all
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | pb_adv.c | 409 link.cb->error(&bt_mesh_pb_adv, link.cb_data, err); in prov_failed()
|
| /Zephyr-latest/drivers/usb/device/ |
| D | usb_dc_stm32.c | 36 #error "Only one interface should be enabled at a time, OTG FS or OTG HS"
|
| /Zephyr-latest/cmake/linker/armlink/ |
| D | scatter_script.cmake | 328 # # ToDo: The code below had en error in original implementation, causing
|
| /Zephyr-latest/drivers/i2s/ |
| D | i2s_esp32.c | 25 #error "Only SoCs with GDMA peripheral are supported!"
|
| /Zephyr-latest/doc/services/storage/settings/ |
| D | index.rst | 220 /* read-out error */
|
| /Zephyr-latest/samples/net/mqtt_publisher/ |
| D | README.rst | 291 means that an error was detected and a new connect message will be sent.
|
| /Zephyr-latest/tests/unit/util/ |
| D | main.c | 145 #define A_BUILD_ERROR (this would be a build error if you used || or &&)
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.1.rst | 77 - Close a pipe, waking up all pending readers and writers with an error code. No further
735 when ``size`` parameter is set to 0 and will return error in such case. User is now
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 188 For example, if you set a breakpoint in an error handler, a snapshot trace can show the sequence
189 of events leading up to the error. Snapshot tracing is also easy to begin with, since it doesn't
|
| /Zephyr-latest/dts/arm/nxp/ |
| D | nxp_s32z27x_r52.dtsi | 715 interrupt-names = "rx_tx_mru", "error";
729 interrupt-names = "rx_tx_mru", "error";
|
| D | nxp_s32k344_m7.dtsi | 674 no-error-irq;
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 382 drivers: sensor: abcd1234: fix bus I/O error handling
385 the response packet from the device which signals that an error
387 buffer. Fix it by checking the flag and adding an error path.
|
| /Zephyr-latest/drivers/serial/ |
| D | uart_nrfx_uarte2.c | 358 data->async->err = event->data.error.error_mask; in evt_handler()
|
| /Zephyr-latest/scripts/tests/twister/ |
| D | test_harness.py | 524 assert logger.error.called
|
| /Zephyr-latest/boards/phytec/phyboard_polis/doc/ |
| D | index.rst | 176 transceiver to be not set. This causes a ENETDOWN error when trying to send
|
| /Zephyr-latest/drivers/flash/ |
| D | nrf_qspi_nor.c | 69 #error "No size specified. 'size' or 'size-in-bytes' must be set"
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 280 simplifies error handling by reducing rare failure conditions to a common
|
| /Zephyr-latest/drivers/gpio/ |
| D | gpio_pcal64xxa.c | 67 #error "Cannot determine the internal data type size"
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 182 error-prone, more readable and more flexible. On the other hand, C99
|
| /Zephyr-latest/tests/subsys/fs/nvs/src/ |
| D | main.c | 16 #error "Run only on qemu_x86, mps2_an385, or a posix architecture based target (for ex. native_sim)"
|
| /Zephyr-latest/doc/services/shell/ |
| D | index.rst | 399 as one argument. If shell won't find a handler it will display an error message.
479 shell_error(sh, "Print error text.");
|
| /Zephyr-latest/subsys/ipc/ipc_service/backends/ |
| D | ipc_icbmsg.c | 1028 .error = NULL, in open()
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 76 accessing or compromising more critical parts of the system, and error
|
1...<<4142434445464748
