You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably already known, but filing an issue nevertheless because it impacts what tests can be run on Verilator. For example, pwrmgr relies on interactions with AST to get into low power mode. Hopefully we can use this to document a path forward.
The text was updated successfully, but these errors were encountered:
- For bootrom, use the `.scr.40.vmem` image.
- Update / add other test entries
- Increase wakeup threshold for pwrmgr test
- Add pwrmgr test to DVSim as well as pytest versions of running
Verilator sims.
- It does not work on Verilator yet due to lowRISC#6656, so its commented
out.
Signed-off-by: Srikrishna Iyer <[email protected]>
- For bootrom, use the `.scr.40.vmem` image.
- Update / add other test entries
- Increase wakeup threshold for pwrmgr test
- Add pwrmgr test to DVSim as well as pytest versions of running
Verilator sims.
- It does not work on Verilator yet due to #6656, so its commented
out.
Signed-off-by: Srikrishna Iyer <[email protected]>
this one should be working for now.
I added some minor fixes in the tb such that pwrmgr can go into sleep and power up (needed for another test on verilator).
The underlying issue still isn't solved, but pwrmgr_smoke can at least run.
since ast is now already part of chip_earlgrey_verilator, i think this can be closed down.
There are separate issues tracking the convergence of the chip level template to support asic / fpga / verilator.
This is probably already known, but filing an issue nevertheless because it impacts what tests can be run on Verilator. For example, pwrmgr relies on interactions with AST to get into low power mode. Hopefully we can use this to document a path forward.
The text was updated successfully, but these errors were encountered: