alter Alu1 test to work around fpga anomoly

[fleet.git] / ships / Debug.ship

diff --git a/ships/Debug.ship b/ships/Debug.ship
index 7978ba3..ba6bab1 100644 (file)
--- a/ships/Debug.ship
+++ b/ships/Debug.ship
@@ -6,15 +6,19 @@ data  in:   in
 == Constants ========================================================
 
 == TeX ==============================================================
-\begin{verbatim}
 
-TODO: have some way to log multiple separate streams; use sibling
-      ports to deliver an opcode
+This ship is used for debugging.  It has only one port, {\tt in}.
+Programmers should send debug report values to this port.  How such
+values are reported back to the programmer doing the debugging is left
+unspecified.
 
-TODO: have a way to programmatically read back the output of the debug
-      ship?
+\subsection*{To Do}
 
-\end{verbatim}
+Provide an {\tt inOp} port and use opcode ports \cite{am25} to
+effectively allow multiple independent ``debug streams''
+
+Provide a way to programmatically read back the output of the debug
+ship.
 
 == Fleeterpreter ====================================================
 public void service() {
@@ -27,9 +31,11 @@ public void service() {
 == FPGA ==============================================================
 `include "macros.v"
 
-module debug (clk, data_debug_data_r, data_debug_data_a, data_debug_data,
-                   data_debug_out_r, data_debug_out_a, data_debug_out );
+module debug (clk, rst,
+              data_debug_data_r, data_debug_data_a, data_debug_data,
+              data_debug_out_r, data_debug_out_a, data_debug_out );
   input clk;
+  input rst;
 
   input  data_debug_data_r;
   output data_debug_data_a;
@@ -45,5 +51,14 @@ module debug (clk, data_debug_data_r, data_debug_data_a, data_debug_data,
 
 endmodule
 
+== Test ================================================================
+#expect 25
+
+#ship debug : Debug
+
+debug.in:
+  literal 25;
+  deliver;
+
 == Contributors =========================================================
 Adam Megacz <megacz@cs.berkeley.edu>