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
|`--no-color`| Remove ANSI colors in debugging output |
@@ -208,7 +209,7 @@ All unit tests from [riscv-samples](https://gitlab.univ-lille.fr/michael.hauspie
208
209
- The emulator relies on ELF symbols for heap management and call tracing: do not strip ELF binaries.
209
210
- When a trap condition is triggered, if `mtvec` is set to zero, the emulator's trap handler is invoked and supports Newlib's system calls. If you install your own trap handler (non-zero `mtvec`), you are responsible for all trap behavior including system calls.
210
211
-`EBREAK` traps with `a7 >= 0xFFFF0000` are used as a debug bridge, regardless of `mtvec`. See `riscv-py.h` for simple logging macros using this facility. These logging macros do not depend on Newlib.
211
-
- The emulated architecure supports unaligned memory accesses and will not trap when they occur.
212
+
- The emulated architecture supports unaligned memory accesses and will not trap when they occur.
212
213
- The 64-bit registers `mtime` and `mtimecmp` are accessible via CSR instructions (rather than being memory-mapped) at addresses `0x7C0` (low 32 bits of `mtime`), `0x7C1` (high 32 bits of `mtime`), `0x7C2` (low 32 bits of `mtimecmp`), and `0x7C3` (high 32 bits of `mtimecmp`). Writes to `mtime` and `mtimecmp` are atomic for the whole 64-bit register and occur when the second word of the register is written.
0 commit comments