-
Notifications
You must be signed in to change notification settings - Fork 887
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
Add DCSR.MPRVEN support #1882
base: master
Are you sure you want to change the base?
Add DCSR.MPRVEN support #1882
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,7 +23,12 @@ _entry: | |
// This fence is required because the execution may have written something | ||
// into the Abstract Data or Program Buffer registers. | ||
fence | ||
csrw CSR_DSCRATCH0, s0 // Save s0 to allow signaling MHARTID | ||
csrw CSR_DSCRATCH0, s0 // Save s0 to allow signaling MHARTID | ||
|
||
// We need to disable privilege modification to avoid | ||
// address translation in debug_rom memory accesses | ||
csrw CSR_DSCRATCH1, s1 // Save s1 | ||
csrrci s1, CSR_DCSR, DCSR_MPRVEN // Save DCSR and clear MPRVEN | ||
|
||
// We continue to let the hart know that we are halted in order that | ||
// a DM which was reset is still made aware that a hart is halted. | ||
|
@@ -47,13 +52,16 @@ _exception: | |
// We need this in case the user tried an abstract write to a | ||
// non-existent CSR. | ||
csrr s0, CSR_DSCRATCH0 | ||
csrr s1, CSR_DSCRATCH1 // Restore s1 | ||
sw zero, DEBUG_ROM_EXCEPTION(zero) // Let debug module know you got an exception. | ||
ebreak | ||
|
||
going: | ||
csrr s0, CSR_MHARTID | ||
sw s0, DEBUG_ROM_GOING(zero) // When debug module sees this write, the GO flag is reset. | ||
csrr s0, CSR_DSCRATCH0 // Restore s0 here | ||
csrw CSR_DCSR, s1 // Restore DSCR | ||
csrr s1, CSR_DSCRATCH1 // Restore s1 | ||
fence | ||
fence.i | ||
jalr zero, zero, %lo(whereto) // Debug module will put different instructions and data in the RAM, | ||
|
@@ -64,6 +72,8 @@ _resume: | |
csrr s0, CSR_MHARTID | ||
sw s0, DEBUG_ROM_RESUMING(zero) // When Debug Module sees this write, the RESUME flag is reset. | ||
csrr s0, CSR_DSCRATCH0 // Restore s0 | ||
csrw CSR_DCSR, s1 // Restore DSCR | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How can the debugger set bits in dcsr if here you overwrite it with a previously saved value? The debugger has to be able to set bits like ebreakm and step. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thank you for your feedback! I understand your concern about the debugger's ability to set bits like ebreakm and step in the DCSR register. As I understand, the debugger modifies the DCSR only in whereto section (section for progbuf and abstract commands code). And we clear MPRVEN only inside of debug ROM which is not intersect with whereto. This means that restoring the entire DCSR register (including MPRVEN) should not interfere with the debugger's ability to set other bits like ebreakm and step during normal operation. |
||
csrr s1, CSR_DSCRATCH1 // Restore s1 | ||
dret | ||
|
||
// END OF ACTUAL "ROM" CONTENTS. BELOW IS JUST FOR LINKER SCRIPT. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,15 @@ | ||
static const unsigned char debug_rom_raw[] = { | ||
0x6f, 0x00, 0xc0, 0x00, 0x6f, 0x00, 0x00, 0x06, 0x6f, 0x00, 0x80, 0x03, | ||
0x0f, 0x00, 0xf0, 0x0f, 0x73, 0x10, 0x24, 0x7b, 0x73, 0x24, 0x40, 0xf1, | ||
0x23, 0x20, 0x80, 0x10, 0x03, 0x44, 0x04, 0x40, 0x13, 0x74, 0x14, 0x00, | ||
0x63, 0x14, 0x04, 0x02, 0x73, 0x24, 0x40, 0xf1, 0x03, 0x44, 0x04, 0x40, | ||
0x13, 0x74, 0x24, 0x00, 0x63, 0x18, 0x04, 0x02, 0x73, 0x00, 0x50, 0x10, | ||
0x6f, 0xf0, 0x9f, 0xfd, 0x73, 0x24, 0x20, 0x7b, 0x23, 0x26, 0x00, 0x10, | ||
0x6f, 0x00, 0xc0, 0x00, 0x6f, 0x00, 0x40, 0x07, 0x6f, 0x00, 0x00, 0x04, | ||
0x0f, 0x00, 0xf0, 0x0f, 0x73, 0x10, 0x24, 0x7b, 0x73, 0x90, 0x34, 0x7b, | ||
0xf3, 0x74, 0x08, 0x7b, 0x73, 0x24, 0x40, 0xf1, 0x23, 0x20, 0x80, 0x10, | ||
0x03, 0x44, 0x04, 0x40, 0x13, 0x74, 0x14, 0x00, 0x63, 0x16, 0x04, 0x02, | ||
0x73, 0x24, 0x40, 0xf1, 0x03, 0x44, 0x04, 0x40, 0x13, 0x74, 0x24, 0x00, | ||
0x63, 0x1e, 0x04, 0x02, 0x73, 0x00, 0x50, 0x10, 0x6f, 0xf0, 0x9f, 0xfd, | ||
0x73, 0x24, 0x20, 0x7b, 0xf3, 0x24, 0x30, 0x7b, 0x23, 0x26, 0x00, 0x10, | ||
0x73, 0x00, 0x10, 0x00, 0x73, 0x24, 0x40, 0xf1, 0x23, 0x22, 0x80, 0x10, | ||
0x73, 0x24, 0x20, 0x7b, 0x0f, 0x00, 0xf0, 0x0f, 0x0f, 0x10, 0x00, 0x00, | ||
0x67, 0x00, 0x00, 0x30, 0x73, 0x24, 0x40, 0xf1, 0x23, 0x24, 0x80, 0x10, | ||
0x73, 0x24, 0x20, 0x7b, 0x73, 0x00, 0x20, 0x7b | ||
0x73, 0x24, 0x20, 0x7b, 0x73, 0x90, 0x04, 0x7b, 0xf3, 0x24, 0x30, 0x7b, | ||
0x0f, 0x00, 0xf0, 0x0f, 0x0f, 0x10, 0x00, 0x00, 0x67, 0x00, 0x00, 0x30, | ||
0x73, 0x24, 0x40, 0xf1, 0x23, 0x24, 0x80, 0x10, 0x73, 0x24, 0x20, 0x7b, | ||
0x73, 0x90, 0x04, 0x7b, 0xf3, 0x24, 0x30, 0x7b, 0x73, 0x00, 0x20, 0x7b | ||
}; | ||
static const unsigned int debug_rom_raw_len = 116; | ||
static const unsigned int debug_rom_raw_len = 144; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This clobbers s1. Now the debugger can't access it anymore.
Also you're going through a bunch of effort here to clear dcsr.mprven while in debug mode, but if you're clearing it then when does the bit actually have an effect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding the use of register s1:
The register s1 is used within the debug ROM to save and restore the DCSR register, specifically to manage the MPRVEN bit. After the debug ROM execution, s1 is restored to its original value, ensuring that the debugger can access it as before. This approach maintains the integrity of s1 for debugger operations.
Clarification on MPRVEN bit management:
The MPRVEN bit is cleared within the debug ROM to prevent unwanted virtual address translations during ROM execution. However, it is crucial that this bit is set when the debugger initiates memory accesses. The debug ROM's role is to ensure a controlled environment, and the MPRVEN bit will have its intended effect when the debugger performs memory operations post-ROM execution.