-
Notifications
You must be signed in to change notification settings - Fork 343
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
Why riscv-011_reg.c
don't have examine_vlenb
and examine_mtopi
API?
#1237
Comments
@Alan-19950616 why do you ask? Discovery of these vector registers was never supported for 0.11 targets. Recent changes just made this explicit to avoid crashes on non RISCV-V compliant targets. Do you have a 0.11-compliant HW that supports RVV/mtopi/mtopei? If this is the case - then file a bug, please. |
@Alan-19950616, AFAIU this is the issue fixed in #1207, please, try using a more recent OpenOCD version. |
@en-sc , @Alan-19950616 the issue fixed by #1207 addresses this assertion failure:
However, vlenb/mtopei/mtopi discovery mechanism is still not available for riscv-0.11 targets. Just FYI |
Yes, my riscv-0.11 target also doesn't support the vlenb/mtopei/mtopi registers, using the latest openocd version solves the problem of the connection being ASSERTED! |
https://github.com/riscv-collab/riscv-openocd/blob/riscv/src/target/riscv/riscv_reg.c#L368-L379
examine_vlenb
https://github.com/riscv-collab/riscv-openocd/blob/riscv/src/target/riscv/riscv-013_reg.c#L126-L163
examine_mtopi
https://github.com/riscv-collab/riscv-openocd/blob/riscv/src/target/riscv/riscv-013_reg.c#L267-L290
The text was updated successfully, but these errors were encountered: