Re: [Openocd-development] OpenOCD auto-config

2010-02-17 Thread Austin, Alex
I don't know any tcl beyond what little I've picked up from stock config files. Also, as far as I can tell, I can't un-init once init has been called, so this program starts and stops many instances of openocd. > -Original Message- > From: Øyvind Harboe [mailto:oyvind.har...@zylin.com] >

Re: [Openocd-development] OpenOCD auto-config

2010-02-17 Thread Øyvind Harboe
Why do you prefer writing this *outside* OpenOCD, rather than *inside* using tcl? -- Øyvind Harboe Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118 http://www.zylin.com/events_embeddedworld.html US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin

[Openocd-development] OpenOCD auto-config

2010-02-17 Thread Austin, Alex
Just starting to write a wrapper to auto-config openocd. Using python, it's a class that attempts to wrap openocd configuration. So far it doesn't do much, but I would appreciate any comments anyone has. Go ahead and run it on your machines (only Linux supported ATM) as it doesn't write to any file

Re: [Openocd-development] FYI -- SWD work

2010-02-17 Thread Michel Catudal
Le 17/02/2010 22:18, Xiaofan Chen a écrit : > On Tue, Feb 16, 2010 at 8:10 AM, David Brownell wrote: > > >> Then the other stuff will be more focussed specifically on SWD low >> level stuff. I figure that'll be the easiest place for other folk >> to help out with code ... new driver support,

Re: [Openocd-development] FYI -- SWD work

2010-02-17 Thread Xiaofan Chen
On Tue, Feb 16, 2010 at 8:10 AM, David Brownell wrote: > Then the other stuff will be more focussed specifically on SWD low > level stuff.  I figure that'll be the easiest place for other folk > to help out with code ... new driver support, in particular, but also > testing and all that. > I bel

Re: [Openocd-development] FYI -- SWD work

2010-02-17 Thread Michel Catudal
Le 17/02/2010 15:59, CeDeROM a écrit : >>> Partially - the Primer1 use RLink in JTAG mode, Primer2 use RLink in >>> SWD mode. I am planning to work on SWD support soon (probably >>> start/mid march) - I have even downloaded some documentation few days >>> ago :-) >>> I have a question on RL

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread Xiaofan Chen
On Thu, Feb 18, 2010 at 5:23 AM, CeDeROM wrote: > Ah, there were reports from Australia even for 0.2.0 that this JLink > does not work on FreeBSD, but the patch is provided - please take a > look at patch for current openocd port > (/usr/ports/devel/openocd/files) and try to (somehow) apply this

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread CeDeROM
Hello Xiaofan! On Wed, Feb 17, 2010 at 10:42 AM, Xiaofan Chen wrote: > Message: 3 > Date: Wed, 17 Feb 2010 16:41:00 +0800 > From: Xiaofan Chen > Subject: Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: >        FreeBSD status of 0.4.0-RC1) > To: Openocd-Dev > (...) > Error: J-Link com

Re: [Openocd-development] FYI -- SWD work

