Are you returning a valid message pointer in the Receive function or does the message pointer get corrupted? Using JTAG or investing the pointer status could help diagnose your problem.
-Joe ps: You are welcome to write the SP glue components to run on Mica2 or MicaZ. We would certainly welcome the contribution. On 6/21/06, Ted Herman <[EMAIL PROTECTED]> wrote:
Dear Radio Stack Experts (using moteiv distro, GenericComm interface): I've got a program that enters a curious behavior. Initially, for a few minutes, it sends and receives messages. Sending is driven by Timer events. Then it stops receiving messages, though it continues to send messages (the sending is done out of a posted task). I watch the messages via sf/TOSBase. Why do I think it stops receiving messages? The first thing in the ReceiveMsg event is a call to Leds.greenToggle(). During the first few minutes, this blinks as one would expect, but then stops blinking (other behavior such as the sent message contents confirms the hypothesis that the mote is not receiving, though messages are in the air to be received). Because messages continue to be sent, I reckon the task queue can't be such that Led blinking would be inhibited (I welcome being corrected on this point, since I'm a T2 newbie). In fact, I added a Leds.redToggle() to the sending task, and I do see the red blink once a minute, as expected, even as the receiving is deaf. What would be the efficient way to diagnose this kind of situation? Thanks, Ted. ps. If the answer is "use SP instead" then please consider that I need to support Mica2 and MicaZ and I'd like to keep a common codebase. _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
