Re: [Openocd-development] openocd scripting

2009-10-24 Thread David Brownell
On Saturday 24 October 2009, Timo Boettcher wrote: > openocd -f openocd/openocd.cfg -f openocd/olimex-arm-usb-ocd.cfg -f > openocd/openocd-sam7s256.cfg -c "mt_flash_bin glow_flash.bin" > I get: > > = begin openocd output = > Warn : use 'sam7se256.cpu' as target identifier, not '0' > Unkno

[Openocd-development] openocd scripting

2009-10-24 Thread Timo Boettcher
Hi! I am trying to configure openocd to run it fom my Makefile. Running it manually works: = begin openocd session = % nc localhost Open On-Chip Debugger > halt halt target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x205

Re: [Openocd-development] OpenOCD scripting API - no over-the-wire format at all

2008-07-12 Thread Duane Ellis
Øyvind Harboe wrote: > You can call that a defined over the wire protocol if you want to. > > But this is all further down the line. Then - later we hash out the wire line protocol. I have always been talking about the narrow subject of "the wireline protocol". I'm ok with that. -Duane. ___

Re: [Openocd-development] OpenOCD scripting API - no over-the-wire format at all

2008-07-12 Thread Øyvind Harboe
On Sat, Jul 12, 2008 at 2:06 PM, Duane Ellis <[EMAIL PROTECTED]> wrote: > There is always an "over the wire protocol" you can dance around the issue > all you want. I intend to modify the tcl server to let the *client* decide what to do with a connection, the data coming in and what data to send b

Re: [Openocd-development] OpenOCD scripting API - no over-the-wire format at all

2008-07-12 Thread Duane Ellis
There is always an "over the wire protocol" you can dance around the issue all you want. As you say: >> The client *decides* what code to run on the server(e.g. on >> the OpenOCD command line + injects scriptlets, etc.) Thus the defined over the wire protocol is: (A) the invoking of e

[Openocd-development] OpenOCD scripting API - no over-the-wire format at all

2008-07-12 Thread Øyvind Harboe
It just occurred to me: Even if we allow TCP/IP connections to talk to the OpenOCD, that doesn't make the format on the wire the API. A HTTP server is a server where the client is under no circumstances allowed to execute code on the server. With OpenOCD this is not the case. The client *decides

Re: [Openocd-development] openocd scripting challenge

2008-06-30 Thread Pavel Chromy
Øyvind Harboe wrote: >> Øyvind Harboe wrote: >>> Can anyone come up with a good example of how scripting >>> could be useful in configuration scripts? >> just as was mentioned already - mass production flash programming ant >> testing, >> but this is pretty important task in my point of view. >

Re: [Openocd-development] openocd scripting challenge

2008-06-29 Thread Øyvind Harboe
On Mon, Jun 30, 2008 at 8:05 AM, Pavel Chromy <[EMAIL PROTECTED]> wrote: > Hello, > > Øyvind Harboe wrote: >> Can anyone come up with a good example of how scripting >> could be useful in configuration scripts? > > just as was mentioned already - mass production flash programming ant testing, > but

Re: [Openocd-development] openocd scripting challenge

2008-06-29 Thread Pavel Chromy
Hello, Øyvind Harboe wrote: > Can anyone come up with a good example of how scripting > could be useful in configuration scripts? just as was mentioned already - mass production flash programming ant testing, but this is pretty important task in my point of view. Pavel __

[Openocd-development] openocd scripting challenge

2008-06-27 Thread Øyvind Harboe
Can anyone come up with a good example of how scripting could be useful in configuration scripts? -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-d