UART DV - Top-level pin-loopback test via UART agent
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 38
- Forks
- 21
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 14
Description
Implement chip_uart_tx_rx (uart_tx_rx / uart_tx_rx_cheri, V1, placeholder registered).
SW transmits a byte sequence out uart_tx_o with no internal loopback. The UVM UART agent, connected to the chip UART pins, receives each byte on uart_tx_o and drives it back onto uart_rx_i, closing the loopback after the chip pins. SW reads each byte back and passes if it matches what was sent.
This is the true chip-level UART smoke, exercising the real uart_tx_o / uart_rx_i pin path, as opposed to chip_uart_smoke which uses the UART's internal system loopback and never leaves the chip. It requires the UART agent to actively drive uart_rx_i (reactive / echo mode).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the registered chip_uart_tx_rx placeholder and inspect the related uart_tx_rx and uart_tx_rx_cheri entry points. Read how the UVM UART agent connects to uart_tx_o and uart_rx_i, then run the chip-level UART test with reactive echo behavior. Done means the transmitted byte sequence returns through the external pin path and passes comparison.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100