Please try with the latest master branch.
Thanks!
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
_
On Thu, Nov 18, 2010 at 4:43 PM, Peter Stuge wrote:
> Andrew Leech wrote:
>> > (A note that you can send patches easily by first committing and then
>> > using the git send-email command.)
>>
>> Ok I'm still pretty new to git, so by committing it just adds changes
>> to the local repository not th
Andrew Leech wrote:
> > (A note that you can send patches easily by first committing and then
> > using the git send-email command.)
>
> Ok I'm still pretty new to git, so by committing it just adds changes
> to the local repository not the mainline one?
Exactly. Every git working copy is a fully
Hi, with openocd 0.4, I use the "bp 0x84 4" to set a breakpoint , then
"resume", but the bp effects only one time:
the target can be breaked only one time.
Use the "bp 0x84 4 hw", and it effects all time.
With gdb, both "soft breakpoint" and "hard point" work.
I want to use the teln
On Thu, Nov 18, 2010 at 2:29 AM, Peter Stuge wrote:
> Andrew Leech wrote:
>>
>> I'll look into that, I've not used snprintf so don't really know the
>> difference. It's obviously only a google away. I'm just used to
>> sprintf from embedded devices when you often don't have a choice of
>> using a
Merged.
Thanks!
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-d
Andrew Leech wrote:
> I actually would normally have used a basic static buffer exactly
> how you suggest, it's only that the malloc'd svf_command_buffer is
> used later for running commands I thought it'd make sense to reuse
> it
That makes sense.
> rather than adding a static ram usage to the
On 16/11/2010 22:15, Peter Stuge wrote:
Spencer Oliver wrote:
Updated patch that removed the HAVE_NO_AUTOCONF hack.
This has an updated jimtcl version.
Well done!
+if test "$use_internal_jimtcl" = yes; then
+ if test -d "$srcdir/jimtcl"; then
This doesn't work because the jimtcl exists a
>/ As I suspected. This is fixed in:
/>/
/>/
http://repo.or.cz/w/jimtcl.git/commit/5a9c9cdc1a0add1d0e6e63e64d5d7d7febc6d749
/>/
/
cheers - i will respin the patch against latest jimtcl then.
>>/ we can work around this many ways depending on how much/little work you
fancy doing :)
/>/
/>/ I
