Closed pkunieck closed 1 year ago
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.
Can we have an update on the issue? These tests are still failing
Apologies for the delay. Could you provide some input on the test environment,
1) Which SOC are you using, MEC1501? 2) What is the FLASH chip used 3) GPIO pin used to connect FLASH with MEC15xx 4) Which debugger used, J-link?
Also share the hardware map file "/home/zephyr/mec1.file"
Added pinctrl property in overlay file to support spi quad mode.
Describe the bug Tests spi_octal and spi_quad from tests/boards/mec15xxevb_assy6853/qspi/ are failing, and this is output from console:
DEBUG - DEVICE: SUITE FAIL - 0.00% [spi_quad]: pass = 0, fail = 2, skip = 0, total = 2 duration = 0.043 seconds DEBUG - DEVICE: - FAIL - [spi_quad.test_spi_octal_read] duration = 0.021 seconds DEBUG - DEVICE: - FAIL - [spi_quad.test_spi_quad_read] duration = 0.022 seconds
Assertion failed at WEST_TOPDIR/zephyr/tests/boards/mec15xxevb_assy6853/qspi/src/main.c:656: spi_quad_test_spi_octal_read: (memcmp(buffer_tx, safbuf2, BUF_SIZE) == 0 is false) Buffer read data is different to write data FAIL - test_spi_octal_read in 0.021 seconds
Assertion failed at WEST_TOPDIR/zephyr/tests/boards/mec15xxevb_assy6853/qspi/src/main.c:590: spi_quad_test_spi_quad_read: (memcmp(buffer_tx_2, safbuf2, BUF_SIZE_2) == 0 is false) Buffer read data is different to write data FAIL - test_spi_quad_read in 0.022 seconds
Problem seems to be old and I can't find a commit that cause the issue because of other problems in the past(no console output and some others in older commits).
To Reproduce Run command on newest commit: twister --hardware-map /home/zephyr/mec1.file --device-testing -T tests/boards/mec15xxevb_assy6853/qspi/
Expected behavior Passing tests
Impact annoyance
Logs and console output See above.
Environment (please complete the following information):