And is there anything in the errata sheet? I remember once coming across an
errata where the device would not wake up from LPM if the interrupt is
triggered a few clock cycles after the LPM instruction.
On Mon, Nov 25, 2013 at 11:38 PM, Andrew McLaren and...@aratika.co.nzwrote:
I'll plug
I'll plug Valentin's response in below, as it's got tied to my erroneous
post (I always thought this was keyed on the message title, but seems to be
more than that?).
In the test code I was running, I was literally doing nothing more than the
bare minimum I needed to do to get the MSP running
Hi
I'm not sure if it is directy related to your issue but one thing I noticed
when debugging targets with MSPGCC is the following.
My program is using Timer A and directly after programming the MSP with
mspdebug the Timer A is not starting up. It is simply not counting. I have
to powercycle the
I'm seeing a bit of a weird situation that I don't really understand. I
suspect it will be something simple (hopefully just a 'dumb user error'!).
It affects the ability of the debugger to reload/restart code following an
LPM3 state.
I've been able to reduce the logic to simply the command that
Seemed to have managed to post this as a reply to another thread... Should
be here on its own!
I'm seeing a bit of a weird situation that I don't really understand. I
suspect it will be something simple (hopefully just a 'dumb user error'!).
It affects the ability of the debugger to
