I've recently begun work on maintaining and adding functionality to an existing product using the Chipcon CC1010. <snip>
sometimes it is simple you are adding code could it be starving the watchdog? Erik
Hi guys, thanks for the input. The watchdog has been disabled for now so that one can be pretty much ruled out. As far as code segments go, unfortunately it's happening somewhere in a 17Kb source file - that I'm essentially unfamiliar with. I suspect the easiest thing to do is to have a look at the map and check where memory for those functions is being allocated. These usually seem to have memory allocated from where the function pointer was assigned, as opposed to where it is actually called from. Thanks for the help Cheers D.
Why not just set a breakpoint on the reset vector, enable trace, and see what causes the reset that way?
Jon