You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm evaluating whether I should use this library for a project but I'm not too familiar with Risc-V. I saw in the source that there is a memory address that looks like an interrupt vector for the cpu. const CSR_MIP_ADDRESS: u16 = 0x344;
Would I set the correct flag here for timer, hardware and software interrupts before calling the tick method on the cpu if I only want the cpu running in machine and debug mode?
Also is the machine interrupt vector table for calling my service routine hardcoded at const CSR_MTVEC_ADDRESS: u16 = 0x305;?
The text was updated successfully, but these errors were encountered:
I'm evaluating whether I should use this library for a project but I'm not too familiar with Risc-V. I saw in the source that there is a memory address that looks like an interrupt vector for the cpu.
const CSR_MIP_ADDRESS: u16 = 0x344;
Would I set the correct flag here for timer, hardware and software interrupts before calling the tick method on the cpu if I only want the cpu running in machine and debug mode?
Also is the machine interrupt vector table for calling my service routine hardcoded at
const CSR_MTVEC_ADDRESS: u16 = 0x305;
?The text was updated successfully, but these errors were encountered: