On Wed, 24 Feb 2010, David Brownell wrote:
> More like: the "nested lists" structure of the NEWS file got
> mangled on its way through WordPress. The several bullets
> after the trailing "ARM11" should have nested under an ARM11
> heading ... similarly with "Cortex-A8".
Things look much better
On Sun, 21 Feb 2010, David Brownell wrote:
> Archives are in the Berlios and SourceForge "files" areas.
The berlios web page shows the highlights strangely in some cases:
- basic semihosting support (ARM7/ARM9 only, for now) ARM11
- Should act much more like other ARM cores:
[...]
- Shar
From: Spencer Oliver
> @@ -480,6 +460,39 @@ int arm_semihosting(struct target *target, int
> *retval)
> return 0;
> }
>
> - *retval = do_semihosting(target);
> + lr = buf_get_u32(ARMV4_5_CORE_REG_MODE(arm->core_cache, ARM_MODE_SVC,
> 14).value, 0, 32);
> +
FYI, I just pushed the following:
commit 3d2d5dcc9c27b84dc2e5e9ed53be0f784a450042
Author: Nicolas Pitre
Date: Tue Feb 2 00:05:42 2010 -0500
ARM semihosting: fix EOF handling with SYS_READ
The semihosting interface has a strange convention for read/write where
the unused
On Mon, 1 Feb 2010, Øyvind Harboe wrote:
> On Mon, Feb 1, 2010 at 1:26 PM, Spencer Oliver wrote:
> > Øyvind Harboe wrote:
> >>>
> >>> should this include not be going in helper/system.h ?
> >>
> >> I generally try to avoid include everything everywhere... so I think it is
> >> nice that it goes i
On Wed, 27 Jan 2010, Spencer Oliver wrote:
> Cygwin would fail to reopen a previously written file if the mode is
> not given.
What do you mean?
> Simplified converting the open flags and made sure the win32 O_BINARY
> bit is set.
ACK.
> Added define for systems that do not support O_BINARY.
On Wed, 27 Jan 2010, Spencer Oliver wrote:
> > When do_semihosting() returns with an error, the caller should return right
> > away with 1 as the original code did and not 0 like the patch does.
> >
>
> I am confused as the code in git master is:
> if ((*retval = do_semihosting(target, &arm->sem
On Tue, 26 Jan 2010, David Brownell wrote:
> On Tuesday 26 January 2010, Nicolas Pitre wrote:
> > Finally the fix for FLEN could be split in a patch of its own too as
> > this is clearly an orthogonal issue.
>
> If you agree this is a bug, then it should get fixed
> bef
On Tue, 26 Jan 2010, David Brownell wrote:
> On Tuesday 26 January 2010, Nicolas Pitre wrote:
> >
> > > > For the record: I did get that working with an ARM9, no
> > > > changes, using the latest CodeSourcery EABI toolchain.
> > > >
> > >
On Tue, 26 Jan 2010, Spencer Oliver wrote:
> David Brownell wrote:
> > On Tuesday 26 January 2010, Spencer Oliver wrote:
> >> I could not get the original implementation from Nicolas Pitr working
> >> when outputting to stdout.
> >
> > For the record: I did get that working with an ARM9, no
> >
On Wed, 9 Dec 2009, David Brownell wrote:
> On Wednesday 09 December 2009, Nicolas Pitre wrote:
> > This is wrong for Feroceon and Dragonite which have only one of them.
> > In that case arm7_9->wp_available_max is initialized to 1 in the
> > target_create method,
This commit adds in src/target/embeddedice.c a plain
LOG_INFO("%s: hardware has 2 breakpoints or watchpoints", ...
This is wrong for Feroceon and Dragonite which have only one of them.
In that case arm7_9->wp_available_max is initialized to 1 in the
target_create method, but the above
On Wed, 9 Dec 2009, Freddie Chopin wrote:
> Nicolas Pitre pisze:
> > What limitations?
> >
> > I never considered the C language to bare any limitations what so ever.
> > You can do much more in C, and with way more control and performance,
> > tha
On Wed, 9 Dec 2009, Pieter Conradie wrote:
> I get the impression that you (the developers) are butting your head
> against the limitations of C.
What limitations?
I never considered the C language to bare any limitations what so ever.
You can do much more in C, and with way more control and
On Mon, 7 Dec 2009, David Brownell wrote:
> Move the ARM opcode macros from , and a few
> Thumb2 ones from , to more appropriate homes
> in a new file.
What about changing the names of a couple of those macros as well? Say
ARMV4_5_STMIA(). This isn't an instruction for ARMv4 or ARMv5 only. I
Fall back to software breakpoint when vector catch isn't available.
Possible enhancements:
- add extra optional command parameter to select high vectors
- add extra optional command parameter to select hardware breakpoint
Signed-off-by: Nicolas Pitre
---
src/target/arm7_9_common.c |
Signed-off-by: Nicolas Pitre
---
src/target/arm_semihosting.c | 10 --
1 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/src/target/arm_semihosting.c b/src/target/arm_semihosting.c
index 39625f6..d448d54 100644
--- a/src/target/arm_semihosting.c
+++ b/src/target
On Fri, 4 Dec 2009, David Brownell wrote:
> Clean up arm_semihosting() entry a bit, comment some issues and just
> which SVC opcodes are getting intercepted. Microcontroller profile
> cores will need a new entry, since they don't use SVC there (or even
> have an SVC mode).
In that case they use
On Thu, 3 Dec 2009, David Brownell wrote:
> On Thursday 03 December 2009, Nicolas Pitre wrote:
> > Semihosting enables code running on an ARM target to use the I/O
> > facilities on the host computer. The target application must be linked
> > against a library that forwards
On Thu, 3 Dec 2009, David Brownell wrote:
> Cool!
>
> On Thursday 03 December 2009, Nicolas Pitre wrote:
> > > Some docs to openocd.texi would be great.
> >
> > It sure would. ;-)
>
> More like "essential". ;)
I provided the minimum in version 2
.0.
Signed-off-by: Nicolas Pitre
---
Changes from version 1:
- abstracted the semihosting hook away for easy reuse by other ARM
archs plus some usage comment
- stat() is no more: used lseek() instead to increase portability
- added include guard and copyright in arm_semihosting.h
On Thu, 3 Dec 2009, Zach Welch wrote:
> On Thu, 2009-12-03 at 12:27 -0500, Nicolas Pitre wrote:
> > On Thu, 3 Dec 2009, Zach Welch wrote:
> >
> > > On Thu, 2009-12-03 at 10:39 +0100, Øyvind Harboe wrote:
> > > > I added a missing #include , but it i
On Thu, 3 Dec 2009, Igor Skochinsky wrote:
> Hello Nicolas,
>
> Thursday, December 3, 2009, 7:58:05 AM, you wrote:
>
>
> NP> Semihosting enables code running on an ARM target to use the I/O
> NP> facilities on the host computer. The target application must be linked
> NP> against a library that
On Thu, 3 Dec 2009, Øyvind Harboe wrote:
> I added a missing #include , but it is not quite ready to commit
> yet I think.
>
> Does it build under Windows? Perhaps it does, I didn't try.
It probably does. We maintain both a Linux and Windows build internally
and I didn't get any complaint yet.
On Thu, 3 Dec 2009, Zach Welch wrote:
> On Thu, 2009-12-03 at 10:39 +0100, Øyvind Harboe wrote:
> > I added a missing #include , but it is not quite ready to commit
> > yet I think.
> >
> > Does it build under Windows? Perhaps it does, I didn't try.
> >
> > I don't think we should try to make th
The Feroceon and Dragonite cores are similar to the ARM926 and ARM966
cores respectively.
Signed-off-by: Nicolas Pitre
---
diff --git a/src/target/Makefile.am b/src/target/Makefile.am
index b083a55..df42413 100644
--- a/src/target/Makefile.am
+++ b/src/target/Makefile.am
@@ -58,11 +58,11
.0.
Signed-off-by: Nicolas Pitre
diff --git a/src/target/Makefile.am b/src/target/Makefile.am
index cb473a3..b083a55 100644
--- a/src/target/Makefile.am
+++ b/src/target/Makefile.am
@@ -80,6 +80,7 @@ ARM_DEBUG_SRC = \
arm_jtag.c \
arm_disassembler.c \
On Tue, 24 Nov 2009, Zach Welch wrote:
> On Tue, 2009-11-24 at 22:08 -0500, Nicolas Pitre wrote:
> > Your usage of --in-reply-to is wrong. That made all patch series to end
> > up in the same thread.
>
> How could I have done it right? Of course, this assumes that sending
On Tue, 24 Nov 2009, Zach Welch wrote:
> On Tue, 2009-11-24 at 21:55 -0500, Nicolas Pitre wrote:
> > On Tue, 24 Nov 2009, Zach Welch wrote:
> >
> > > On Tue, 2009-11-24 at 16:33 -0600, Dean Glazeski wrote:
> > > > First of all, screw you for all o
On Tue, 24 Nov 2009, Zach Welch wrote:
> On Tue, 2009-11-24 at 16:33 -0600, Dean Glazeski wrote:
> > First of all, screw you for all of these patches. Frekin' 80+ emails!
>
> Yeah, sorry. ;) I particularly apologize for 'git send-email' failing
> to properly thread the messages for each series
On Sat, 7 Nov 2009, David Brownell wrote:
> The other is that we really don't have a team of folk set up
> to build for different Linux distros, BSDs, MacOS, Windows, etc;
> and IMO, we shouldn't. There *are* teams of folk set up to
> build for those ... e.g. the Fedora project builds regularly,
On Thu, 5 Nov 2009, David Brownell wrote:
> On Thursday 05 November 2009, Nicolas Pitre wrote:
> > If advertised as 0.3.0 then there is a pretty good chance it is the
> > true 0.3.0.
>
> Only if "pretty good" means "100%". ;)
>
> Of course, that m
On Fri, 6 Nov 2009, CeDeROM wrote:
> Hello guys!
>
> I try to maintain OpenOCD port for FreeBSD, and I think current
> numbering scheme sux and brings great confusion - there are two unused
> digits in the release number and now there is also a -rc0 suffix. This
> is a MESS! I don' like it.
Well
On Mon, 2 Nov 2009, David Brownell wrote:
> That is, "git describe efef05870d726fe4cb6786d785fae4628fe7ec1e"
> will tell you that it's 125 commits after the v0.2.0 tag.
BTW, when using that 40 character hex string, you can abbreviate it to
the first 7 or 8 characters. Git will accept it as long
On Fri, 30 Oct 2009, David Brownell wrote:
> On Friday 30 October 2009, Nicolas Pitre wrote:
> > I really don't like this pointer business. No type checking at all,
> > etc. This should be turned upside down as you suggested already: embed
> > more generic structure
On Fri, 30 Oct 2009, David Brownell wrote:
> I'm suspecting this code can never have worked, since the
> original commit (svn #335) in early 2008.
>
> Fix is just copy/paste from another (working) function.
> ---
> src/target/arm926ejs.c |4 +++-
> 1 file changed, 3 insertions(+), 1 deletion
On Thu, 29 Oct 2009, Øyvind Harboe wrote:
> How's this branch btw? (comments, signoff, etc.)
>
> It's where I exercise my rebase skills :-)
>
> http://repo.or.cz/w/openocd/oharboe.git?a=shortlog;h=refs/heads/mrcmcr
You're making progress!
One example where improvements could be made though:
h
On Thu, 29 Oct 2009, Øyvind Harboe wrote:
> Maybe I'm using rebase incorrectly, but when code is reordered
> (to avoid declarations to resolve forward references), then a
> rebase will not run without requiring manual merging.
Exact.
> If rebase can't merge reordering of code automatically, then
On Thu, 29 Oct 2009, Øyvind Harboe wrote:
> If the particular issue above is caught red-handed we'll
> be able to evaluate whether or not we have something
> which is optimized too much for marginal speed gains
> and too little for stability...
The work area is used for far more things than just
On Thu, 29 Oct 2009, Øyvind Harboe wrote:
> In OpenOCD there is a bit of clever handling of working areas.
>
> You can essentially allocate a piece of working memory on the target and
> store e.g. an algorithm into that working area over an extended period
> of time to improve performance.
>
> I
On Wed, 28 Oct 2009, David Brownell wrote:
> On Wednesday 28 October 2009, Zach Welch wrote:
> > I am becoming fairly discouraged by the ongoing high-pace use of the
> > central repository, seeing this type of commit pushed without sufficient
> > review period. Are we trying for 0.3.0, or not?!?
Only type 1 branch instruction has a condition code, not type 2.
Currently they're both tagged with ARM_B which doesn't allow for the
distinction.
Signed-off-by: Nicolas Pitre
---
src/target/arm_simulator.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/
A Thumb BLX instruction is branching to ARM code, and therefore the
first 2 bits of the target address must be cleared.
Signed-off-by: Nicolas Pitre
---
src/target/arm_disassembler.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/target/arm_disassembler.c b/src
On Tue, 27 Oct 2009, David Brownell wrote:
> On Monday 26 October 2009, Nicolas Pitre wrote:
> > Here are 3 patches to fix all the remaining issues I've encountered with
> > single-step support and Thumb mode.
> >
> > [PATCH 1/3] call thumb_pass_branch_co
On Tue, 27 Oct 2009, Øyvind Harboe wrote:
> On Tue, Oct 27, 2009 at 2:27 PM, John Devereux wrote:
> > Øyvind Harboe writes:
> >
> >> From a developer point of view, I'm satisified with pushing dev branches
> >> to http://repo.or.cz/w/openocd.git. I have not yet used a shared developer
> >> branc
On Tue, 27 Oct 2009, John Devereux wrote:
> Øyvind Harboe writes:
>
> > From a developer point of view, I'm satisified with pushing dev branches
> > to http://repo.or.cz/w/openocd.git. I have not yet used a shared developer
> > branch... Who in their right mind would get involved in the mrcmcr b
single-stepping of
Thumb2 code is implemented. But for now this appears to be the simplest
solution to fix Thumb1 support.
Signed-off-by: Nicolas Pitre
---
src/target/arm_simulator.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/src/target/arm_simulator.c b
bit
is not always relevant (like when PC is used with ALU insns or as an index
with some addressing modes). It is unclear which way would be simpler in
the end.
Signed-off-by: Nicolas Pitre
---
src/target/arm_simulator.c | 55 ++-
1 files changed, 33
no condition code.
While at it, let's make the nearby code more readable by reducing some of
the redundant brace noise and reworking the error handling construct.
Signed-off-by: Nicolas Pitre
---
src/target/arm_simulator.c | 14 ++
1 files changed, 6 insertions(+), 8 dele
Here are 3 patches to fix all the remaining issues I've encountered with
single-step support and Thumb mode.
[PATCH 1/3] call thumb_pass_branch_condition() only for actual branch opcodes
[PATCH 2/3] allow proper single stepping of Thumb BL and BLX instructions
[PATCH 3/3] fix Thumb mode handling w
On Mon, 26 Oct 2009, David Brownell wrote:
> Note by the way that public repositories are mostly for
> publishing work you expect others to use. I'm not sure I'd
> expect folk to review patches from repositories as any kind
> of regular thing ... it may be marginally easier to do that
> way than
On Mon, 26 Oct 2009, Spencer Oliver wrote:
>
> Hi,
>
> While i have been away openocd certainly has been busy, while i have used
> git i am no expert - a git guide for devs may be a good idea :)
>
> The following files seem to now be in CRLF format (linux host), whether this
> was a svn-git iss
On Mon, 26 Oct 2009, Zach Welch wrote:
> On Mon, 2009-10-26 at 00:12 +0100, Øyvind Harboe wrote:
> > What about testers, how should they behave?
>
> Any way they please. ;) Seriously, that's perfectly valid question.
> Testers should:
>
> 1) Clone/pull from a branch that interests them.
> 2) Ru
On Mon, 26 Oct 2009, Zach Welch wrote:
> Your suggestion reflects client-server thinking. Really, Git is P2P.
> There are few good reasons to do active branch development in the main
> repository. I established the openocd/testing fork on repo.or.cz to do
> exactly what you describe. Setting t
On Sun, 25 Oct 2009, David Brownell wrote:
> Now, if I could only find out why nontrivial merges
> with git never seem to work right for me. :(
You may have a look at 'git mergetool'.
[...]
> > Eventually, when OpenOCD will become a project as big as the Linux
> > kernel ;-) then major develop
On Sat, 24 Oct 2009, David Brownell wrote:
> > I'm very pleased we have successfully migrated to git
> > before 0.3.
>
> Yes; though as Nico pointed out, doing some work in
> branches would be a good thing. (I'm thinking of
> checking out "stgit" myself ... )
I was a quilt user before Git. The
On Sat, 24 Oct 2009, David Brownell wrote:
> On Saturday 24 October 2009, Igor Skochinsky wrote:
> > I think you need to fix your client unless some relay server screwed
> > up the message. Here, David's email headers say:
> > Content-Type: text/plain; charset="iso-8859-1"
> > Content-Transfer-Enc
On Fri, 23 Oct 2009, Øyvind Harboe wrote:
> Since this work will take place over some period of time, I had to
> commit now.
*IN* *A* *SEPARATE* *BRANCH* !!
Please.
Nicolas
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
htt
On Fri, 23 Oct 2009, David Brownell wrote:
> On Friday 23 October 2009, Øyvind Harboe wrote:
> > I'm not going to hold mcr/mrc hostage to arm11 C interface
> > abstraction cleanup or somesuch. With the current changes
> > committed, it will be a tiny matter to push the mcr/mrc back up
> > to an ar
The wrong variable (pc instead of r0) was used. Furthermore, someone
did cover this error by stupidly silencing the compiler warning that
occurred before a dummy void reference to r0 was added to the code.
---
diff --git a/src/target/feroceon.c b/src/target/feroceon.c
index 8eea33e..f084201 1006
Without this fix, the following code cannot be single stepped:
add ip, pc, #1
bx ip
[thumb code here]
---
diff --git a/src/target/arm_simulator.c b/src/target/arm_simulator.c
index 93fb3dd..e2f49c3 100644
--- a/src/target/arm_simulator.c
+++ b/src/target/arm_simul
On Sun, 18 Oct 2009, David Brownell wrote:
> On Sunday 18 October 2009, Øyvind Harboe wrote:
> > I'm not quite up to speed on this graft stuff(first I heard of
> > it), but I trust you on how to execute this in the best manner.
>
> I didn't know about "graft" (in the non-political sense!)
> befor
On Thu, 8 Oct 2009, David Brownell wrote:
> On Thursday 08 October 2009, Nicolas Pitre wrote:
> >
> > > For the XScale and Sheevaplug things, I suggest Nicolas Pitre
> > > tell us what to do.
> >
> > I don't know anything about OpenOCD and XScale (
t;
> pause ~= sleep
> text output == echo
>
> ... close this "feature request" as resolved.
>
>
> For the XScale and Sheevaplug things, I suggest Nicolas Pitre
> tell us what to do.
I don't know anything about OpenOCD and XScale ((I guess that should be
Øyvi
On Wed, 7 Oct 2009, Raúl Sánchez Siles wrote:
> I said I didn't want to start a flamewar and provided there has been, at
> least, a slight interest on my messages, I'll try to clear up some point and
> leave the thread alone.
I cannot resist correcting you on one point though.
[...]
> That
On Tue, 6 Oct 2009, David Brownell wrote:
> I committed both of yoru Dragonite patches.
Thx.
Nicolas
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Dragonite has the same affliction as feroceon.
Dragonite has the same affliction as feroceon.
diff --git a/src/target/embeddedice.c b/src/target/embeddedice.c
index 0d23c12..39f87c7 100644
--- a/src/target/embeddedice.c
+++ b/src/target/embeddedice.c
@@ -264,7 +264,8 @@ reg_cache_t* embeddedice_bu
Dragonite target script
Dragonite target script
diff --git a/tcl/target/dragonite.cfg b/tcl/target/dragonite.cfg
new file mode 100644
index 000..d2e7e32
--- /dev/null
+++ b/tcl/target/dragonite.cfg
@@ -0,0 +1,31 @@
+##
+# Target:Marvell Dragonite CPU cor
On Mon, 14 Sep 2009, David Brownell wrote:
> What code do we have which wants JTAG chitchat during SRST?
Have a look at sheevaplug_init in tcl/board/sheevaplug.cfg.
Nicolas
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
http
+3,7 @@
* Copyright (C) 2009 Marvell Semiconductor, Inc.
*
* Authors: Lennert Buytenhek
- * Nicolas Pitre
+ * Nicolas Pitre
*
* This file is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License as published by the
On Fri, 11 Sep 2009, Spencer Oliver wrote:
>
> > The SheevaPlug interface is now unusable since rev 2573:
> >
> > Error: unable to open ftdi device: device not found
> > Runtime error, file "command.c", line 469:
> >
> > Backing out changes from that revision does indeed fix the issue.
> > So w
On Fri, 11 Sep 2009, Øyvind Harboe wrote:
> Added the missing line in target.c and committed.
Thanks.
Nicolas
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Fri, 11 Sep 2009, Øyvind Harboe wrote:
> Why doesn't target.c doesn't add dragonite_target to the target_types array?
Oops. I did add the extern declaration, but forgot to add it back into
the array as well when I cleaned up that patch.
Nicolas
__
feroceon.c: put feroceon target definition at the end so to avoid a
bunch of useless forward declarations.
feroceon.c: put feroceon target definition at the end so to avoid a bunch of
forward declarations.
---
src/target/feroceon.c | 165 +++-
1 files
Make sure the target is actually halted at the end of the transfer and
confirm from the target's r0 content that the right amount of data was
actually received.
feroceon: tighten error checking in bulk_write
---
src/target/feroceon.c | 19 +++
1 files changed, 15 insertions(+),
.*
+ * Copyright (C) 2008-2009 by Marvell Semiconductors, Inc.
*
* Written by Nicolas Pitre*
* *
* Copyright (C) 2008 by Hongtao Zheng
The SheevaPlug interface is now unusable since rev 2573:
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
Backing out changes from that revision does indeed fix the issue.
So what was the point of that patch?
Nicolas
On Sun, 30 Aug 2009, David Brownell wrote:
> On Saturday 29 August 2009, Duane Ellis wrote:
>
> > Some screens are nice and wide, tiny fonts, mine is not - I have to have
> > larger fonts so I can see.
>
> Yeah, that too. Some peoples' eyes are born weak; other
> people have to age into eyes t
On Mon, 13 Jul 2009, Zach Welch wrote:
> On Wed, 2009-07-08 at 01:02 -0400, Nicolas Pitre wrote:
> > Before, the ./configure --help used to list --enable-parport-ppdev
> > instead of the current --disable-parport-ppdev. The later suggests that
> > parport-ppdev is now set
Before, the ./configure --help used to list --enable-parport-ppdev
instead of the current --disable-parport-ppdev. The later suggests that
parport-ppdev is now set by default when using --enable-parport (which
would be a good thing I think) but this is apparently not the case.
Nicolas
__
ost to this thread once (and for all).
In all honesty, I'm playing devil advocate all along, and prodding for
opinions with a stick. ;-)
> On Mon, 2009-06-15 at 00:28 -0400, Nicolas Pitre wrote:
> [snip]
> > Now... who can make that call? Is there someone with code in
On Mon, 15 Jun 2009, Freddie Chopin wrote:
> Nicolas Pitre pisze:
> > If libftd2xx is not statically
> > linked, or even not distributed along with the compiled OpenOCD binary, then
> > the case against it is highly arguable and far from being a black and white
> > pict
On Mon, 15 Jun 2009, David Brownell wrote:
> No, it's extremely easily defensible. They saw the license was
> GNU GPLv2, and they knew just what that means. It's hardly news
> to anyone ever looks at licenses. There would be no "retroactive
> revocation" going on, to just acknowledge reality by
On Mon, 15 Jun 2009, David Brownell wrote:
> On Monday 15 June 2009, Nicolas Pitre wrote:
> > On Mon, 15 Jun 2009, David Brownell wrote:
> >
> > > On Sunday 14 June 2009, Nicolas Pitre wrote:
> > > > Now... who can make that call? Is there someone with co
On Mon, 15 Jun 2009, David Brownell wrote:
> On Sunday 14 June 2009, Nicolas Pitre wrote:
> > Now... who can make that call? Is there someone with code in OpenOCD
> > who is against such a relicensing?
>
> Not the right process. Every OpenOCD copyright holder must explici
On Sun, 14 Jun 2009, Freddie Chopin wrote:
> (sorry for sending to David only in the first try, this "Reply-To"
> policy is really strange, and the "reasons" just don't convince me...)
>
> In my country such imaginary problems are often described as "a shot in
> one's own foot".
>
> If OpenOCD
On Sun, 14 Jun 2009, Xiaofan Chen wrote:
> On Sun, Jun 14, 2009 at 9:45 AM, Nicolas Pitre wrote:
> > Furthermore, my own testing with both libraries showed libftd2xx
> > marginally faster, and not many times faster as the doc is claiming.
> >
> > OTOH, libftdi
On Sat, 13 Jun 2009, David Brownell wrote:
> It's my understanding that verions of OpenOCD built using
> the "libftd2xx" library (FTDI's binary code) can not be
> redistributed without violating the OpenOCD license (GPL).
>
> http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLIncompatibleLib
On Sat, 30 May 2009, Øyvind Harboe wrote:
> On Fri, May 29, 2009 at 12:14 AM, David Brownell wrote:
> > than just "conform to JTAG spec". No problem when
> > docs are available ... but sometimes they aren't.
>
> XScale is under Marvell NDA for instance :-)
Some of it has been opened up:
htt
On Mon, 1 Jun 2009, Michael Bruck wrote:
> On Mon, Jun 1, 2009 at 4:41 AM, David Brownell wrote:
> > On Sunday 31 May 2009, Michael Bruck wrote:
> >> The 'struct foo_s' syntax is code bloat that obscures the actual
> >> algorithms. 'foo_t' is shorter.
> >
> > Disagree about obscuring. And "short
On Sun, 31 May 2009, David Brownell wrote:
> On Sunday 31 May 2009, Zach Welch wrote:
> > While I think this would help the code and documentation a
> > lot, I would even go further to suggest "s/_s//" from all struct names.
>
> Most certainly. I realize there are coding conventions that
> p
On Sun, 31 May 2009, David Brownell wrote:
> Various updates, mostly small/formatting changes:
>
> * Small content tweaks:
> - Re-title: "OpenOCD User's Guide".
> - For users, URLs for latest doc and SparkFun forum
> - Mention GIT-SVN
You suggest:
git svn clone svn://svn.
Feroceon is unusual and we know it. Stop complaining about that.
diff --git a/src/target/embeddedice.c b/src/target/embeddedice.c
index 31ac0b4..9d2be36 100644
--- a/src/target/embeddedice.c
+++ b/src/target/embeddedice.c
@@ -179,6 +179,13 @@ reg_cache_t* embeddedice_build_reg_cache(target_t *targ
On Mon, 25 May 2009, David Brownell wrote:
> On Monday 25 May 2009, Nicolas Pitre wrote:
> > On Sat, 23 May 2009, David Brownell wrote:
> >
> > > I see messages about needing to increase some GDB timeout/interval. But
> > > that's foolishness, since I'
openocd.texi:12: @include `version.texi': No such file or directory.
openocd.texi:47: warning: undefined flag: EDITION.
openocd.texi:48: warning: undefined flag: VERSION.
openocd.texi:48: warning: undefined flag: UPDATED.
makeinfo: Removing output file `openocd.info' due to errors; use --force to
On Sun, 24 May 2009, Rick Altherr wrote:
>
> On May 24, 2009, at 9:37 PM, Zach Welch wrote:
>
> > On Sun, 2009-05-24 at 21:19 -0700, Rick Altherr wrote:
> > > =On May 24, 2009, at 9:04 PM, Zach Welch wrote:
> > >
> > > > On Sun, 2009-05-24 at 20:51 -0700, David Brownell wrote:
> > > > > On Sund
On Sat, 23 May 2009, David Brownell wrote:
> I see messages about needing to increase some GDB timeout/interval. But
> that's foolishness, since I'm not even working with GDB when they start
> spamming me.
This is indeed really irritating.
What about those messages being displayed only when a g
On Sat, 23 May 2009, Zach Welch wrote:
> On Fri, 2009-05-22 at 20:28 -0700, David Brownell wrote:
> > Update two oddball NAND commands to work with {offset, length}
> > instead of block numbers, matching the other commands as well
> > as usage in U-Boot and the Linux-MTD utilities.
> >
> > Docume
When the CPU is in the WFI state, the JTAG interface simply doesn't
respond at all and initial tap examination simply fails. Let's simply
do it again when we come around to assert nSRST.
diff --git a/src/target/board/sheevaplug.cfg b/src/target/board/sheevaplug.cfg
index 276d6f2..d1a0cce 100644
-
On Fri, 22 May 2009, David Brownell wrote:
> On Friday 22 May 2009, Sergey Lapin wrote:
> > How hard it is po port that to at91sam9260?
>
> Shouldn't be hard to get basic soft-ecc working.
> Sort of like Orion ... I think the fast-download
> code there should be pulled out and made available
> f
1 - 100 of 146 matches
Mail list logo
