On Sat, Jun 7, 2008 at 2:45 AM, Nicola Wegner <[EMAIL PROTECTED]> wrote: > 2008/6/6 Omprakash Gnawali <[EMAIL PROTECTED]>: >> On Fri, Jun 6, 2008 at 3:35 AM, Nicola Wegner >> <[EMAIL PROTECTED]> wrote: >>> 2008/6/6 Paul Stickney <[EMAIL PROTECTED]>: >>> [...] >>>> >>>> I don't have in-depth enough knowledge about the Collection >>>> implementations, but I suspect that >>>> (in priority of where I'd start looking) >>>> 1) No route is being found and it's waiting and waiting and ... >>> >>> This really seems to be the problem. I have put some debug messages in >>> CtpForwardingEngineP.nc to check it. It retries to send every 10 >> >> You can also use the built-in debugging system that should report a >> lack of path when you try to send a packet. > > What do you mean? The dbg(..)-Statements or the messages that are sent > to the UART? I am not working with TOSSIM so, as far as I know, there > is no possibility to see the dbg(...) output. I tried to use MsgReader > to read CollectionDebugMsg but I did not get any output. Although I > did not have a very deep look at this. Perhaps I have to activate > debug messages first?
There is a default implementation of CollectionDebug in the forwarding engine which is what you use if you don't wire it to a debugger. You can look at apps/tests/TestNetwork to see how to wire CollectionDebug to a proper debugger. - om_p _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
