I do not remember finding it, or fixing it.

It was one prototype and my customer has been testing it for 6 months
and most likely he has not left it on that long, or else the problem
disappeared. Otherwise I would have heard from him.

Next time it is here I will try to run it that long again.

Kip

On Fri, 2007-10-26 at 16:51 +0300, Tolga COPLU wrote:
> Hi all,
>
> I am using a wireless sensor node hardware with MSP430F1611 and a
> CC2420. I am having similar problem defined under the discussion given
> with "Lock up through power cycling".
>
> My hardware is undeterministically locked up. However, a power off /
> power on event does not make it work.
>
>
>
> I would like to ask if Kipton has found the problem. (I could not find
> the root cause or the answer in the mailing list)
>
>
>
> Thanks,
>
> Tolga Coplu
>
> www.genetlab.com
>
> ________________________________
>
> From: m... [mailto:m...] On Behalf
> Of Kipton Moravec
> Sent: Thursday, February 22, 2007 6:16 PM
> To: m...
> Subject: Re: [msp430] Re: Lock up through power cycling.
>
>
>
> I stay away from alloc/dealloc in embedded systems. I never use them.
>
> The Stack already seems to be pre-loaded with 0xCD. I have watched it
> and so far the initialization routines use more of the stack than the
> main program, that runs after the first 60 seconds and we get GPS lock.
> It does not seem to be creeping.
>
> I have removed the two subroutines that initialize information memory at
> startup, and load it with erasing main memory only. There are no FLASH
> write routines in the code at all.
>
> If it was something with anything to do with RAM, (Stack, allocations,
> etc.) cycling power should fix it. It does not.
>
> On Thu, 2007-02-22 at 07:54 -0600, Lou C wrote:
> > >I am betting on a stack Issue...why not fill the unused space with a
> know
> > >value like DEADBEEF ;) and have the ram dumped at periodic intervals
> to see
> > >if ram usage is growing
> >
> > I agree. Because he seems to have a problem after a certain period of
> time
> > has passed, I also think it is something in his code. I would
> recommend in
> > a periodic ISR to read the value of the stack pointer and write it to
> a
> > memory location. Then, at the 29th hour, stop the processor and read
> the
> > value of the stack pointer variable. Something seems to be building up
> and
> > finally causes a problem at the 30th hour.
> >
> > I suppose it could also be the heap. If you do any alloc/dealloc's, I
> would
> > look at that to see if somehow it is filling memory.
> >
> > BTW, I like your DEADBEEF fill, I will have to try that some time. I
> used
> > to use just DEAD.
> >
> > Lou
> >
> > __________________________________________________________
> > Don't miss your chance to WIN 10 hours of private jet travel from
> Microsoft(r)
> > Office Live
> http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/
>
> >
> >
> >
> >
> >
>
> >
> >
> > Yahoo! Groups - Join or create groups, clubs, forums &
> communities. Links
> >
> >
> >
> >
--
Kipton Moravec KE5NGX
"Always do right; this will gratify some people and astonish the rest."
--Mark Twain Start a New Thread