-
Notifications
You must be signed in to change notification settings - Fork 938
Open
Labels
Component:ChipLevelTestUsed to filter the chip-level test backlogUsed to filter the chip-level test backlog
Description
Test point name
//sw/device/tests/uart_baud_rate_test
Host side component
Rust
OpenTitanTool infrastructure implemented
Yes
Silicon Validation (SiVal)
Yes
Emulation Targets
- None
- CW310
- Hyperdebug + CW310
Contact person
rprakas-gsc
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.
- Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
- Device-side (C) component developed
- Bazel build rules developed
- Host-side component developed
- HJSON test plan updated with test name (so it shows up in the dashboard)
- Test added to dvsim nightly regression (and passing at time of checking)
- [x ] For SiVal test cases, test is running relevant FPGA or silicon regression
The following UART tests are failing - as soon as I reconfigure the pinmuxchannelDUT from Iob4/Iob5 pins to Ioa0/Ioa1 pins
[kUartPinmuxChannelDut] = { .mio_out = kTopEarlgreyPinmuxMioOutIob5, .insel = kTopEarlgreyPinmuxInselIob4,
//sw/device/tests/uart_baud_rate_test_silicon_owner_gb_rom_ext
//sw/device/tests/uart_loopback_test_silicon_owner_gb_rom_ext
The test failure is attributed to the timeout due to the host not receiving any data from DUT.
Metadata
Metadata
Assignees
Labels
Component:ChipLevelTestUsed to filter the chip-level test backlogUsed to filter the chip-level test backlog