Could be a wiring problem. If you somehow wire in Boot in more than one place if will be called 1 time for each such wiring. It sounds like two different Boot interfaces have somehow managed to be wired in in a loop (i.e. one Boot.booted signals another Boot.booted at the bottom of it, and the second Boot interface is fed back into the first via a wiring error). Can't say for sure though without seeing the code.
Kevin On Thu, May 29, 2008 at 11:43 AM, Jack Travis <[EMAIL PROTECTED]> wrote: > second try... > > any advice is welcome. > > Thx > > ---------- Forwarded message ---------- > From: Jack Travis <[EMAIL PROTECTED]> > Date: Tue, May 27, 2008 at 5:12 PM > Subject: erratic boot.booted > To: tiny help <[email protected]> > > > Hi all, > > I am having an erratic problem with my platform and I could use some advice. > > OK here is the situation. > > I am working on an application and sometimes a get a bug which is totally > unrelated to the code I am writing. I tried improving the initialization > code for my platform and it fixed the problem the first time until it came > back after doing changes that are unrelated to the boot up sequence. > Loading similar applications on the same platform works well (the boot > sequence should be fine!?!). > > Actual bug description: > The boot.booted event is triggered multiple time 100x 1000x ? Then > everything stops. timers are not running. > > When the application works (I removed an Alarm32khz16C()), the boot.booted > is still triggered a few times (3x). > > Anyone as suggestion on what I should check. > > Thanks > > > > > > > > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- ~Kevin _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
