Does anyone have any idea what is causing this anomaly? Regards, Bharat.
On Thu, Sep 3, 2009 at 8:19 PM, bharat naik <[email protected]> wrote: > Hi, > > I tried running the Blink application. It was working fine a few > days back. However, now when I did: > make pc > ./main.exe -t=30 4 > > I got completely different results. > Here's what I got: > > > SIM: EEPROM system initialized. > SIM: event queue initialized. > SIM: Random seed is 726451 > SIM: Initializing sockets > SIM: Created server socket listening on port 10584. > SIM: Created server socket listening on port 10585. > SIM: Time for mote 0 initialized to 37552002. > SIM: Time for mote 1 initialized to 9035434. > SIM: Time for mote 2 initialized to 17492501. > SIM: Time for mote 3 initialized to 35430226. > 3: BOOT: Scheduling for boot at 0:0:9.38800050. > 3: BOOT: Scheduling for boot at 0:0:2.25885850. > 3: BOOT: Scheduling for boot at 0:0:4.37312525. > 3: BOOT: Scheduling for boot at 0:0:8.85755650. > 3: Popping event for mote 1 with time 0:0:2.25885850. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: BOOT: Mote booting at time 0:0:2.25885850. > 1: CLOCK: Setting clock rate to interval 231, scale 3 > 1: malloc data entry for clock event: 0x80fa7c8 > 1: LEDS: initialized. > SIM: eventAcceptThread running. > SIM: commandReadThread running. > 1: Popping event for mote 1 with time 0:0:2.48443000. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: CLOCK: event handled for mote 1 at 0:0:2.48443000 (902286 ticks). > 1: CLOCK: Setting clock interval to 231 @ 0:0:2.48443000 > 1: malloc data entry for clock event: 0x80fa808 > 1: Popping event for mote 1 with time 0:0:2.71000150. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: event_cleanup: freeing event: 0x80fa7a0 > 1: event_total_cleanup: freeing event data: 0x80fa7c8 > 1: event_total_cleanup: freeing event: 0x80fa7a0 > 1: Popping event for mote 1 with time 0:0:2.71000150. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: CLOCK: event handled for mote 1 at 0:0:2.71000150 (902286 ticks). > 1: CLOCK: Setting clock interval to 231 @ 0:0:2.71000150 > 1: malloc data entry for clock event: 0x80fa7c8 > 1: Popping event for mote 1 with time 0:0:2.93557300. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: event_cleanup: freeing event: 0x80fa7e0 > 1: event_total_cleanup: freeing event data: 0x80fa808 > 1: event_total_cleanup: freeing event: 0x80fa7e0 > 1: Popping event for mote 1 with time 0:0:2.93557300. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: CLOCK: event handled for mote 1 at 0:0:2.93557300 (902286 ticks). > 1: CLOCK: Setting clock interval to 231 @ 0:0:2.93557300 > 1: malloc data entry for clock event: 0x80fa808 > 1: Popping event for mote 1 with time 0:0:3.16114450. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: event_cleanup: freeing event: 0x80fa7a0 > 1: event_total_cleanup: freeing event data: 0x80fa7c8 > 1: event_total_cleanup: freeing event: 0x80fa7a0 > 1: Popping event for mote 1 with time 0:0:3.16114450. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: CLOCK: event handled for mote 1 at 0:0:3.16114450 (902286 ticks). > 1: CLOCK: Setting clock interval to 77 @ 0:0:3.16114450 > 1: malloc data entry for clock event: 0x80fa7c8 > 1: Popping event for mote 1 with time 0:0:3.23633500. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: CLOCK: event handled for mote 1 at 0:0:3.23633500 (300762 ticks). > 1: CLOCK: Setting clock interval to 231 @ 0:0:3.23633500 > 1: malloc data entry for clock event: 0x80fa848 > 1: LEDS: Red on. > 1: Popping event for mote 1 with time 0:0:3.31152550. > 1: Setting TOS_LOCAL_ADDRESS to 1 > 1: event_cleanup: freeing event: 0x80fa7a0 > 1: event_total_cleanup: freeing event data: 0x80fa7c8 > ............................................ > and the same thing continued. Is this because of lack of space or > something? I haven't touched the Blink application since the time it > worked properly. > > Regards, > Bharat. >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
