[top/fpga] De-duplicate pin and pad info for cw310 and cw340
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
The `pinmux`, `pinout`, and, pending #29546, `chiplevel` properties of the cw310 and cw340 targets of earlgrey are nearly identical. The only difference is the added `POR_BUTTON_N` pad for cw310.
We should somehow unify this configuration data in `top_earlgrey.hjson` and only mention the differences in the respective target(s).
Contributor guide
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 in top_earlgrey.hjson and compare the pinmux, pinout, and pending chiplevel properties for the cw310 and cw340 earlgrey targets. Consolidate the shared configuration while retaining the cw310-only POR_BUTTON_N pad; done means the targets no longer duplicate identical data and their differences remain explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100