On 10 June 2011 13:14, Spencer Oliver s...@spen-soft.co.uk wrote:
On Jun 10, 2011 11:53 AM, Mahavir Jain mj...@marvell.com wrote:
Hi Spencer,
Did you get time to perform additional tests? What would be fix for this
issue (disabling working areas makes entire operation really slow)?
Hi,
When performing a erase_check on a cortex we gets lots of
Error: 36989 4463475 target.c:1190 target_alloc_working_area_try(): BUG:
code tried to allocate unaligned number of bytes (0x000e), padding
The reason being that the erase_check_code for armv7 is only 14bytes, now i
would not
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 appreciated!
You can read up on the scripts to produce
Hello
Attached is an implementation of a remote bitbang jtag driver which sends
ascii encoded bitbang commands over unix sockets or TCP to another process.
This has been very useful to us, and we would like to contribute it to
openocd. Will you accept this contribution?
Thanks,
Very cool!
I think I'd like to see error propagation on *all* socket
calls, but otherwise I don't have any objections.
Would you be willing to add such error propagation?
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
On Wed, Jun 15, 2011 at 3: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
Good to hear! I was planing to make 0.4.1 as there are s many
On Wed, Jun 15, 2011 at 6:04 PM, Uhler, Richard ruh...@qualcomm.com wrote:
This has been very useful to us
Hi Richard,
what is the exact benefit of this driver ? I.e. when it should be used and
for what purposes - can you give me some example ?
Best regards,
Drasko
The swd is some time away from being merged with master,
so I wouldn't want to see it in the next release of openocd, unless
the release drags out.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
The main thing that needs fixing is the issue with how to release the Jim
tcl lib.
Currently a make distcheck will fail due the Jim lib.
Previously Jim was integrated and this made releases simpler - now we have
to decide whether to leave it seperate or release the Jim src with openocd
release
On Jun 15, 2011 8:08 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
On Wed, Jun 15, 2011 at 9:01 PM, Spencer Oliver s...@spen-soft.co.uk
wrote:
The main thing that needs fixing is the issue with how to release the
Jim
tcl lib.
Currently a make distcheck will fail due the Jim lib.
I don't understand. Can you clarify what you mean by error propagation and
which socket calls do or don't have it? If it's just a matter of changing some
code in the remote_bitbang driver I would be happy to add this error
propagation.
Richard
On Wed, Jun 15, 2011 at 5:34 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
The swd is some time away from being merged with master,
so I wouldn't want to see it in the next release of openocd, unless
the release drags out.
I would suggest 0.4.1 for the current code freeze, as there should
On Wed, Jun 15, 2011 at 10:51 PM, Uhler, Richard ruh...@qualcomm.com wrote:
I don't understand. Can you clarify what you mean by error
propagation and which socket calls do or don't have it? If it'
s just a matter of changing some code in the remote_bitbang
driver I would be happy to add this
On Wed, Jun 15, 2011 at 10:55 PM, Tomek CEDRO tomek.ce...@gmail.com wrote:
On Wed, Jun 15, 2011 at 5:34 PM, Øyvind Harboe oyvind.har...@zylin.com
wrote:
The swd is some time away from being merged with master,
so I wouldn't want to see it in the next release of openocd, unless
the release
Hello Spencer :-)
I would use git submodule and simply include JimTCL with OpenOCD build
binary. This would save lots of problems and produce common
distribution. Anyone who want to use external library can build
his/her own binary. Ofcourse there is a situation to solve what to to
when JimTCL is
Hello Richard,
Seems to be nice feature, however:
It should be somehow related with interface driver bitbang..?
It should be possible to enabled/disabled by configure script.
Bets regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Wed, Jun 15, 2011 at 8:57 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
0.4.1 implies that it is a variant of 0.4. What we have now is *completely*
different from 0.4, so 0.5.0 is better
Yeah, isn't current HEAD somehow development/bugfix of 0.4.0? Are
there any totally new
On Wed, Jun 15, 2011 at 11:16 PM, Tomek CEDRO tomek.ce...@gmail.com wrote:
On Wed, Jun 15, 2011 at 8:57 PM, Øyvind Harboe oyvind.har...@zylin.com
wrote:
0.4.1 implies that it is a variant of 0.4. What we have now is *completely*
different from 0.4, so 0.5.0 is better
Yeah, isn't current
I think we should stick to distributing source packages only.
For the source package, we can include the version of Jim Tcl we
tested with.
If someone wants something else, they can start with cloning
the openocd repository and checking out the release tag?
--
Øyvind Harboe
Can Zylin
but are these any major changes or simply improvements? also if we use
A.B.C nomenclature or A.B?
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
On Wed, Jun 15, 2011 at 9:30 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I think we should stick to distributing source packages only.
For the source package, we can include the version of Jim Tcl we
tested with.
If someone wants something else, they can start with cloning
the openocd
On Jun 15, 2011 10:30 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I think we should stick to distributing source packages only.
That's my plan
- even that is not easy as Jim does not use autoconf etc.
Cheers
Spen
___
Openocd-development mailing
Attached is a patch which adds board support for the Olimex STM32-P107
and STM32-H107 connectivity line development boards.
The only difference between this board file and the
olimex_stm32_h103.cfg file is that the WORKSPACE size is larger --
these devices have 64kb of ram instead of 20kb of ram.
So is there anyone else wanting to release 0.4.1 (or any other) from
the current source tree?? There were so many people interested...
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
Openocd-development mailing list
On Jun 15, 2011 11:40 PM, Tomek CEDRO tomek.ce...@gmail.com wrote:
So is there anyone else wanting to release 0.4.1 (or any other) from
the current source tree?? There were so many people interested...
I am all for a 0.50 release.
As mentioned need to fix make dist first.
Spen
On Wed, Jun 15, 2011 at 10:56 PM, Spencer Oliver s...@spen-soft.co.uk wrote:
I am all for a 0.50 release.
As mentioned need to fix make dist first.
Spen
gjt :-) if there are others eager to do this then im backing off to
work on swd :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Wed, Jun 15, 2011 at 11:06 PM, Rodrigo Rosa rodrigorosa...@gmail.com wrote:
i'm not sure i'm getting this right, i think i know very little about
how this stuff works...
i had modified ft2232.c
in ft2232_execute_queue, instead of doing layout-blink was using some
mpsse commands to
On 16/06/2011, at 7:49 AM, Spencer Oliver wrote:
On Jun 15, 2011 10:30 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I think we should stick to distributing source packages only.
That's my plan
- even that is not easy as Jim does not use autoconf etc.
That sounds like an easy
28 matches
Mail list logo
