Janos and Aurelien, Thank you for the response and suggestions. I have checked out avarice from cvs and compiled it with usb support. Giving it the arguments suggested by Aurelien solves my issue with sleep. However, I am still having trouble with "atomic". If I have an atomic section in my nesC code then doing a step or next into this code in ice-gdb never returns control back to the debugger. Have you experienced something like this? Is there any workaround for this?
Once again thank you for the help. On Tue, Jun 24, 2008 at 1:33 AM, Aurelien Francillon <[EMAIL PROTECTED]> wrote: > Le Monday 23 June 2008 14:42:02 Sarfraz Nawaz, vous avez écrit : >> Hello everyone, > Hi, > >> breakpoints. My first breakpoint is on BlinkC$Boot$booted which is >> successfully hit. However, after that when I continue I keep getting >> the following message from gdb >> >> (gdb) c >> Continuing. >> >> Target went to sleep >> >> Program received signal SIGINT, Interrupt. >> McuSleepC$McuSleep$sleep () >> at /opt/tinyos-2.x/tos/chips/atm1281/McuSleepC.nc:136 >> 136 cli(); >> > which version do you use CVS ? a recent snapshot? > you most probably need to ask avarice not to stop on the event "target went to > sleep". > you can do this with some thing like (on one line, note the "target_sleep" > event others are the default ones ) > > export AVARICE_ARGS='--mkII --jtag usb --event > none,run,target_power_on,target_wakeup,target_sleep' > > then start ice gdb as usual > ice-gdb > > the sleep event should not be fired anymore ... > cheers > Aurelien > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
