Searched refs:failure (Results 51 – 75 of 80) sorted by relevance
1234
/Zephyr-latest/doc/releases/ |
D | release-notes-1.12.rst | 48 * kernel/mempool: Handle transient failure condition 224 * Fixed a potential assertion failure in the controller related to white list 765 …ys/fs/fat_fs_api - test_fat_file and test_fat_dir results into Assertion failure on Arduino_101 du… 780 * :github:`8099` - tests/drivers/rtc/rtc_basic_api assertion failure on Arduino 101 / ARC 787 * :github:`8145` - samples/subsys/usb/dfu: Build failure, Reference to non-existent node or label "… 797 * :github:`8200` - Tests: arm_irq_vector_table: Assertion failure on nrf52840_pca10056
|
D | release-notes-2.6.rst | 48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change 1071 * :github:`35896` - frdm_k64f: build failure missing dt-bindings/clock/kinetis_sim.h: No such file … 1088 * :github:`35713` - tests: kernel.scheduler.multiq: test_k_thread_suspend_init_null failure 1149 * :github:`35390` - net.socket.tls.tls_ext: frdm_k64f test failure 1296 …17` - arch.interrupt.arm| arch.interrupt.extra_exception_info: lpcxpresso55s28 series: test failure 1299 * :github:`34909` - dma_loopback:lpcxpresso55s28_ns driver test failure 1363 * :github:`34482` - net_tunnel_virtual:frdm_k64f: build failure 1564 * :github:`33727` - mec15xxevb_assy6853: multiple tests failed due to assertion failure at kernel/s… 1604 * :github:`33542` - reel_board: samples/subsys/usb/hid/ timeout failure 1888 * :github:`32656` - reel_board: tests/lib/devicetree/devices/ build failure [all …]
|
D | release-notes-1.6.rst | 321 * ``ZEP-1124`` - tests/kernel/test_sprintf/microkernel/testcase.ini#test failure on frdm_k64f 354 * ``ZEP-1297`` - test/legacy/kernel/test_mail: failure on ARC platforms
|
D | release-notes-2.0.rst | 576 …ub:`18574` - Some platforms: “reel_board”, “frdm_k64f” and “sam_e70_xplained” are be built failure 691 …o/tinycrypt_hmac_prng and tests/crypto/mbedtls and tests/posix/fs build failure on mimxrt1015_evk 712 * :github:`18181` - Some platforms(e.g. sam_e70_xplained) will be flashed failure if the platforms … 817 * :github:`17581` - linker script packing failure with subsys/fb fonts and native_posix_64 855 * :github:`17376` - device tree diagnostic failure in enum 1170 * :github:`15823` - Build failure for spi_loopback on atsamr21_xpro 1213 * :github:`15664` - Zephyr modules failure report 1267 * :github:`15374` - PR 15230 introduces test failure for particle_argon 1365 * :github:`13444` - Build failure when including both socket.h and posix/time.h
|
D | release-notes-2.2.rst | 39 * :github:`24086` - Bluetooth: SMP: Existing bond deleted on pairing failure 760 * :github:`22968` - Bluetooth: controller: LEGACY: ASSERTION failure on invalid packet sequence 913 * :github:`22010` - Bluetooth 'central' failure on native_posix 914 * :github:`22003` - 'central' failure on nrf52_pca10040 930 * :github:`21846` - RFC: API: Counter: counter_read() has no way of indicating failure 1192 …635` - tests/subsys/fs/nffs_fs_api/common/nffs_test_utils.c fail with Assertion failure on nrf52840
|
D | release-notes-1.7.rst | 428 * ``ZEP-1745`` - Bluetooth samples build failure 445 * ``ZEP-1810`` - Build failure in net/lib/zoap with LLVM/icx
|
D | release-notes-3.1.rst | 1242 - :github:`45596` - samples: Code relocation nocopy sample has some unusual failure on nrf5340dk 1254 - :github:`45845` - tests: The failure test case number increase significantly in CMSIS DSP tests o… 1316 * :github:`45893` - MCUboot authentication failure with RSA-3072 key on i.MX RT 1160 EVK 1372 * :github:`45611` - GD32 build failure: CAN_MODE_NORMAL is redefined 1434 * :github:`45226` - samples/drivers/led_pwm: Build failure 1460 * :github:`44985` - tests: drivers: can: timing: failure to set bitrate of 800kbit/s on nucleo_g474… 1461 * :github:`44977` - samples: modules: canopennode: failure to initialize settings subsystem on nucl… 1658 * :github:`43739` - tests: dma: random failure on dma loopback suspend and resume case on twr_ke18f
|
D | release-notes-1.8.rst | 307 * ``ZEP-2057`` - crash in tests/net/rpl on qemu_x86 causing intermittent sanitycheck failure
|
D | release-notes-2.1.rst | 544 * :github:`20558` - Build failure for samples/bluetooth/peripheral\_hr/sample.bluetooth.peripheral\… 656 * :github:`19848` - stm32wb MPU failure 688 * :github:`19629` - tinycbor buffer overflow causing mcumgr image upload failure
|
/Zephyr-latest/arch/xtensa/ |
D | Kconfig | 94 NOPs after failure to lock a spinlock. This gives
|
/Zephyr-latest/doc/services/crypto/ |
D | psa_crypto.rst | 125 storage failure.
|
/Zephyr-latest/doc/kernel/drivers/ |
D | index.rst | 421 propagating return values unless the failure is expected to occur 429 returned on failure. See
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | tls_credentials_shell.rst | 201 …"``<STATUS>``", "Status code indicating success or failure with generating a digest of the listed …
|
D | net_l2.rst | 55 error code if there was a failure sending the network packet.
|
/Zephyr-latest/doc/develop/test/ |
D | bsim.rst | 59 failure, and in many cases to build several tests into the same binary.
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 203 your Pull Request (PR). You can see any failure results in the workflow 645 GitHub PR page, below the review status. Depending on the success or failure 651 In case of failure you can click on the "Details" link presented below the 652 failure message in order to navigate to ``Github Actions`` and inspect the
|
/Zephyr-latest/doc/develop/west/ |
D | west-apis.rst | 142 failure in this zephyr documentation that could not be fixed without
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | heap.rst | 29 returning a NULL pointer on an allocation failure.
|
/Zephyr-latest/doc/services/rtio/ |
D | index.rst | 97 sqe. A chain of sqe will however ensure ordering and failure cascading.
|
/Zephyr-latest/ |
D | LICENSE | 161 work stoppage, computer failure or malfunction, or any and all
|
D | CMakeLists.txt | 526 # in binaries, makes failure logs more deterministic and most 990 # To prevent CMake failure when a driver is enabled, for example: REGULATOR=y
|
/Zephyr-latest/doc/connectivity/bluetooth/ |
D | bluetooth-le-host.rst | 280 simplifies error handling by reducing rare failure conditions to a common
|
/Zephyr-latest/doc/security/ |
D | vulnerabilities.rst | 529 failure, or division by zero, resulting in a denial of service attack. 793 BT: Assertion failure on repeated LL_FEATURE_REQ 907 Truncated L2CAP K-frame causes assertion failure 910 to only one byte, causes assertion failure in previous releases of
|
/Zephyr-latest/boards/intel/adsp/doc/ |
D | intel_adsp_generic.rst | 322 Sometimes a flash failure or network miscommunication corrupts the state of
|
/Zephyr-latest/subsys/net/lib/lwm2m/ |
D | Kconfig | 222 is notified about the network failure. Once application is notified,
|
1234