From: Tim Newsome <tim@sifive.com>
Date: Tue, 14 Jun 2016 00:56:53 +0000 (-0700)
Subject: Add a few tips.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=9ecc5021698fcf7632e4364cf97a7c20e606ac4f;p=riscv-tests.git

Add a few tips.
---

diff --git a/debug/README.md b/debug/README.md
index 2be795b..3fa43c7 100644
--- a/debug/README.md
+++ b/debug/README.md
@@ -1,3 +1,15 @@
 Debugging requires many of a system components to all work together.  The goal
 is to collect some tests that test gdb with spike, and gdb talking to real
 hardware through openocd.
+
+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
+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.
+
+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.)