Set a convenient latency for each platform, since each platform
reacts differently to the driver.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
The optee suite was failing in test_suspend() after a call to
k_aligned_alloc() which returns -ENOMEM. The alignment requirement is
4096 bytes, which seems reasonable, but what is odd about that is
that the alignment fails in spite of
CONFIG_SRAM_SIZE=145131134582784
and
CONFIG_HEAP_MEM_POOL_SIZE=270044
So there is plenty of memory available for this test and alignment
considerations should not be an issue.
Removing `CONFIG_DEBUG=y` solved the problem for me.
Signed-off-by: Chris Friedt <cfriedt@tenstorrent.com>
This test fails sporadically on SMP, so make it run only on one CPU.
Related to zephyrproject-rtos/zephyr#91620
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
add scenario in build-only operation to check for CI failures
when interrupt is disabled for the STM32 i2c driver.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
add arduino_i2c node in overlay files to be enable building the i2c_api
test on multiple stm32 boards,compatible for both i2c V1 and V2
driver.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
According to RFC 793, the seqnum test includes 4 cases when STATE >
TCP_SYN_SENT:
Seg-len Recv-win Test
------- -------- ---------------------------------------
0 0 SEG.SEQ = RCV.NXT
0 >0 RCV.NXT =< SEG.SEQ < RCV.NXT+RCV.WND
>0 0 not acceptable
>0 >0 RCV.NXT =< SEG.SEQ < RCV.NXT+RCV.WND
or RCV.NXT =< SEG.SEQ+SEG.LEN-1 <RCV.NXT+RCV.WND
After the seq validation, the 'send duplicated ACK' code in FIN_WAIT1/
2/CLOSING/TIMEWAIT state processing is duplicated, so remove them.
Added TEST_CLIENT_SEQ_VALIDATION ztest case in tests/net/tcp.
Signed-off-by: Shrek Wang <inet_eman@outlook.com>
clock control is required for "fast instances" so assert clock
is enabled alongside PM DEVICE RUNTIME. Update UART tests to
reflect this requirenment.
Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
Add a new test suite for the Renesas ELC driver.
Signed-off-by: Khanh Nguyen <khanh.nguyen.wz@bp.renesas.com>
Signed-off-by: Khoa Nguyen <khoa.nguyen.xh@renesas.com>
When testing y2k rollover, the seconds value can easily be off by one
since there is no guarantee that the RTC will be exactly on the second
boundary.
Relax the check to allow for a one second difference.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Ensure the alarm tests exercise rollover scenarios by setting RTC time
to a few seconds before midnight on a December 31st and alarm time to a
few seconds after midnight on the following day.
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Add nRF specific test to check if it possible for multiple users
to enable XIP independently and also if XIP can be successfully
re-enabled (see fb1d0785ae).
Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
On arrays DT_ENUM_HAS_VALUE() and DT_INST_ENUM_HAS_VALUE()
were only checking the first index, this changes it to check all indexes.
Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
The nucleo_f746zg board doesn't handle RX/TX buffers in
non-cacheable memory when required. This leads to an error
in the test_adc_api with the log:
Supplied buffer is not in a non-cacheable region.
Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>
If GPIO_DISCONNECTED is not supported by GPIO driver, then try to configure
the pin to be input, otherwise there will be some unstable signal between
two test pins.
Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>
Add missing tests for edge cases (ex. peek on empty heap, push to full
heap, ...) to get to 100% coverage (lines & branches)
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
make test cases more readable using more direct assert_ macros, for
example zassert_not_null(foo, ...) instead of
zassert_true(foo != NULL, ...).
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
Add test case verifying that offloaded DNS APIs are called as expected
and that enabling/disabling DNS offloading at runtime works.
Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>
Implemented unit tests for the crc4 and crc4_ti functions as they were
missed when they were introduced
Signed-off-by: Benjamin Cabé <benjamin@zephyrproject.org>
remove phy related configs from eth config.
phy related configs chould go directly into the phy.
Most ethernet drivers didn't support the now removed
functions yet. Users should instead use `phy_configure_link()`
together with the `net_eth_get_phy()` function.
Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
This reverts commit 28bd478a0b.
This commit can be reverted as the cause of test failure
has been removed in ipc service by increasing workqueue stack size.
Signed-off-by: Adam Kondraciuk <adam.kondraciuk@nordicsemi.no>
When CONFIG_TIMEOUT_64BIT is y, positive values are relative/delta
timeouts and negative values are absolute timeouts, except
for two special values. -1 is K_WAIT_FOREVER and 0 is K_NO_WAIT.
The reserved value of -1 means INT64_MAX is not a valid argument
to K_TIMEOUT_ABS_TICKS(), but there was no check. If a literal
was passed, a preprocessor/compiler warning would be generated
for overflow, but if a variable was passed as the argument,
then the code would compile but not work correctly since the
absolute timeout would be changed to a relative one. One
example of this is task_wdt_init() if no channels are enabled.
Rather than just fixing task_wdt, and trying to find other cases
in an adhoc way, this CL changes K_TIMEOUT_ABS_TICKS() to
limit the larges value to (INT64_MAX-1). It does so silently,
but given the range of int64_t, there should be no practical
difference.
Also, change the implementation for Z_IS_TIMEOUT_RELATIVE() to
fix the case where INT64_MAX relative timeout was being
improperly reported as being not a relative timeout. This was
again due to the -1 reserved value.
Add some tests for these changes to the timer_api test.
Signed-off-by: Mike J. Chen <mjchen@google.com>
In 9.3 due to font licensing issues LV_FONT_SIMSUN_16_CJK was deprecated.
Instead select now LV_FONT_SOURCE_HAN_SANS_SC_16_CJK symbol.
Signed-off-by: Fabian Blatz <fabianblatz@gmail.com>
The llext-edk test case is timing out on some workloads, so increase the
timeout to 120 seconds to accommodate longer execution times.
Signed-off-by: Luca Burelli <l.burelli@arduino.cc>
When not using dynamic interrupt mapping, various interrupt tables are
configured to be stored in read-only memory in the linker script.. Mark
them const so that the linker doesn't complain.
This affects _sw_isr_table, _irq_vector_table, and z_shared_sw_isr_table in
arch/common along with _VectorTable in arch/arc.
Signed-off-by: Keith Packard <keithp@keithp.com>
The mode is activated by the CONFIG_MODBUS_NONCOMPLIANT_SERIAL_MODE option
and allows any stop-bit setting for the serial port.
Signed-off-by: Maksim Salau <msalau@iotecha.com>
The is_valid_gap_packet_len check for
btp_gap_ev_periodic_transfer_received_ev referenced a field
that was recently removed.
Modify the check to just check the size, as the event now
has not variable length fields.
Signed-off-by: Emil Gydesen <emil.gydesen@nordicsemi.no>
The test which measures and validates transfer times is using the
helper spi_loopback_transceive() to perform the transfer. This
helper internally gets the spi controller, which is useful for
most tests, but for this one, it means the time to get and put
the spi controller is included in the transfer time measurement.
This commit gets the spi controller before calling
spi_loopback_transceive() which results in only the actual
transfer time being measured.
Before this commit, on the nrf54h20:
START - test_spi_complete_multiple_timed
Transfer took 745 us vs theoretical minimum 108 us
Latency measurement: 637 us
PASS - test_spi_complete_multiple_timed in 0.008 seconds
START - test_spi_complete_multiple_timed
Transfer took 700 us vs theoretical minimum 54 us
Latency measurement: 646 us
Assertion failed at ...
Very high latency
FAIL - test_spi_complete_multiple_timed in 0.027 seconds
After this commit:
START - test_spi_complete_multiple_timed
Transfer took 250 us vs theoretical minimum 108 us
Latency measurement: 142 us
PASS - test_spi_complete_multiple_timed in 0.008 seconds
START - test_spi_complete_multiple_timed
Transfer took 204 us vs theoretical minimum 54 us
Latency measurement: 150 us
PASS - test_spi_complete_multiple_timed in 0.008 seconds
Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
The spi_loopback test suite creates three internal threads. The
stack sizes for these threads is hardcoded to 512, which is to little
for some socs, namely the nrf54h20 cpuapp if pm device runtime is
enabled. Instead, determine the stack sizes the same way ztest
stack sizes are determined.
Signed-off-by: Bjarki Arge Andreasen <bjarki.andreasen@nordicsemi.no>
Currently, every boards that implement a memory controller add an entry
in tests/drivers/memc/ram/testcase.yaml. However, the configuration is
exactly the same for all the boards. So, we can just consider that any
board that declare "memc" capability has to be tested.
For the record here are the boards that has the memc capability:
adi/apard32690/apard32690_max32690_m4.yaml
adi/eval_adin1110ebz/adi_eval_adin1110ebz.yaml
adi/max32690evkit/max32690evkit_max32690_m4.yaml
arduino/giga_r1/arduino_giga_r1_stm32h747xx_m7.yaml
arduino/portenta_h7/arduino_portenta_h7_stm32h747xx_m7_1_0_0.yaml
arduino/portenta_h7/arduino_portenta_h7_stm32h747xx_m7_4_10_0.yaml
atmel/sam/sam4s_xplained/sam4s_xplained.yaml
renesas/da1469x_dk_pro/da1469x_dk_pro.yaml
sifive/hifive_unmatched/hifive_unmatched_s7.yaml
sifive/hifive_unmatched/hifive_unmatched_u74.yaml
silabs/radio_boards/siwx917_rb4342a/siwx917_rb4342a.yaml
st/stm32f746g_disco/stm32f746g_disco.yaml
st/stm32f7508_dk/stm32f7508_dk.yaml
st/stm32f769i_disco/stm32f769i_disco.yaml
st/stm32h735g_disco/stm32h735g_disco.yaml
st/stm32h745i_disco/stm32h745i_disco_stm32h745xx_m7.yaml
st/stm32h747i_disco/stm32h747i_disco_stm32h747xx_m7.yaml
st/stm32h750b_dk/stm32h750b_dk.yaml
st/stm32h757i_eval/stm32h757i_eval_stm32h757xx_m7.yaml
st/stm32h7b3i_dk/stm32h7b3i_dk.yaml
st/stm32h7s78_dk/stm32h7s78_dk.yaml
st/stm32n6570_dk/twister.yaml
Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
This adds support for BTP commands and events required for running
PAST tests.
struct btp_gap_ev_periodic_transfer_received_ev is also adjusted
to match BTP specification.
Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