2010-02-17 Thread CeDeROM
On Tue, Feb 16, 2010 at 12:10 AM, David Brownell wrote: > On Monday 15 February 2010, CeDeROM wrote: >> > But also ... don't all those "STM32Primer" boards require >> > SWD support?  OpenOCD doesn't yet support that. >> >> Partially - the Primer1 use RLink in JTAG mode, Primer2 use RLink in >> SWD

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 8:33 PM, Xiaofan Chen wrote: > On Wed, Feb 17, 2010 at 4:41 PM, Xiaofan Chen wrote: > >> The first run with EK-LM3S1968 seems to work. But J-Link does not seem to >> work. > > J-Link V3 (black, IAR OEM) does not seem to work at all under FreeBSD. > J-Link V7 (black, ADI O

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 4:41 PM, Xiaofan Chen wrote: > The first run with EK-LM3S1968 seems to work. But J-Link does not seem to > work. J-Link V3 (black, IAR OEM) does not seem to work at all under FreeBSD. [mc...@myfreebsd /usr/home/mcuee/Desktop/build/openocd/luminary/lm3s1968]$ openocd -f

Re: [Openocd-development] OpenOCD failed to find libftdi in /usr/local

2010-02-17 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 4:47 PM, David Brownell wrote: >> Maybe it is not a real bug after all since there is a work-around to >> specify CFLAGS and LDFLAGS to get it built. > > That's how it's installed on one of my machines.  "configure" needs to > be fed those flags ... otherwise "openocd" won'

Re: [Openocd-development] [RFC, PATCH for 0.5] arm920t: data cache full support

2010-02-17 Thread Øyvind Harboe
Take #2 using MCR macro -- Øyvind Harboe Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 - 118 http://www.zylin.com/events_embeddedworld.html 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 debugge

Re: [Openocd-development] OpenOCD failed to find libftdi in /usr/local

2010-02-17 Thread David Brownell
On Wednesday 17 February 2010, Xiaofan Chen wrote: > > So I just tested it under Linux, if I install libftdi to /usr/local (which > > is the default if you build from source), it will fail to build. > > > > I will tend to think this is a bug. > > > > Maybe it is not a real bug after all since ther

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 4:35 PM, Xiaofan Chen wrote: > On Mon, Feb 15, 2010 at 8:43 AM, Xiaofan Chen wrote: >> I just want to use plain git if possible without using the port system. > > Yes it is possible now. I do not need to use the port system after all. > The first run with EK-LM3S1968 seem

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-17 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 8:43 AM, Xiaofan Chen wrote: > I just want to use plain git if possible without using the port system. Yes it is possible now. I do not need to use the port system after all. [mc...@myfreebsd ~/Desktop/build/openocd/build]$ CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local

Re: [Openocd-development] [RFC, PATCH for 0.5] arm920t: data cache full support

2010-02-17 Thread Øyvind Harboe
Does it work? I've tried to clean up the patch a bit(I can't test this version, so you would have to do that...). If that nicer "execute any instruction" approach pans out then this patch can be simplified... -- Øyvind Harboe Visit us at Embedded World, March 2nd-4th. IS2T's stand, HALL 10 -

Re: [Openocd-development] OpenOCD failed to find libftdi in /usr/local

2010-02-17 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 4:00 PM, Xiaofan Chen wrote: >> Actually I consider this a bug of OpenOCD. /usr/local should >> be searched, even under Linux. >> > > So I just tested it under Linux, if I install libftdi to /usr/local (which > is the default if you build from source), it will fail to build

Re: [Openocd-development] [bisected] Re: arm920t regression cache support

2010-02-17 Thread Marc Pignat
Hi all! On Wednesday 17 February 2010 00:10:43 David Brownell wrote: > On Tuesday 16 February 2010, Øyvind Harboe wrote: ... > But rather complicated, compared with using real flush > ops (not via scanchain 15). > Sure, I will the "execute one instruction" method today! Regards Marc __

Re: [Openocd-development] [RFC, PATCH for 0.5] arm920t: data cache full support

2010-02-17 Thread Marc Pignat
same patch rebased as requested! 0001-step1.patch is Øyvind Harboe's patch rebased 0002-atm920t-cleanup-data-cache-handling.patch my patch for data cache support From 06c2935ba15ae54d33612315ce3cbef3a2481c92 Mon Sep 17 00:00:00 2001 From: Marc Pignat Date: Tue, 16 Feb 2010 10:08:18 +0100 Subject

[Openocd-development] OpenOCD failed to find libftdi in /usr/local

2010-02-17 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 9:47 AM, Xiaofan Chen wrote: > On Mon, Feb 15, 2010 at 9:36 AM, CeDeROM wrote: >> Ah yes, OpenOCD's configure script can also assume using >> "/usr/local/lib" and "/usr/local/include" to search for libraries and >> header files - it would be nice, however if it don't the P