Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests/drivers/uart/uart_async_api fails on qemu_cortex_m0 #21877

Closed
andrewboie opened this issue Jan 14, 2020 · 5 comments
Closed

tests/drivers/uart/uart_async_api fails on qemu_cortex_m0 #21877

andrewboie opened this issue Jan 14, 2020 · 5 comments
Assignees
Labels
area: ARM ARM (32-bit) Architecture area: QEMU QEMU Emulation area: Tests Issues related to a particular existing or missing test

Comments

@andrewboie
Copy link
Contributor

To exit from QEMU enter: 'CTRL+a, x'
[QEMU] CPU: cortex-m0
*** Booting Zephyr OS build zephyr-v2.1.0-948-gebaed210c786  ***
Running test suite uart_async_test
===================================================================
starting test - test_single_read
test
    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:59: test_single_read: (k_sem_take(&rx_rdy, K_MSEC(100)) not equal to 0)
RX_RDY timeout
FAIL - test_single_read
===================================================================
starting test - test_chained_read
Message 0
    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:137: test_chained_read: (k_sem_take(&rx_rdy, K_MSEC(1000)) not equal to 0)
RX_RDY timeout
FAIL - test_chained_read
===================================================================
starting test - test_double_buffer

    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:194: test_double_buffer: (uart_rx_enable(uart_dev, double_buffer[0], sizeof(double_buffer[0]), 50) not equal to 0)
Failed to enable receiving
FAIL - test_double_buffer
===================================================================
starting test - test_read_abort

    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:248: test_read_abort: (k_sem_take(&rx_rdy, K_MSEC(100)) not equal to 0)
RX_RDY timeout
FAIL - test_read_abort
===================================================================
starting test - test_chained_write
Message 1Message 2
    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:379: test_chained_write: (k_sem_take(&tx_done, K_MSEC(100)) not equal to 0)
TX_DONE timeout
FAIL - test_chained_write
===================================================================
starting test - test_long_buffers

    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:453: test_long_buffers: (k_sem_take(&rx_rdy, K_MSEC(200)) not equal to 0)
RX_RDY timeout
FAIL - test_long_buffers
===================================================================
starting test - test_write_abort

    Assertion failed at ZEPHYR_BASE/tests/drivers/uart/uart_async_api/src/test_uart_async.c:309: test_write_abort: (k_sem_take(&rx_rdy, K_MSEC(100)) not equal to 0)
RX_RDY timeout
FAIL - test_write_abort
===================================================================
Test suite uart_async_test failed.
===================================================================
PROJECT EXECUTION FAILED
@andrewboie andrewboie added the bug The issue is a bug, or the PR is fixing a bug label Jan 14, 2020
@andrewboie andrewboie reopened this Jan 14, 2020
@andrewboie
Copy link
Contributor Author

For some baffling reason, this doesn't fail when sanitycheck runs it.

@andrewboie andrewboie added question and removed bug The issue is a bug, or the PR is fixing a bug labels Jan 14, 2020
@carlescufi
Copy link
Member

@Mierunski any input on this issue?

@Mierunski
Copy link
Collaborator

This test needs physical connection between RX and TX on second UART not used for console to pass

@stephanosio
Copy link
Member

This is where #21073 could potentially come in handy, given that we only have one UART on nRF51822; we could redirect console to semihosting and UART chardev to loopback.

@carlescufi carlescufi added area: ARM ARM (32-bit) Architecture area: QEMU QEMU Emulation area: Tests Issues related to a particular existing or missing test labels Apr 30, 2020
@carlescufi
Copy link
Member

Closing this since it needs a second UART

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ARM ARM (32-bit) Architecture area: QEMU QEMU Emulation area: Tests Issues related to a particular existing or missing test
Projects
None yet
Development

No branches or pull requests

5 participants