Regarding your comments about documenting stuff.
At some point we're risk drowning the user in information that
he can't possibly relate to. If the issues relate to the current state
of OpenOCD w.r.t. a problem we'll be fixing in the code in the next
3-6 months, then perhaps it is better to docume
Hi Ronald,
FYI: A while ago I tried to chain watchpoints together, but failed. This is
useful when debugging multi-threaded code. See:
https://lists.berlios.de/pipermail/openocd-development/2008-May/002193.html
Best regards,
Pieter
-Original Message-
From: Ronald Vanschoren [mailto:[EM
On Nov 30, 2008, at 9:59 PM, Duane Ellis wrote:
duane> What is the required work area size?
rick> None. The flash methods
Actually the flash methods do need space - otherwise they will not
work.
That isn't true for at least the Stellaris flash code. It will fall
back to hittin
duane> What is the required work area size?
rick> None. The flash methods
Actually the flash methods do need space - otherwise they will not work.
Thank you for pointing out the flash - I had forgotten about that.
There are two sides to the problem.
(A) flash programing - I had forgotte
Hi,
I've just started using OpenOCD on a Cortex-M3 platform and am looking
into thread support for RTOS's.
I've seen Øyvind Harboe's post of 5 Nov titled "Support for eCos threads
in OpenOCD", but didn't see much replies. So I'm trying again, hoping
there are more people on this list that would l
On Nov 30, 2008, at 6:26 PM, Duane Ellis wrote:
What is the required work area size?
None. The flash methods attempt to allocate space for the flash
algorithm and a data block area. They start with the size needed to
contain the whole image and divide that by 2 on failure. If the size
What is the required work area size?
I know that having a work area and the DCC can give a 5x to 10x download
speed improvement.
-Duane.
Reasons for my question is the following:
=
For example some chips have lots of ram. Some chips do not have much.
What happens when the download goes ov
I write this as a separate (from my Commit) email hoping it stops some
email and help you solve some immediate problems.
-Duane.
The command:
jtag_device IRLEN IRCAPTURE IRMASK IDCODE
Has been removed.
The "quick fix" is as follows.
set _CHIPNAME mychip
set _CPUTAPID 0.
For those who do not know - I am a new commit person for OpenOCD.
I have just committed a large (in size) but small (in scope) patch. The
patch is 300K, I did not attach it.
There may be some "bumps" in the road, they should be sorted out
*QUICKLY*.
If you are reading this and
* you are a "p
Duane Ellis wrote:
> The simple truth is - the same (target) CHIP is used on MULTIPLE boards,
> having a common reusable CHIP config file is a good thing.
>
>
I think it's a good idea.
___
Openocd-development mailing list
Openocd-development@lists.b
> Comments?
Sounds good. :-)
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listin
11 matches
Mail list logo
