Skip to content
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

Update VeeR-EL2 codebase #93

Merged
merged 1 commit into from
May 30, 2023

Conversation

mkurc-ant
Copy link
Contributor

@mkurc-ant mkurc-ant changed the base branch from main to dev-goog May 26, 2023 13:02
@mkurc-ant
Copy link
Contributor Author

mkurc-ant commented May 26, 2023

@mcockrell-google @howardtr @bharatpillilli Please take a look.

@mkurc-ant mkurc-ant force-pushed the mkurc/update-veer branch from fe5bd87 to 786d57c Compare May 26, 2023 13:10
Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Definitely, I included those changes.

Signed-off-by: Maciej Kurc <[email protected]>
@mkurc-ant mkurc-ant force-pushed the mkurc/update-veer branch from 786d57c to 55ad1fd Compare May 29, 2023 10:35
@howardtr howardtr merged commit d107d4f into chipsalliance:dev-goog May 30, 2023
@@ -856,7 +857,7 @@ import el2_pkg::*;

// ----------------- DEBUG END -----------------------------

assign core_rst_l = rst_l & (dbg_core_rst_l | scan_mode);
assign core_rst_l = rst_l & (scan_rst_l | scan_mode);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just now noticing this.... shouldn't we be using ~scan_mode since this is an active-low reset? As-is, once we enter scan_mode, scan_rst_l has no effect on core_rst_l.

Copy link
Collaborator

Choose a reason for hiding this comment

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

you are right @calebofearth - @Nitsirks to also confirm this. We should file a bug and fix this - and understand what test/coverage shld have covered this

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.

4 participants