Re: [OpenOCD-devel] Introduction to Cortex Serial Wire Debugging

2012-11-26 Thread CeDeROM
On Mon, Nov 26, 2012 at 9:15 PM, Spencer Oliver wrote: > A bit of bedtime reading. > http://www.lpcware.com/content/blog/introduction-cortex-serial-wire-debugging-part-one http://stm32primer2swd.sf.net http://libswd.sf.net http://repo.or.cz/w/openocd/libswd.git :-) -- CeDeROM, SQ7MHZ, http://w

Re: [OpenOCD-devel] Introduction

2012-05-26 Thread Tomek CEDRO
Removing TCL will also break lots of code, configurations and existing commandline, also make srtipt extensions impossible. There is no alternative to TCL from what I remember and there has been a discussion about that (i.e. to replace TCL with Python etc), so I also dont understand why TCL should

Re: [OpenOCD-devel] Introduction

2012-05-26 Thread Peter Stuge
Akos Vandra wrote: > I understand your point of view, however there is no real alternative > to it at the moment, right? The only alternative would be to build your stuff into OpenOCD. I don't suggest that I want this, but it would work. > I mean is there another working way to "remote control"

Re: [OpenOCD-devel] Introduction

2012-05-26 Thread Akos Vandra
On 26 May 2012 20:39, Peter Stuge wrote: > Akos Vandra wrote: >> > a protocol is also *not* the same thing as a programming language. >> >> Please explain what is the problem with TCL? It does the job, it >> seems quite easy to learn, and it's extensible... > > I'd really like to get rid of the ji

Re: [OpenOCD-devel] Introduction

2012-05-26 Thread Peter Stuge
Akos Vandra wrote: > > a protocol is also *not* the same thing as a programming language. > > Please explain what is the problem with TCL? It does the job, it > seems quite easy to learn, and it's extensible... I'd really like to get rid of the jimtcl dependency, and much rather sooner than later

Re: [OpenOCD-devel] Introduction

2012-05-26 Thread Akos Vandra
On 26 May 2012 00:03, Peter Stuge wrote: > Akos Vandra wrote: >> >> I intend to use the TCL server >> > >> > Why? >> >> Because I need the GDB server port available for debugging, and the >> scripting possibilities of TCL are very inviting. >> Also it's simple and neat. Wasn't this kind of thing t

Re: [OpenOCD-devel] Introduction

2012-05-25 Thread Peter Stuge
Akos Vandra wrote: > >> I intend to use the TCL server > > > > Why? > > Because I need the GDB server port available for debugging, and the > scripting possibilities of TCL are very inviting. > Also it's simple and neat. Wasn't this kind of thing the exact purpose > of the TCL interface? Probably

Re: [OpenOCD-devel] Introduction

2012-05-25 Thread Akos Vandra
On 25 May 2012 10:29, Peter Stuge wrote: > Akos Vandra wrote: >> I intend to use the TCL server > > Why? > Because I need the GDB server port available for debugging, and the scripting possibilities of TCL are very inviting. Also it's simple and neat. Wasn't this kind of thing the exact purpose o

Re: [OpenOCD-devel] Introduction

2012-05-25 Thread Peter Stuge
Akos Vandra wrote: > I intend to use the TCL server Why? > I have little to no experience with gerrit, jenkis, and git, No need to repeat this over and over. Just start using git and as I have now told you at least three times please just ask if there are any questions. //Peter -

Re: [OpenOCD-devel] Introduction

2012-05-24 Thread Bill Traynor
On Thu, May 24, 2012 at 8:24 PM, Akos Vandra wrote: > Hi! > > As I've started commiting patches to the project, I guess it's high > time I introduced myself a little bit. Thanks! It's nice to know who's out there. > > I am currently studying electrical engineering at the Budapest > University o