Home
last modified time | relevance | path

Searched refs:failure (Results 1 – 25 of 71) sorted by relevance

123

/Zephyr-Core-3.5.0/drivers/bbram/
Dbbram_emul.c43 int bbram_emul_set_standby_power_state(const struct device *dev, bool failure) in bbram_emul_set_standby_power_state() argument
47 data->status.standby_failure = failure; in bbram_emul_set_standby_power_state()
51 int bbram_emul_set_power_state(const struct device *dev, bool failure) in bbram_emul_set_power_state() argument
55 data->status.power_failure = failure; in bbram_emul_set_power_state()
71 bool failure = data->status.standby_failure; in bbram_emul_check_standby_power() local
74 return failure; in bbram_emul_check_standby_power()
80 bool failure = data->status.power_failure; in bbram_emul_check_power() local
83 return failure; in bbram_emul_check_power()
/Zephyr-Core-3.5.0/scripts/ci/
Dcheck_compliance.py159 def failure(self, text, msg=None, type_="failure"): member in ComplianceTest
224 self.failure(output)
398 self.failure(str(e))
443 self.failure(f"""
458 self.failure(f"""
483 self.failure(f"""
507 self.failure("""\
524 self.failure(f"Undefined Kconfig symbols:\n\n {undef_ref_warnings}")
593 self.failure(f"""
785 self.failure(f"""
[all …]
/Zephyr-Core-3.5.0/tests/ztest/fail/
DREADME.rst3 Ztest framework failure tests
9 In order to test the actual framework's failure cases, this test suite has to do something unique.
21 reporting a failure.
DKconfig5 prompt "Select the type of failure to test"
/Zephyr-Core-3.5.0/include/zephyr/drivers/
Dbbram.h243 int bbram_emul_set_standby_power_state(const struct device *dev, bool failure);
254 int bbram_emul_set_power_state(const struct device *dev, bool failure);
/Zephyr-Core-3.5.0/samples/tfm_integration/psa_crypto/
DCMakeLists.txt23 # insufficient memory failure while verifying signature. Increase it to 0x2400.
/Zephyr-Core-3.5.0/subsys/storage/stream/
DKconfig26 using the settings subsystem. In case of power failure or device
/Zephyr-Core-3.5.0/tests/kernel/common/
Dmultilib.txt13 Sample failure output ("thumb" used on Cortex-M instead of "thumb2"):
/Zephyr-Core-3.5.0/subsys/net/lib/dns/
Dresolve.c819 int failure = 0; in cb_recv() local
834 failure++; in cb_recv()
838 if (failure) { in cb_recv()
839 NET_DBG("DNS cname query failed %d times", failure); in cb_recv()
841 if (failure == j) { in cb_recv()
1121 int failure = 0; in dns_resolve_name() local
1280 failure++; in dns_resolve_name()
1291 if (failure) { in dns_resolve_name()
1292 NET_DBG("DNS query failed %d times", failure); in dns_resolve_name()
1294 if (failure == j) { in dns_resolve_name()
/Zephyr-Core-3.5.0/subsys/sd/
DKconfig47 Number of times to retry initialization commands in case of failure
85 Number of times to retry sending data to SD card in case of failure
/Zephyr-Core-3.5.0/samples/boards/stm32/uart/single_wire/
DREADME.rst29 After flashing the console output should not show any failure reports,
/Zephyr-Core-3.5.0/subsys/emul/
DKconfig23 approach 100% if all failure conditions are emulated.
/Zephyr-Core-3.5.0/drivers/ieee802154/
DKconfig.nrf584 There are few cases where the frame reception failure can happen because of
87 This options enables logging the reason of frame reception failure.
/Zephyr-Core-3.5.0/dts/arm/st/f0/
Dstm32f071.dtsi42 * result in a build failure.
Dstm32f091.dtsi17 * result in a build failure.
Dstm32f030Xc.dtsi27 * result in a build failure.
Dstm32f070Xb.dtsi26 * result in a build failure.
/Zephyr-Core-3.5.0/tests/kernel/timer/starve/
DREADME.txt14 without detecting a failure.
/Zephyr-Core-3.5.0/subsys/mgmt/osdp/
DKconfig.cp34 Time in seconds to wait after a command failure, and before retrying or
DKconfig89 Time in seconds to wait after a secure channel failure, and before
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dlwm2m.rst286 LOG_DBG("Bootstrap registration failure!");
298 LOG_DBG("Registration failure!");
314 LOG_DBG("Deregister failure!");
563 Occurs if there is a timeout or failure in bootstrap registration.
577 Occurs if there is a failure in the registration.
591 no registration update failure event is generated.
601 Occurs if there is a timeout or failure in the deregistration.
/Zephyr-Core-3.5.0/subsys/net/l2/ieee802154/
DKconfig.radio55 before declaring a channel access failure (MAC PIB attribute:
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.10.rst225 * :github:`1474` - tests/net/ipv6_fragment build failure, missing testcase.yaml
369 * :github:`4050` - zephyr.git/tests/kernel/obj_validation/testcase.yaml#test :Evaluation failure
385 * :github:`4186` - tcf.git/examples/test_network_linux_zephyr.py#_test :Compilation failure
417 …`4424` - Turning on network debug message w/ LwM2M sample client will result in stack check failure
425 * :github:`4480` - Compilation failure for qemu_x86 with CONFIG_DEBUG_INFO=y
426 * :github:`4481` - Build failure with CONFIG_NET_DEBUG_APP=y
468 * :github:`4757` - kw41z-frdm: assertion failure while setting IRQ priority
471 * :github:`4766` - tests: mem_pool: Fixed memory pool test case failure on quark d2000
490 * :github:`4881` - device_get_binding() returns failure in sample/drivers/crypto
541 * :github:`5145` - samples/bluetooth: Connection failure on peripheral CSC with Arduino 101
/Zephyr-Core-3.5.0/lib/libc/newlib/
DKconfig30 newlib heap. An assertion failure message will be displayed during
/Zephyr-Core-3.5.0/drivers/watchdog/
DKconfig.nxp_fs2627 watchdog failure occurs, the device increments this counter by 2. The

123