Verilog good first issues

20 open Verilog issues currently match the default 10+ star filter. Scored difficulty: 5,946 at 1/5, 8,786 at 2/5, 12,699 at 3/5, 12,118 at 4/5, 857 at 5/5. This hub uses the same feed as the homepage, limited to repositories whose GitHub language is Verilog.

All languages · Browse projects · How to find good first issues

Active projects

Unique repos with open help-wanted issues updated in the last 30 days

Showing 20 of ~20 matching filters (Verilog · 10+ stars)

List

Toki / Juju densetsu sound problem.

AI summary

The user is reporting a high-pitched crackling sound issue specifically with the main theme music in the Toki core, while other audio tracks appear unaffected. A similar crackle is also present when flying enemies are destroyed, which is not present on the original hardware. The issue is labeled as 'help wanted'.

help wanted
314
Difficulty
3/5

gpl: report internal metrics

AI summary

This issue proposes to expose several key internal metrics from the GPL (Global Placement) tool to a metrics dashboard. Currently, these metrics are only available in log files. The implementation involves adding calls to `logger_->metric()` for each relevant metric, which is described as straightforward.

good first issuegpl
2.5K
Difficulty
2/5

cts: isolate tests

AI summary

This issue aims to improve the isolation of tests within the CTS (Common Test Suite) by removing dependencies on external Detailed Placement (DPL) and Global Placement (GPL) commands. The goal is to ensure that CTS tests can run independently without relying on the output of these other tools, by generating necessary DEF files internally.

good first issue
2.5K
Difficulty
3/5

test: isolate tests at multiple tools

AI summary

This issue proposes to improve the isolation of regression tests by preventing them from unnecessarily invoking upstream tools. The suggested solution is to generate intermediate ODB or DEF files that can be directly used as input for target tool regression tests, thereby reducing maintenance overhead and test fragility.

good first issue
2.5K
Difficulty
3/5

ram: bloat occupied layers in test lefs

AI summary

The current RAM tests generate overly detailed LEF files with specific obstructions, which is inefficient. The issue proposes using a flag (`-bloat_occupied_layers`) to create simpler LEF files with whole-layer obstructions, reducing complexity and improving test efficiency.

good first issueram
2.5K
Difficulty
2/5

Also browsing: Python , TypeScript , JavaScript