Hallo Rowley team,

in my app I put the board to sleep (PMODE = 3) and let
it wake up when button is pressed or when WDT
timer elapses. Sometimes this works fine, but more
often I receive messages like:

Server Terminate Operation Failed
Read from ARM debug comm port timed out

Sometimes the app goes into address 0xffffffe8 (or
near) where it is in "break" state. Sometimes it
loops in libarm_dcc_write (write_wait). Next time I
debug I receive (sometimes):

Cannot halt target after reset

And I have to disconnect/poweroff the board to be able
to debug again. Can I do something about it,
like tell the debugger "sleep" and then "wakeup", or
enable clocks for some modules (even when board
in sleep), or let the board wakeup for some
debugging-related event?

Thanks and regards,
Jan

Start a New Thread

Jan,

> in my app I put the board to sleep (PMODE = 3) and let
> it wake up when button is pressed or when WDT
> timer elapses. Sometimes this works fine, but more
> often I receive messages like:
>
> Server Terminate Operation Failed
> Read from ARM debug comm port timed out
>
> Sometimes the app goes into address 0xffffffe8 (or
> near) where it is in "break" state. Sometimes it
> loops in libarm_dcc_write (write_wait). Next time I
> debug I receive (sometimes):
>
> Cannot halt target after reset
>
> And I have to disconnect/poweroff the board to be able
> to debug again. Can I do something about it,
> like tell the debugger "sleep" and then "wakeup", or
> enable clocks for some modules (even when board
> in sleep), or let the board wakeup for some
> debugging-related event?

Putting CPUs to sleep usually takes the TAP.JTAG down with it. I would
recommend that you don't do this... The IDE has no idea when the CPU will
sleep, and no, you can't tell the IDE when the core is asleep...

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

Start a New Thread

Hi Paul,

thanks, I can live without it for debugging and hope
it works in release. Isn't there a holiday
today in England?

Jan

----- Original Message -----
From: "Paul Curtis"
To:
Sent: Monday, May 26, 2008 11:34 AM
Subject: RE: [lpc2000] debugging power-down in
Crossworks, LPC288x
> Jan,
>
>> in my app I put the board to sleep (PMODE = 3) and
let
>> it wake up when button is pressed or when WDT
>> timer elapses. Sometimes this works fine, but more
>> often I receive messages like:
>>
>> Server Terminate Operation Failed
>> Read from ARM debug comm port timed out
>>
>> Sometimes the app goes into address 0xffffffe8 (or
>> near) where it is in "break" state. Sometimes it
>> loops in libarm_dcc_write (write_wait). Next time I
>> debug I receive (sometimes):
>>
>> Cannot halt target after reset
>>
>> And I have to disconnect/poweroff the board to be
able
>> to debug again. Can I do something about it,
>> like tell the debugger "sleep" and then "wakeup",
or
>> enable clocks for some modules (even when board
>> in sleep), or let the board wakeup for some
>> debugging-related event?
>
> Putting CPUs to sleep usually takes the TAP.JTAG
down with it. I would
> recommend that you don't do this... The IDE has no
idea when the CPU will
> sleep, and no, you can't tell the IDE when the core
is asleep...
>
> --
> Paul Curtis, Rowley Associates Ltd
http://www.rowley.co.uk
> CrossWorks for ARM, MSP430, AVR, MAXQ, and now
Cortex-M3 processors

Start a New Thread

Hi Jan,

> thanks, I can live without it for debugging and hope
> it works in release. Isn't there a holiday
> today in England?

Yep, it's rainy Monday bank holiday.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

Start a New Thread