Sorry, I'm clueless...
I don't use T2 or all the fancy resource grant stuff you have.
There are/used-to-be simple demo apps like Blink2Radio that
sent simple messages. I would go back to one of those and see
if it works, then build on it.
MS
David Lee wrote:
So, I've broken a test bit out that
Hey everyone -
I'm working on some radio code for the telosB motes. Specifically, my code
calls AMSend.send(), and via the printf library, I've proved that it returns
SUCCESS.
Unfortunately, the event for sendDone never gets called.
I've heard that this can be caused due to ack issues, so for
One should get a sendDone() with a failed ACK, although
you probably need to look at the message.ack field rather
then the error argument to figure it out.
If you are not getting the sendDone() call ever-at-all,
I would suspect that you have something hogging the processor
-- like that possibly
That's an excellent idea I never thought to look for.
However, I know it's not that specific infinite loop, since the printf()
usually prints the same thing (except for the occasional bad packet?), and
that's:
Thread[Thread-1,5,main]serial@/dev/mote_ultrasound:115200: resynchronising
Attempting
I don't know of any telos profiling tools. It does have
pads for a JTAG connector which you could use to trace
code, but I've never used it. Toggling LEDs is the best
debugging tool available, since it's easy (if you keep
the on/off patterns logical somehow) and doesn't interfere
with timing -- of
So, I've broken a test bit out that just handles the sending of a single
byte.
I've stuck more printfs in there to check for loops (not enough leds to use
those)
I'm not seeing any loops in my code's output. For references, here's the
output:
Sorry for the double-email, but I may have found some interesting
information.
I tried using MSPSim, which I know isn't 100% accurate, but it at least has
a Profile command.
It seems I'm spending a LOT of time in McuSleepC__getPowerState.
Does that indicate anything?
On Thu, May 5, 2011 at
