[tests] uart_parity_break and uart_tx_rx_test require two UARTs
Open
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
Those tests were originally written for Earlgrey, which has 4 UARTs. Darjeeling only has a single UART, thus making them incompatible. Those tests use the second UART solely for logging.
@pamaury proposed to use the SPI console as an alternative logging facility.
via https://github.com/lowRISC/opentitan/pull/28316
Contributor guide
Research direction
Start with the uart_parity_break and uart_tx_rx_test tests and identify where their second UART is used for logging. Review the SPI console proposal, then adapt the tests so they can run on Darjeeling with its single UART while retaining their existing test behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100