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

Incorrect documentation of mtvec CSR in user manual #1060

Closed
1 task done
spidugu444 opened this issue Feb 14, 2023 · 2 comments
Closed
1 task done

Incorrect documentation of mtvec CSR in user manual #1060

spidugu444 opened this issue Feb 14, 2023 · 2 comments
Assignees
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Status:New Newly created issue, nobody has looked at it yet. Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system

Comments

@spidugu444
Copy link
Contributor

spidugu444 commented Feb 14, 2023

Is there an existing CVA6 bug for this?

  • I have searched the existing bug issues

Bug Description

This issue points out mtvec documentation.
In CVA6 CSR documentation, Mode field access for mtvec is mentioned as RW as shown below.

Bits Name Display Name Access Type Reset
[31:2] BASE   RW 0b0
[1:0] MODE   RW 0b0
The access type for the Mode field should be as mentioned below.

As per the CVA6 for mtvec CSR mode field we have two implementation options i.e Direct Mode(00) and vector Mode (01).so the mode[1] bit is fixed to 0 making this bit to RO.

Bits Mode Description
1 RO MODE[1]: always 0
0 RW MODE[0]: 0 = direct mode, 1 = vectored mode.
@spidugu444 spidugu444 added the Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system label Feb 14, 2023
@JeanRochCoulon
Copy link
Contributor

JeanRochCoulon commented Feb 14, 2023

Thank you @spidugu444 for this GitHub issue.
As it is connected with the previous discussion involving @ASintzoff and @MikeOpenHWGroup about #1049, I prefer to have it assigned to André

@MikeOpenHWGroup
Copy link
Member

Hi @JeanRochCoulon. It is good that you have an opinion about who to assign this to. In such cases, please feel free to change the Assignee.

Hi @spidugu444. Please ensure that Component and Status flags are added to each Issue.

@MikeOpenHWGroup MikeOpenHWGroup added Component:Doc For issues in the Documentation (e.g. for README.md files) Status:New Newly created issue, nobody has looked at it yet. labels Feb 16, 2023
frikhaAziz pushed a commit to ThalesSiliconSecurity/cva6 that referenced this issue Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Status:New Newly created issue, nobody has looked at it yet. Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system
Projects
None yet
Development

No branches or pull requests

4 participants