You also need to update target/Makefile.am to get the scripts installed.
Committed.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@l
Committed.
Thanks!
--
Ø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/listinfo/openocd
On Fri, Jun 27, 2008 at 1:13 AM, Tim Hudson <[EMAIL PROTECTED]> wrote:
> Øyvind Harboe wrote:
>>> for {set i 0} {$i < 10} {incr i} {openocd "mww [expr $i*4] 0"}
>
> Hooking the command interpreter on a per-line basis isn't a good approach IMHO
The reason for hooking it up to the command line inter
I'm currently using Openocd with luminary cortex-m3 devices, the version I'm
using is the one coming with freeRTOS
(2007-08-17), when I try to use a freshly compiled version I'm not able to make
it working with the same scripts.
Does any one have a sample script working with the latest version
Øyvind Harboe wrote:
>> for {set i 0} {$i < 10} {incr i} {openocd "mww [expr $i*4] 0"}
Hooking the command interpreter on a per-line basis isn't a good approach IMHO.
I think something more along the lines of embedded script usage in web pages
would make more sense:
e.g.
or with tcl:
Scri
the following patch adds the TinCanTools Hammer Module target library entries
Dave Anders
diff -urN trunk/src/target/event/hammer_reset.script
trunk-hammer/src/target/event/hammer_reset.script
--- trunk/src/target/event/hammer_reset.script 1969-12-31 18:00:00.0
-0600
+++ trunk-hammer/s
Hi, all!
Is there some documentation around on making NAND flash work for OpenOCD on
some particular board?
S.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Any objections to committing?
(I don't have hardware to test this...)
--
Ø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.
the follow patch fixes an issue with large block nand flash address where the
beginning of the OOB area is always selected instead of the beginning of a page
when needed.
Dave Anders
diff -urN trunk/src/flash/nand.c trunk-nand/src/flash/nand.c
--- trunk/src/flash/nand.c 2008-06-26 14:34
>
> That's excellent except that I found the default build was 'debug'
> (2.2MB) and I had to add options to make it a 'release' build
> (~700KB).
>
> CFLAGS="-O2 -Wall"
>
The default CFLAGS for the build for autoconf are "-O2 -g"
If you need to remove the debug info, either change the CFLAGS
Hello Tim,
>That's excellent except that I found the default build was 'debug'
>(2.2MB) and I had to add options to make it a 'release' build (~700KB).
>
>CFLAGS="-O2 -Wall"
I think the default is with -O2 too, but the build is with debug info.
You can remove it later by "strip openocd.exe"
All m
Hi Michael,
That's excellent except that I found the default build was 'debug'
(2.2MB) and I had to add options to make it a 'release' build (~700KB).
CFLAGS="-O2 -Wall"
I've been fumbling around for the past six months trying to build a
native Win32 OpenOCD and have even resorted to making a Vi
> At least, I'm still optimistic and happy to hear, that you are considering
> this language for OpenOCD. This would probably increase its acceptance among
> embedded developers. But be prepared, that people may keep asking you, why
> in the hell you are using a new language nobody is familiar with
Hello List,
if you like to build OpenOCD by yourself and do not know
how it will goes, take a look here:
http://forum.sparkfun.com/viewtopic.php?t=11221
Here I have described how to build a FT2232 interface
based on the FT2DXX driver for cygwin and mingw.
Even you will find here the information
Øyvind Harboe wrote:
> How about using Lua for highlevel parts of OpenOCD and
> implement low level fn's in C.
In the Ethernut Project we have a few years of experience with Lua as a
script language for system configuration. The result is not impressive,
which may be caused by
1. Simple, static
"Øyvind Harboe" <[EMAIL PROTECTED]> writes:
>
> I'm leaning towards Lua for an "end user scripting language"
> given the feedback so far.
I'm also in favour of Lua over Tcl (I agree that Tcl is sick).
Jürgen
--
Jürgen Stuber <[EMAIL PROTECTED]>
http://www.jstuber.net/
Loop to fill memory:
> for {set i 0} {$i < 10} {incr i} {openocd "mww [expr $i*4] 0"}
Example of syntax error:
> for {set i 0} {$i < 10} {incr i} {openocd "mww [expr aaa $i*4] 0"}
Runtime error, file "?", line 1:
Syntax error in expression
Next step is to show how an internal command of Op
Sorrym forgot to Cc list.
-- Forwarded message --
From: Sergey Lapin <[EMAIL PROTECTED]>
Date: Wed, Jun 25, 2008 at 6:39 PM
Subject: Re: [Openocd-development] Implementing OpenOCD in Lua & C
To: Øyvind Harboe <[EMAIL PROTECTED]>
On Wed, Jun 25, 2008 at 5:55 PM, Øyvind Harboe <[E
I integrated Jim Tcl in OpenOCD so as to enable some experimentation
and to gauge interest.
Usage:
- type Tcl on command line interpreter
> expr 1+2
3
- invoke an OpenOCD command from the Tcl interpreter.
> openocd "flash bank [expr 0"
output from executing "flash bank 0"
Implementation
19 matches
Mail list logo
