Hi,
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power mode
to stop the arm core to reduce power consumption. All IT and peripheral are
still ON in this mode, only the arm core is sleeping.
The problem is when we want to use our probe (Olimex ARM-USB-OCD) with
OpenOCD (0.5.0 from
On 6 July 2011 10:02, Luc ANTOLINOS luciogi...@gmail.com wrote:
Hi,
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power mode
to stop the arm core to reduce power consumption. All IT and peripheral are
still ON in this mode, only the arm core is sleeping.
Have you tried
Hi,
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power mode
to stop the arm core to reduce power consumption. All IT and peripheral are
still ON in this mode, only the arm core is sleeping.
I the software running on the CPU doesn't use the power reduction mode (arm
core is
On 6 July 2011 11:08, Spencer Oliver s...@spen-soft.co.uk wrote:
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power
mode
Have you tried reducing the jtag clock?
Hi,
I've try the following settings :
- jtag_khz 1 == Still can not halt or reset the board
- jtag_rclk 1 == RCLK
On 6 July 2011 11:29, Laurent Gauch laurent.ga...@amontec.com wrote:
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power mode
Try to reduce the JTAG frequency or use a JTAGkey-2 with RTCK feature
enabled since you have a ARM -s (arm7tdmi-s core).
The RTCK will help to have
On 06/07/2011 10:53, Luc ANTOLINOS wrote:
On 6 July 2011 11:08, Spencer Oliver s...@spen-soft.co.uk
mailto:s...@spen-soft.co.uk wrote:
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE
power mode
Have you tried reducing the jtag clock?
Hi,
I've try the following
On Wed, Jul 6, 2011 at 11:02 AM, Luc ANTOLINOS luciogi...@gmail.com wrote:
Hi,
I'm working with an LPC2388 (arm7tdmi-s core). I use the IDLE power mode
to stop the arm core to reduce power consumption. All IT and peripheral are
still ON in this mode, only the arm core is sleeping.
The
On 6 July 2011 12:05, Spencer Oliver s...@spen-soft.co.uk wrote:
Can you provide a full openocd log?
Attached to this mail. Debug level 3.
It may be worth at this point to use telnet until we get a better idea of
the issue.
Ok.
Here is the sequence of commands (telnet on port ):
On 6 July 2011 11:58, Luc ANTOLINOS luciogi...@gmail.com wrote:
On 6 July 2011 12:05, Spencer Oliver s...@spen-soft.co.uk wrote:
Can you provide a full openocd log?
Attached to this mail. Debug level 3.
I really need to see a log of the actual problem, eg. you connect ok
then when the
On 6 July 2011 12:37, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote:
From OpenOCD Manual
Thanks for all the pointers to the documentation. From these
informations, I understand the better way is to not use the wait for
IRQ or other related low power consumption mode.
It is off course possible
On Wed, Jul 6, 2011 at 1:08 PM, Luc ANTOLINOS luciogi...@gmail.com wrote:
On 6 July 2011 12:37, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote:
From OpenOCD Manual
Thanks for all the pointers to the documentation. From these
informations, I understand the better way is to not use the wait
On 6 July 2011 12:14, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote:
On Wed, Jul 6, 2011 at 1:08 PM, Luc ANTOLINOS luciogi...@gmail.com wrote:
On 6 July 2011 12:37, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote:
From OpenOCD Manual
Thanks for all the pointers to the documentation. From
On 6 July 2011 13:17, Spencer Oliver s...@spen-soft.co.uk wrote:
Openocd did work ok for wfi as long as the jtag clock was slow enough.
However this was broken in HEAD last time i tested it - it has been on
my look at list for a while
I'm not using 'WFI' instruction, I've found this one in the
On 6 July 2011 13:17, Spencer Oliver spen at spen-soft.co.uk
https://lists.berlios.de/mailman/listinfo/openocd-development wrote:
/ Openocd did work ok for wfi as long as the jtag clock was slow enough.
// However this was broken in HEAD last time i tested it - it has been on
// my look at list
On Wed, Jul 6, 2011 at 1:40 PM, Andreas Fritiofson
andr...@fritiofson.net wrote:
How could this work if the core clock is stopped?
This should work, as host JATG inteface embedded in the ARM core has a
procedure to remove WFI when it gets debug request from the dongle (if
everything is well
On Wed, Jul 6, 2011 at 1:36 PM, Luc ANTOLINOS luciogi...@gmail.com wrote:
On 6 July 2011 13:17, Spencer Oliver s...@spen-soft.co.uk wrote:
Openocd did work ok for wfi as long as the jtag clock was slow enough.
However this was broken in HEAD last time i tested it - it has been on
my look at
On 6 July 2011 13:52, Laurent Gauch laurent.ga...@amontec.com wrote:
Are you sure your Target JTAG interface is active in your low power mode ?
You seams to be right (even if I have not found this information in
the user manual of the LPC2388 for the moment) :
From
On 6 July 2011 13:55, Drasko DRASKOVIC drasko.drasko...@gmail.com wrote:
For the sake of experiment, can you try with WFI, and tell us what you
are getting ?
asm(wfi;);
== /tmp/cctkCVDM.s: Assembler messages:
/tmp/cctkCVDM.s:5275: Error: selected processor does not support ARM mode `wfi'
'wfi'
On Wed, Jul 6, 2011 at 1:57 PM, Spencer Oliver s...@spen-soft.co.uk wrote:
On 6 July 2011 12:36, Luc ANTOLINOS luciogi...@gmail.com wrote:
On 6 July 2011 13:17, Spencer Oliver s...@spen-soft.co.uk wrote:
Openocd did work ok for wfi as long as the jtag clock was slow enough.
However this was
On 6 July 2011 13:52, Laurent Gauch laurent.gauch at amontec.com
https://lists.berlios.de/mailman/listinfo/openocd-development wrote:
/ Are you sure your Target JTAG interface is active in your low power mode ?
/You seams to be right (even if I have not found this information in
the user manual
20 matches
Mail list logo
