Skip to content

[doc] Improve dev guide#554

Open
elliotb-lowrisc wants to merge 1 commit into
lowRISC:mainfrom
elliotb-lowrisc:doc
Open

[doc] Improve dev guide#554
elliotb-lowrisc wants to merge 1 commit into
lowRISC:mainfrom
elliotb-lowrisc:doc

Conversation

@elliotb-lowrisc
Copy link
Copy Markdown
Contributor

Several updates and improvements to the dev guide:

  • Update out-of-date commands.
  • Add commands for running SW on FPGA.
  • Add options to Verilator build command to improve build/sim runtime.
  • Document temperature sensor connections.
  • Add some useful alternative commands.
  • Clarify the use of the "_sram" SW binary suffix.
  • Other minor textural improvements.

@elliotb-lowrisc
Copy link
Copy Markdown
Contributor Author

I intend to make this PR non-draft when I have had a chance to try the new FPGA commands

@elliotb-lowrisc elliotb-lowrisc linked an issue May 14, 2026 that may be closed by this pull request
Several updates and improvements to the dev guide:
- Update out-of-date commands.
- Add commands for running SW on FPGA.
- Add options to Verilator build command to improve build/sim runtime.
- Document temperature sensor connections.
- Add some useful alternative commands.
- Clarify the use of the "_sram" SW binary suffix.
- Other minor textural improvements.
@elliotb-lowrisc elliotb-lowrisc marked this pull request as ready for review May 15, 2026 13:07
Comment thread doc/ref/dev_guide.md
cmake --build build/sw -j $(nproc)
```

Outputs with the suffix "_sram" exist only for UVM-based tests, as they lack a DRAM backdoor-load mechanism.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm concern that this will be left behind when the _sram binaries are dropped.
If you wan't to keep this, please add item to the issue to clean up the documentation.

Comment thread doc/ref/dev_guide.md
### Code Quality

For software written in C, `clang-format` and `clang-tidy` are used format and lint the code. Wrapper scripts to run these on all C files in the project are provided for convenience.
For software written in C, `clang-format` and `clang-tidy` are used format and lint the code.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For software written in C, `clang-format` and `clang-tidy` are used format and lint the code.
For software written in C, `clang-format` and `clang-tidy` are used to format and lint the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOC] Improve Developer Guide

2 participants