New community extension: systemrdl-pro — LSP + interactive memory-map viewer for SystemRDL 2.0

[seimei-d]

Hi SystemRDL maintainers and community,

I wanted to share a project I've been building on top of systemrdl-compiler: systemrdl-pro - a VS Code extension paired with a standalone LSP server and a memory-map viewer for SystemRDL 2.0.

What it gives you in the editor:

• Diagnostics, hover, go-to-definition, document symbols, and references - all powered by systemrdl-compiler under the
  hood, so behavior matches what peakrdl users already expect.
• CodeLens and inlay hints for elaborated address/offset/width values, kept in sync with edits.
• An interactive memory-map viewer (tree + detail pane) for elaborated addrmap roots, including multi-root workspaces.
• Editor-agnostic by design - the LSP and viewer aren't VS Code–specific, so other editors can plug in later.

It's intentionally a peaceful coexistence with the existing SystemRDL/vscode-systemrdl extension: different language id (systemrdl-pro), different feature scope, no overlap on syntax highlighting.

Links:

• Repo: https://github.com/seimei-d/systemrdl-pro
• Open VSX: https://open-vsx.org/extension/seimei-d/systemrdl-pro

If this looks useful to the community, it'd be great to see it linked somewhere on the SystemRDL side — org profile, systemrdl-compiler README, or the PeakRDL docs tools page. Happy to send a PR with the entry wherever fits best.

Feedback, issues, and PRs very welcome.

Thanks for systemrdl-compiler = none of this would exist without it.

[amykyta3]

Wow! This is incredibly cool!!

Please feel free to open a PR to edit this page: https://github.com/SystemRDL/PeakRDL/blob/main/docs/community.rst
It is probably worth adding a new section to organize this better anyways. Eventually this community page will probably get absorbed into a proper static site I plan to build rather than be part of the PeakRDL docs.

[seimei-d]

Thanks Alex! PR up: SystemRDL/PeakRDL#81

Two small framing questions in the PR description (column header and intro paragraph wording) - take whichever direction you prefer in review.

[amykyta3]

Oops noticed your questions just after I merged. Not attached to any particular phrasing so feel free to adjust. Otherwise I'll clean it up later - I'm planning a larger reorg where I build up a proper landing site at peakrdl.org (similar to what cocotb.org has), which would host things like the community page, language errata, and other things that are less tightly bound to the tools themselves.