Home
last modified time | relevance | path

Searched +refs:test +refs:byte +refs:writes (Results 1 – 9 of 9) sorted by relevance

/Zephyr-latest/samples/drivers/spi_flash_at45/
DREADME.rst13 The sample writes a defined test region in the flash memory with bytes of
88 Reading the first byte of the test region ... OK
89 Preparing test content starting with 0x01.
90 Writing the first half of the test region... OK
91 Writing the second half of the test region... OK
92 Reading the whole test region... OK
/Zephyr-latest/doc/releases/
Drelease-notes-3.0.rst686 * Fixed incomplete :c:func:`zsock_sendmsg` writes handling.
858 * Drivers: clock_control: Added test suite for stm32 (u5, h7).
881 * :github:`42665` - tests: kernel.common.context: test failure on imxrt series platform
887 * :github:`42602` - I2C scan writes 0 bytes
896 * :github:`42499` - mec15xxevb_assy6853: boards.mec15xxevb_assy6853.i2c.i2c_pca95xx test failed.
907 * :github:`42385` - STM32: Entropy : health test config & magic never used
958 * :github:`42010` - intel_adsp_cavs18: Test cases failed on SMP related test cases (when CONFIG_MP_…
960 * :github:`41993` - Intel_adsp_cavs18: test cases can not get complete log
962 * :github:`41991` - Intel_adsp_cavs18: some test cases can not get any log
971 * :github:`41943` - Intel_adsp_cavs15: all the test cases run failed when running them by twister
[all …]
Drelease-notes-3.2.rst286 * :c:func:`semihost_exec` function is now aligned at 16-byte boundary.
1284 * :dtcompatible:`st,stm32-ospi-nor`: new ``four-byte-opcodes``,
1546 ``--test suite_name:*`` or ``--test suite_name::test_name`` command line arguments.
1649 :ref:`test-framework` for more details. This should be used for newly
1653 * Added test for the new shell API function: :c:func:`shell_ready`.
1703 - :github:`47014` - can: iso-tp: implementation test failed with twister on nucleo_g474re
1707 - :github:`47500` - twister: cmake: Failure of "--build-only -M" combined with "--test-only" for --…
1708 - :github:`47607` - Settings with FCB backend does not pass test on stm32h743
1713 - :github:`48018` - ztest: static threads are not re-launched for repeated test suite execution.
1722 - :github:`48394` - vsnprintfcb writes to ``*str`` if it is NULL
[all …]
Drelease-notes-3.3.rst143 * zTest now supports controlling test summary printouts via the
145 less verbose test output.
149 a single test for the class of devices and testing various boards using
645 * Made the fake CAN test driver generally available.
685 * Intel GPDMA linked list transfer descriptors appropriately aligned to 64 byte addresses
704 * DMA API start/stop are defined to be repeatable callable with test cases added.
778 * I2C Added support for dumping messages in the log for all transactions, reads and writes
878 * Added a new test that allows to verify regulator output voltage using the
880 * Added a new test that checks API behavior provided we have a well-behaved
1067 * Improved test coverage for IPv6 fragmentation.
[all …]
Drelease-notes-2.2.rst239 * Enhanced test coverage for ARM-specific kernel features
733 * :github:`23208` - Can not flash test images into up_squared board.
753 * :github:`23004` - Can't use west to flash test images into up_squared board.
775 * :github:`22888` - Can't flash test image into iotdk board.
776 * :github:`22885` - Sanitycheck timeout all test cases on mec15xxevb_assy6853 board.
790 * :github:`22730` - CONFIG_BT_SETTINGS writes bt/hash to storage twice
835 * :github:`22522` - GPIO test code tests/drivers/gpio/gpio_basic_api does not compile for microchip…
887 * :github:`22257` - test wdt_basic_api failed on nucleo_f746zg
991 * :github:`21450` - sample.net.cloud.google_iot_mqtt test is failing for frdm_k64f
1035 * :github:`21167` - libraries.libc.newlib test fails
[all …]
Drelease-notes-2.4.rst248 * Increased test coverage in QEMU for ARMv6-M architecture variant.
464 to be synthesized to test driver behavior. See
905 * :github:`28627` - tests: kernel: fatal: exception: stack_sentinel test is failing for nRF platfor…
935 * :github:`28394` - nanosleep test failed on ARC series targets
936 …` - drivers: sensor: lsm6dsl compilation issue when sensor defined in board (I2C) and in test (SPI)
959 * :github:`28295` - kernel.common: lpcxpresso55s16_ns test failure
994 * :github:`28193` - include/drivers/flash: API stands mistakenly unrestricted alignment of writes.
1012 * :github:`28156` - twr_kv58f220m: libraries.cmsis_dsp.transform.cf64 test fails
1045 * :github:`28049` - nucleo_wb55rg: test/spi/spi_loopback build failure
1046 * :github:`28045` - [mimxrt1050_evk] uart_fifo_fill only send 1 byte
[all …]
Drelease-notes-2.5.rst460 test. It's a driver again.
517 * Avoid wrapping each byte in muxing headers in PPP.
872 * flash_map: Added API to get the value of an erased byte in the flash_area,
956 * :github:`32221` - Sporadic kernel panics on stm32g4 flash erase/writes
1029 * :github:`31782` - adc: test and sample failed on STM32
1037 * :github:`31729` - test: build fatal related testcase failed on qemu_cortex_m0 and run failed on q…
1089 * :github:`31616` - test: ipc: Test from samples/subsys/ipc/rpmsg_service fails on nrf5340dk_nrf534…
1103 * :github:`31555` - tests:drivers_can_api: mimxrt1060 can api test meet assert failure
1162 …unsupported fixture without defined harness causes an infinite loop during on-target test execution
1247 * :github:`30573` - up_squared: slowdown on test execution and timing out on multiple tests
[all …]
/Zephyr-latest/cmake/modules/
Dextensions.cmake201 # writes "-Isome_dir;-Isome/other/dir" to x
292 # This function writes a dict to it's output parameter
350 # This test will match in case there are more generator expressions in the flag.
436 # provided base and writes it to the argument "lib_name"
1112 # so we cache the capability test results in USER_CACHE_DIR (This
1117 # an automated test.
1136 # toolchain test.
1160 LIMIT 1 # Read at most 1 byte ('0' or '1')
1169 # tested, so to test -Wno-<warning> flags we test -W<warning>
1211 # result, and the toolchain test.
[all …]
/Zephyr-latest/doc/hardware/porting/
Darch.rst344 check test suite, a system clock is needed as well. Since these two are usually
787 * :c:func:`arch_buffer_validate` to test whether the current thread has
941 * This writes the value of one hardware register received from GDB.
984 and read/write can be done byte-by-byte.