On 13:25 Sat 18 Apr , Jean-Michel Hautbois wrote:
Hi everybody,
I am new to this mailing list, and new with using openOCD.
I have a Tribbox (STi7109 based board), and I wish to use a JTAGkey
from amontec.
I can't find any file relative to this board in the source code. Is
there any way
it will allow to be at the highest speed of the jlink without touching the
board or cpu config
tested on sam-ice v5 and at91rm9200-ek
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
.barebox_initcalls, size 0x80 lma 0x21f3b620
Start address 0x21f0, load size 243360
Transfer rate: 26 KB/sec, 13520 bytes/write.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/board
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
doc/openocd.texi |4 ++--
src/jtag/drivers/jlink.c | 16 +---
2 files changed, 15 insertions(+), 5 deletions(-)
diff --git a/doc/openocd.texi b/doc/openocd.texi
index 7772d78..5b12386 100644
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
src/jtag/drivers/jlink.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/jtag/drivers/jlink.c b/src/jtag/drivers/jlink.c
index f1b9711..b182b61 100644
--- a/src/jtag/drivers/jlink.c
+++ b
this will allow us to use multiple jlink at the same time as when
the USB-Address is specified the PID change from 0x0101 to
(0x101 + usb_adress)
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
doc/openocd.texi |2 ++
src/jtag/drivers/jlink.c | 27
The default pid of the segger is 0x0101
But when you change the USB Address it will also
pid = ( usb_address 0x4) ? 0x0101 : (0x101 + usb_address)
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
src/jtag/drivers/jlink.c | 10 --
1 files changed, 8 insertions
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/target/at91sam9263.cfg | 20
1 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 tcl
all at91sam9 are nearly the same except sram and soc name
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/board/at91sam9g20-ek.cfg | 28 +--
tcl
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/target/at91sam9261.cfg | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
create mode 100644 tcl/target
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/target/at91sam9260.cfg |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/tcl/target/at91sam9260.cfg b
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/target/at91sam9g45.cfg | 16
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 tcl/target
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/target/at91sam9g10.cfg | 16
1 files changed, 16 insertions(+), 0 deletions(-)
create mode 100644 tcl/target
Hi,
I'm currently adding the support of a third party JTAG based on a ftdi
FT4232
but on my devices the TDO is connected to ADBUS1 and TDI ADBUS2
how can I specify this in the drivers?
Best Regards,
J.
___
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
doc/openocd.texi |2 +
src/jtag/drivers/jlink.c | 102 +-
2 files changed, 103
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
doc/openocd.texi | 18 ++
src/jtag/drivers/jlink.c | 397 ++
2 files changed
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
src/jtag/drivers/jlink.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/src/jtag/drivers
as said in the datasheet Section 3.3.2 Organization of buffers
All buffers are big enough to hold 2 KByte of data.
this will double the speed of download
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/board/at91sam9261-ek.cfg | 63 ++
1 files changed, 63 insertions(+), 0 deletions
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/chip/atmel/at91/at91sam9263.cfg| 113
tcl/chip/atmel/at91/at91sam9263_matrix.cfg | 112
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/chip/atmel/at91/at91sam9261.cfg| 90
tcl/chip/atmel/at91/at91sam9261_matrix.cfg | 46
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
tcl/board/at91sam9263-ek.cfg | 63 ++
1 files changed, 63 insertions(+), 0 deletions
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
src/jtag/drivers/jlink.c | 14 --
1 files changed, 4 insertions(+), 10 deletions(-)
diff --git a/src/jtag/drivers
for
- pio
- pmc
- rstc
- wdt
- sdramc
- smc
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Patrice Vilchez patrice.vilc...@atmel.com
---
Hi,
please apply this one before
Best Regards,
J.
tcl/chip/atmel/at91
Please revert this break the rm9200-ek with jlink
where we do have a adapter_khz specified in the init script
Best Regards,
J.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
On 14:26 Tue 03 May , Øyvind Harboe wrote:
Please be more specific. We intend to move forward on this one and
we are interested in hearing what problems you are seeing.
This is an important and somewhat tricky problem that we intend
to put to bet once and for all, and knew that there
On 15:52 Tue 03 May , Øyvind Harboe wrote:
The error message is working as intended, near as I can tell.
You have to specify the JTAG communication frequency, there
no longer is any concept of a default frequency.
These scripts are missing a statement to set the JTAG communication
On 04:17 Wed 04 May , Øyvind Harboe wrote:
why do you want to set one the adapter is in auto adaptive mode by default
no need to set any speed
OpenOCD doesn't have an auto-adaptive mode, so I guess you need
to explain what you are referring to.
on J-Link
if you set the speed to
Best regards
Jonas Hörberg
diff --git a/tcl/board/at91rm9200-ek.cfg b/tcl/board/at91rm9200-ek.cfg
index 07a006b..cf0fb7a 100644
--- a/tcl/board/at91rm9200-ek.cfg
+++ b/tcl/board/at91rm9200-ek.cfg
@@ -18,6 +18,8 @@ $_TARGETNAME configure -event reset-init {
at91rm9200_ek_init }
set
On 06:58 Fri 06 May , Øyvind Harboe wrote:
+# The chip may run @ 32khz, so set a really low JTAG speed
+adapter_khz 8
this is the wrong place it's not board specific but soc specific
tcl/target/at91rm9200.cfg
Perhaps jtag_rclk 8 should be used, i.e. use RCLK if it is supported
On 09:17 Thu 19 May , Lingfeng Xiong wrote:
hi there,
I am trying to debug u-boot on samsung s3c2410 board with OpenOCD and
Eclipse. The initialization script is listed below:
[code]
source [find jlink.cfg]
jtag_khz 500
jtag_nsrst_delay 100
jtag_ntrst_delay 100
source [find
On 14:06 Sun 22 May , Bear wrote:
hi,
I am using a old version of u-boot. It seems like 1.3.2. This
version of u-boot has been modified to suit my special board which
has no NOR flash.
As far as I remember I had the support of the dcc in U-Boot much later
Do you use a mini2440?
BTW: I
On 11:22 Fri 27 May , Paul Claessen wrote:
I built OpenOCD 0.5.0-dev-00882 the other day with Jlink support enabled.
It built okay, but when I tried to use it I got some errors (See below for
error log). They seem to hint at USB endpoint problems (but I could be
totally
On 17:05 Wed 01 Jun , Øyvind Harboe wrote:
How about this?
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash
On 10:45 Fri 03 Jun , Tormod Volden wrote:
On Thu, Jun 2, 2011 at 2:32 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
normaly in shell we so
if [ x$1 = xnosubmodule ]; then
to compatible with old shell too
Yes, I have seen this construct a lot in old scripts, but it reduces
On 15:25 Tue 07 Jun , Laurent Gauch wrote:
/If our ft2232.c patches are not merged quickly, Amontec Team will certainly
// come with a new specific jtagkey.c API driver instead of the ft2232.c
JTAG
// driver.
// The advantage with a specific Amontec JTAGkey API driver in openocd,
On 08:42 Thu 09 Jun , Laurent Gauch wrote:
On 15:25 Tue 07 Jun , Laurent Gauch wrote:
/
// /If our ft2232.c patches are not merged quickly, Amontec Team will
certainly
// // come with a new specific jtagkey.c API driver instead of the
ft2232.c JTAG
// // driver.
// // The
On 18:05 Wed 15 Jun , Øyvind Harboe wrote:
On Wed, Jun 15, 2011 at 5:33 PM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 23:04 Tue 07 Jun , Ųyvind Harboe wrote:
Nobody has stepped up to do the work of being a release
manager.
If no-one do it I'll
Much
Hi all,
I'd like to propose the following release cycle
For the people familiar with Linux kernel its basically the same
2 development window:
merge window
fix window
We will get 2 weeks of merge window where any code can be merge in the
On 08:17 Fri 17 Jun , Øyvind Harboe wrote:
Some questions/comments:
- if we look at the current way we work with OpenOCD, we just
commit stuff to the master branch without regards to a release.
I would like this to continue in the same manner, which I don't
think is in conflict with
On 08:17 Fri 17 Jun , Øyvind Harboe wrote:
Some questions/comments:
- if we look at the current way we work with OpenOCD, we just
commit stuff to the master branch without regards to a release.
I would like this to continue in the same manner, which I don't
think is in conflict with
On 08:35 Fri 17 Jun , Jean-Christophe PLAGNIOL-VILLARD wrote:
On 08:17 Fri 17 Jun , Øyvind Harboe wrote:
Some questions/comments:
- if we look at the current way we work with OpenOCD, we just
commit stuff to the master branch without regards to a release.
I would like
On 09:03 Fri 17 Jun , Øyvind Harboe wrote:
On Fri, Jun 17, 2011 at 8:25 AM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 08:17 Fri 17 Jun , Ųyvind Harboe wrote:
Some questions/comments:
- if we look at the current way we work with OpenOCD, we just
commit
On 09:57 Fri 17 Jun , Øyvind Harboe wrote:
so we do two tree the next tree (yours) and the release tree
if multiple maintainer eed to merge code together they will send it the the
RM
in his next branch
the description will be what must follow the release tree for the other tree
On 12:32 Fri 17 Jun , Øyvind Harboe wrote:
if possible a MAINTAINER file as done in the linux kernel
Do you want to write up the definitions and procedures in a patch for
MAINTAINER file and then I can commit it to OpenOCD master branch
before we start this cycle?
I think it will be
On 07:30 Tue 21 Jun , Øyvind Harboe wrote:
2011/6/21 Jon Povey jon.po...@racelogic.co.uk:
Øyvind Harboe wrote:
I am struggling a bit following the above, but I think we agree:
- development goes on in master like it always has done
- you create a fork at the openocd mirror and
On 19:04 Tue 28 Jun , Øyvind Harboe wrote:
The best way to do is to choose one git tree as the master git
then each maintainer will have their one git tree too
where they manage it how they want.
All the maintainers have their own repositories and forks at the git
mirror, but we also
On 12:02 Tue 28 Jun , Paul Claessen wrote:
Greetings ...
Question for the J-link developer (Jean-Christophe?), or anyone who
knows the answer:
Is there a way to hookup and use multiple Segger J-Links devices
with OpenOCD?
Yes you can I use it everyday and I implement it in openOCD
On 19:39 Tue 28 Jun , Øyvind Harboe wrote:
but now all the maintainer will have their own fork/repository
as done in the kernel
Right. And you will pull merge from us and push the result to the
master branch?
exactly
Best Regards,
J.
___
On 19:15 Tue 28 Jun , Øyvind Harboe wrote:
On Tue, Jun 28, 2011 at 6:58 PM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 19:04 Tue 28 Jun , Øyvind Harboe wrote:
The best way to do is to choose one git tree as the master git
then each maintainer will have
On 19:56 Tue 28 Jun , Øyvind Harboe wrote:
On Tue, Jun 28, 2011 at 7:30 PM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 19:39 Tue 28 Jun , Øyvind Harboe wrote:
but now all the maintainer will have their own fork/repository
as done in the kernel
Right
On 20:20 Tue 28 Jun , Øyvind Harboe wrote:
Where is the plan?
I'll write the patch when we have finish the discussion about the workflow
now we just close the merge window
Could you create a mirror at the openocd git mirror?
We've done that so far and it makes it easier to find stuff...
On 08:34 Wed 29 Jun , Øyvind Harboe wrote:
So when I send a pull request to you from my repository, would
you rebase or merge?
merge never rebase the master repo
We now have a nice linear history, which gives me a warm fuzzy
feeling for a simple project like OpenOCD
What would a
On 07:24 Wed 29 Jun , Øyvind Harboe wrote:
On Wed, Jun 29, 2011 at 2:30 AM, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
On 20:20 Tue 28 Jun , Øyvind Harboe wrote:
Where is the plan?
I'll write the patch when we have finish the discussion about the workflow
now
On 08:13 Wed 29 Jun , Øyvind Harboe wrote:
On Wed, Jun 29, 2011 at 7:43 AM, simon qian simonqian.open...@gmail.com
wrote:
Is it possible to update Versaloon driver in 0.5.0 release?
Mail me if there is any problem with the driver patch.
I don't have a problem with applying this patch
On 07:21 Wed 29 Jun , Øyvind Harboe wrote:
I'd have some reservations about only one person having write
access, but not particularly the way of working. Call me old fashioned.
Does not mean you do not have the write access does just mean you dont use
it
As example if the release
On 08:23 Thu 30 Jun , Øyvind Harboe wrote:
Please give a warm welcome to Jean-Christophe as the release
manager.
He will be laying down some new ground rules for how we
treat the git repository and how we handle the release process.
As well as releases, we're looking forward to more
On 16:35 Thu 30 Jun , Øyvind Harboe wrote:
It will be nice to have a list of Maintainer and their role to specify which
part of OpenOCD they take care of
Admin / maintainer:
Spencer Oliver s...@spen-soft.co.uk,
Øyvind Harboe oyvind.har...@zylin.com,
Maintainer: Peter Stuge
On 07:28 Fri 01 Jul , Øyvind Harboe wrote:
Is there a GPL wiz in the house?
Can we accept anonymous contributions just like that?
I know there are anonymous contributions in Linux.
My Point will be simple each must have the SOB
which imply that the author agree that his patch is under
On 11:17 Mon 04 Jul , Luca Bruno wrote:
Jean-Christophe PLAGNIOL-VILLARD scrisse:
I'll send a patch to sumurize all our discussion about the new release
process this WE
It will be nice to have a list of Maintainer and their role to
specify which part of OpenOCD they take care
Hi,
Today is RC day
Here is OpenOCD v0.5.0-rc2
This time on the official git tree
The following changes since commit ff640f197a9a343b2f3ed10e9174e35282334e8c:
cortex_m3: add auto maskisr (2011-06-28 14:16:48 +0100)
are available in the git repository at:
On 20:05 Mon 04 Jul , Freddie Chopin wrote:
On 2011-07-04 16:11, Jean-Christophe PLAGNIOL-VILLARD wrote:
I'll prepare the tarball on sf.net
A tarball would be highly appreciated (; Drop us a line on the list
when it will be available! (;
for rc I think a tarball is not needed as we have
On 23:05 Wed 06 Jul , Xiaofan Chen wrote:
On Wed, Jul 6, 2011 at 10:02 PM, Eric Wetzel thewet...@gmail.com wrote:
This built cleanly, and I got an openocd.exe that doesn't segfault
immediately and ldd says doesn't depend on cygwin1.dll. Those seem
like positive things. The trouble
On 09:30 Sun 10 Jul , Xiaofan Chen wrote:
On Sun, Jul 10, 2011 at 9:11 AM, li...@neuronenwerk.de wrote:
Hi list,
I've been trying for some days to get the Segger JLink EDU
version going with OpenOCD on Windows 7 32 bit. As the JLink,
OpenOCD and LibUSB might have be the reason for
On 16:59 Sun 10 Jul , Øyvind Harboe wrote:
On the subject of tarballs for release candidates. I think David
Brownell and Zach Welch used to do this.
At least I think you presented some evidence that perhaps at least
the *first* rc should be a tarball so as to catch any problems
we
On 15:20 Sun 10 Jul , Tomek CEDRO wrote:
On Sun, Jul 10, 2011 at 2:41 PM, Luca Bruno lu...@debian.org wrote:
As a sidenote, publishing tarball for -rc helps testing in conditions
similar to the final one, avoiding late bugs introduced by autotools
packaging or similar.
Totally agree
On 19:43 Sun 10 Jul , li...@neuronenwerk.de wrote:
On Sun, 10 14:38 , Jean-Christophe PLAGNIOL-VILLARD wrote:
On 09:30 Sun 10 Jul , Xiaofan Chen wrote:
On Sun, Jul 10, 2011 at 9:11 AM, li...@neuronenwerk.de wrote:
Hi list,
... snip ...
The results as of now
On 09:22 Mon 11 Jul , Spencer Oliver wrote:
On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
plagn...@jcrosoft.com wrote:
Totally agree on this - FreeBSD ports use automatic package download
and extraction mechanism, so having tarball for RC2 would be great!
Please let me know
On 08:56 Fri 05 Aug , Øyvind Harboe wrote:
When I run git describe now I get v0.4.0-973-g0d7a948 rather than
a v0.5.0-rc2-.
Is that intentional?
I think it's nice that we stick to v0.4.0- until v0.5.0- goes out
of the door.
I have no particular opinion, except it should
On 09:18 Tue 09 Aug , Øyvind Harboe wrote:
Hi Jean-Christophe,
thank you so much for your work here!
I'm looking forward to hear feedback on this release.
We're on the right track here I think with a couple of releases
a year!
When will the merge window open?
already open
The
On 07:50 Tue 09 Aug , Tomek CEDRO wrote:
Ugh, why this is a release not RC3? We did not test RC to have go for
a release... are we supposed to test on a release? :\
there was no patch during day so as I said no rc
we get more than 4weeks of fix windows it's enough
If some bug are found on
tested in buildroot
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
configure.in |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/configure.in b/configure.in
index dfa1e8f..cfe2218 100644
--- a/configure.in
+++ b/configure.in
@@ -1046,8
On 23:15 Tue 09 Aug , Øyvind Harboe wrote:
Any objections?
I tried the command line below and it worked perfectly! :-)
git checkout origin/master
git pull --rebase http://repo.or.cz/r/openocd/andreasf.git async_algo
normaly it's, we do not rebase the code
git merge
On 16:46 Tue 09 Aug , Rodrigo Rosa wrote:
hi
first pull request attempt
is there a HACKING doc for this procedure?
commands i used to try this out were
git remote add dsp5680xx git://repo.or.cz/openocd/dsp568013.git
git fetch dsp5680xx
git checkout -b merge_tmp
git merge
Hi,
in the kernel and barebox we avoid as much as possible the rebase
as you loose information when you do so.
When you rebase you do not known against which commit the current
pull request was tested
This histary is important specially when you apply
On 15:20 Wed 10 Aug , Øyvind Harboe wrote:
I think it's very reasonable to require any pull request to apply
cleanly to current tree.
Say we have 2 outstanding pull requests, both impeccable.
Then when I pull to push to the repository, then without rebasing on
my end I will not get
On 19:35 Tue 09 Aug , Jean-Christophe PLAGNIOL-VILLARD wrote:
tested in buildroot
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
ok for everyone?
if yes I'll prepare a 0.5.1 release as we can not cross compile openocd under
buildroot without it
Best Regards,
J
On 18:56 Thu 11 Aug , Luca BRUNO wrote:
Jean-Christophe PLAGNIOL-VILLARD scrisse:
HI,
I finally get the time to generate the release
Sorry for the delay I was busy on the kernel and barebox
merge window
The tarbal are available at
https://sourceforge.net
On 12:04 Sat 13 Aug , Carlson Gary wrote:
Hi Eric,
I have worked a little on the jlink stuff in the past and fixed a few
problems with OpenOCD. I have a new project that is going to force me to
buy an unrestricted Segger very shortly since my current jlink dongles are
Atmel-only
On 19:35 Tue 09 Aug , Jean-Christophe PLAGNIOL-VILLARD wrote:
tested in buildroot
any comments?
Best Regards,
J.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
---
configure.in |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git
Hi,
this one could go on the bug fix release
Best Regards,
J.
On 21:22 Mon 22 Aug , Evan Hunter wrote:
Hi All,
Attached are two patches that fix bugs that I've found in FreeRTOS thread
awareness.
Regards,
Evan Hunter
On 19:54 Tue 23 Aug , Øyvind Harboe wrote:
Do we need a bugfix release?
yes I've a bug on the usb in cross comp when integrate openocd in buildroot
so I'll prepare a bugfix release within 1 or 2weeks
When is the next release?
I'm traveling right now so give me few days to prepare the next
On 08:12 Thu 25 Aug , Øyvind Harboe wrote:
Hi,
is anyone out there working on something that they would like
to see in the next release?
I know Tomek has been working on SWD. Here we need resources
to review, give feedback and look into what it would take to bring
this to a state
On 16:52 Thu 25 Aug , Xiaofan Chen wrote:
On Fri, Aug 19, 2011 at 9:03 PM, Antonio Borneo
borneo.anto...@gmail.com wrote:
On Fri, Aug 19, 2011 at 6:36 PM, Xiaofan Chen xiaof...@gmail.com wrote:
[...]
Thanks a lot for the updates. Yes I can confirm that V4.33h beta firmware
fixed the
Hi,
personnally I'd like we use the same coding style as the kernel
in the kernel anre barebox we use checkpatch to check the patch coding
style
Best Regards,
J.
On 19:40 Sat 27 Aug , Øyvind Harboe wrote:
As a maintainer I'm interested in this subject from the point
Hi,
I'll try on my chip at home
Best Regards,
J.
On 10:19 Wed 21 Sep , Peter Tympanick wrote:
Does anyone know if users of OpenOCD can access the ETM Regisiters?
Peter Tympanick
Product Manager
Ultimate Solutions, Inc.
Hi,
how about using patchwoek simply as done for the kernel ML?
Best Regards,
J.
On 13:40 Tue 11 Oct , Spencer Oliver wrote:
Hi,
We are now testing Gerrit for use within OpenOCD.
A Gerrit server has been setup at the following url:
http://openocd.zylin.com/
To keep loading
On 19:31 Wed 12 Oct , Peter Stuge wrote:
Jean-Christophe PLAGNIOL-VILLARD wrote:
how about using patchwoek simply as done for the kernel ML?
One significant benefit of Gerrit is that it integrates really well
with git. Gerrit takes input from git, and output from Gerrit goes to
git
88 matches
Mail list logo
