projects
/
riscv-tests.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Add test of compare-sections command.
[riscv-tests.git]
/
debug
/
README.md
diff --git
a/debug/README.md
b/debug/README.md
index 829a285deb0ec7430164d4791423f559b95af046..56f69db07ec6a1cf6c009a97d1d1314b6b860834 100644
(file)
--- a/
debug/README.md
+++ b/
debug/README.md
@@
-12,23
+12,29
@@
Targets
64-bit Spike
------------
64-bit Spike
------------
-`./gdbserver.py --spike --cmd $RISCV/bin/spike`
+`./gdbserver.py --spike
64
--cmd $RISCV/bin/spike`
32-bit Spike
------------
`./gdbserver.py --spike32 --cmd $RISCV/bin/spike`
32-bit Spike
------------
`./gdbserver.py --spike32 --cmd $RISCV/bin/spike`
-32-bit SiFive Core on Microsemi FPGA board
-------------------------------------------
+32-bit SiFive Core on Supported FPGA Boards & Hardware
+-------------------------------------
+
+`./gdbserver.py --freedom-e300`
+
+32-bit rocket-chip core in Simulation
+-------------------------------------
+
+`./gdbserver.py --freedom-e300-sim`
-`./gdbserver.py --m2gl_m2s`
Debug Tips
==========
You can run just a single test by specifying <class>.<function> on the command
Debug Tips
==========
You can run just a single test by specifying <class>.<function> on the command
-line, eg: `./gdbserver.py --spike --cmd $RISCV/bin/spike
+line, eg: `./gdbserver.py --spike
64
--cmd $RISCV/bin/spike
SimpleRegisterTest.test_s0`.
Once that test has failed, you can look at gdb.log and (in this case) spike.log
to get an idea of what might have gone wrong.
SimpleRegisterTest.test_s0`.
Once that test has failed, you can look at gdb.log and (in this case) spike.log
to get an idea of what might have gone wrong.
@@
-36,3
+42,6
@@
to get an idea of what might have gone wrong.
You can see what spike is doing by add `-l` to the spike command, eg.:
`./gdbserver.py --spike32 --cmd "$RISCV/bin/spike -l"
DebugTest.test_breakpoint`. (Then look at spike.log.)
You can see what spike is doing by add `-l` to the spike command, eg.:
`./gdbserver.py --spike32 --cmd "$RISCV/bin/spike -l"
DebugTest.test_breakpoint`. (Then look at spike.log.)
+
+You can run gdb under valgrind by passing --gdb, eg.: `./gdbserver.py --spike64
+--gdb "valgrind riscv64-unknown-elf-gdb" -- -v DownloadTest`.