-
Notifications
You must be signed in to change notification settings - Fork 807
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
[DRAFT] Darjeeling DV bring up #26088
Draft
alees24
wants to merge
8
commits into
lowRISC:master
Choose a base branch
from
alees24:darjeeling-dv
base: master
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.
Draft
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
Separate flash support into another package so that designs such as Darjeeling can employ mem_bkdr_util without depending upon the flash controller/package. Signed-off-by: Adrian Lees <[email protected]>
Signed-off-by: Adrian Lees <[email protected]>
Sensor control is not present in Darjeeling. Modifications to support RAM DFT. Signed-off-by: Adrian Lees <[email protected]>
Signed-off-by: Adrian Lees <[email protected]>
Signed-off-by: Adrian Lees <[email protected]>
Changes to support modified OTP controller and memory backdoor utility (no flash controller present in Darjeeling). AST/Calibration signaling changes and wire up soc_dbg_ctrl. Signed-off-by: Adrian Lees <[email protected]>
The build flow presently creates ROM images only using Earl Grey scrambling keys (read from top_earlgrey.gen.hjson), so in order to unscramble the ROM images successfully and execute software, temporarily modify the templated top_level for Darjeeling only to use fixed keys. Note that this only works for the standard build seed that we employ, and that this is a temporary measure to avoid conflicting with/replicating the work on multitop support in sw/building. Signed-off-by: Adrian Lees <[email protected]>
Temporary change to the test_rom to report status codes in DV simulation and yield a passing test; demonstration that very simple software is running. Signed-off-by: Adrian Lees <[email protected]>
Thanks for doing this and sharing the PR @alees24 ! |
For reference, the multitop work is now partially merged in master, the last remaining part is in #26038 |
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.
This DRAFT PR - DO NOT MERGE - ports the DV environment from integrated_dev onto master and makes sufficient changes to permit the CPU to start up and execute code from the first stage boot ROM.
There are a number of tidy ups still required:
A temporary modification in the final commit to the test_rom startup code is sufficient to permit the following test to complete successfully on Darjeeling, demonstrating that the
rom_ctrl
s andsoc_dbg_ctrl
have granted permission for the Ibex core to proceed, and the CPU is receiving correctly-unscrambled, valid code. It simply writes the SwTestStatus<> values into the DV sim window, producing a test pass.Please also note that this PR depends upon and presently includes the changes in PR #26081 that permits Darjeeling in the absence of any flash memory/controller.
Aside from the final commit with its temporary modification of the test_rom boot code, the changes in this PR should have zero impact upon Earl Grey.
@Razer6 for awareness; no need to review presently. @pamaury in case this is helpful for the ongoing multi-top software work.