google / google/CFU-Playground
Add some linting / sanity checks / physical design summary output
Open
- Dominant language
- Verilog
- Stars
- 565
- Forks
- 160
- PR merge metrics
- No merged PRs in 30d
Description
We had a situation where a small mistake caused the creation of a 2048b counter. This consumed 2000 extra LUTs and had a 85ns path, but it wasn't flagged during the build and the user (me) didn't notice anything amiss. But on the board, there were nondeterministic failures due to the long path, and only after some investigation did we find the issue. The following additions would have helped us find the issue sooner:
* Visible printout of the LUT count and critical path delay after building the bistream
* Maybe some linting in nMigen to flag Signals wider than say 128b
* Others?
Contributor guide
Assessment
This issue has not been assessed yet.