Changes between Version 2 and Version 3 of WARPLab/Debugging

Timestamp:

May 20, 2013, 3:48:19 PM (11 years ago)

Author:

murphpo

Comment:

--

WARPLab/Debugging

@@ -3 +3 @@
 = WARPLab 7: Debugging Errors =
 
-coming soon
+---
+{{{
+Error using wl_transport_eth_udp_pnet/send (line 228)
+maximum number of retransmissions met without reply from node
+
+Error in wl_node/sendCmd (line 677)
+            resp = obj.transport.send(cmd.serialize());
+
+Error in wl_node/procCmd (line 644)
+                    node.sendCmd(myCmd);
+
+Error in wl_node/wl_nodeCmd (line 310)
+                out(n) = currNode.procCmd(n, currNode, varargin{:});
+
+Error in wl_node/applyConfiguration (line 160)
+            obj.wl_nodeCmd('initialize');
+
+Error in wl_initNodes (line 106)
+        currNode.applyConfiguration(nodeIDs(n));
+}}}
+
+This error indicates that a WARP node didn't respond to repeated communication attempts from the {{{wl_initNodes}}} script.
+
+Things to check:
+ * Did all WARP nodes boot successfully? On each node a green LED will blink while waiting for the Ethernet link, then all LEDs will turn off and the hex display will show the node's IP address suffix.
+ * Did you specify an invalid number of nodes or invalid node IDs in the arguments to {{{wl_initNodes}}?
+ * Does each WARP node have a unique ID? In the reference design IDs are assigned by setting the user DIP switch on the WARP node.
+ * Are all WARP nodes connected to a 1Gb Ethernet switch?
+
+Debugging steps: To isolate which node is failing to communicate, you can use the optional {{{wl_initNodes}}} syntax to set node IDs explicitly:
+{{{
+wl_initNodes(1, 0); %initialize one node with ID 0
+wl_initNodes(1, 1); %initialize one node with ID 1
+wl_initNodes(1, 2); %initialize one node with ID 2
+%continue until a node fails to initialize
+}}}
+ ---
+