-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hw: Add native bootrom #168
Open
fischeti
wants to merge
53
commits into
main
Choose a base branch
from
bootrom
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fischeti
changed the title
hw: Add native bootrom to the cluster
hw: Add native bootrom
Jul 22, 2024
fischeti
requested review from
paulsc96,
lucabertaccini and
colluca
as code owners
July 29, 2024 07:23
fischeti
force-pushed
the
bootrom
branch
2 times, most recently
from
August 5, 2024 07:36
7026e09
to
85232d4
Compare
Setup toolchain for generating bootrom. Created scratch registers. Begun setup for instantiating bootrom.
Bootrom fully instantiated. Fetches Bootrom instructions in simulation.
Setup toolchain for generating bootrom. Created scratch registers. Begun setup for instantiating bootrom.
Bootrom fully instantiated. Fetches Bootrom instructions in simulation.
…d set Performance Counters to track Retired Instructions during Boot Procedure.
will be done in another PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds native bootrom to the cluster instead of fetching from externally. Also adds additional scratch registers to the peripherals which can be used to write the entry point of the binary.
The current bootrom is very simple currently, and just fetches from the start of the
DRAM
region:The desired bootrom would look more like this:
where the cores are parked, and after getting an interrupt they start fetching from one of the scratch register (which is written by a host core e.g.).
This was also my first approach, but getting this to run in the testbench was not trivial to do (at that time). It requires an external interrupt and writing the entrypoint to one of the configuration registers, which is possible with an AXI driver connected to the narrow AXI interface. However, verilator4 does not support timing constructs, so AXI drivers cannot be used at all, which is why I reverted back to a very simple bootrom.
Now, we upgraded to verilator 5, which would theoretically allow such a thing. The question now is if this is needed, or if the intended use case is that the user will anyway write his custom bootrom that will overwrite the default one. Afaik, this is also the approach that we did for previous tapeouts (i.e. Occamy).
TODO
rtl
target and prerequisites