[Openocd-development] improve arm11 performance

2010-02-21 Thread Øyvind Harboe
I would like to push these changes. https://lists.berlios.de/pipermail/openocd-development/2010-February/014638.html There was some discussion to add a capability for interfaces to override a fn pointer to implement specific fn's more efficiently, but that mechanism does not exist yet and it is a

Re: [Openocd-development] mem2array command fails in event handler

2010-02-21 Thread David Brownell
On Saturday 20 February 2010, Rolf Meeser wrote: > A target script defines a "reset-end" handler. In this handler I need to read > a few words from target memory. When I try to use "ocd_mem2array", the > command fails with > Error: 357 1442 target.c:3106 jim_mem2array(): mem2array: no command con

Re: [Openocd-development] OpenOCD auto-config

2010-02-21 Thread David Brownell
On Sunday 21 February 2010, Xiaofan Chen wrote: > I think the LM3S1968 is like other Luminary boards and > the default ICDI layout works fine since the default config > file works fine (the JTAG frequency may need to be lowered > for certain OS or certain USB ports). This suggests to me that succe

Re: [Openocd-development] OpenOCD auto-config

2010-02-21 Thread Xiaofan Chen
On Mon, Feb 22, 2010 at 10:01 AM, David Brownell wrote: > So far as I'm aware, all *current* Luminary boards should > use the same ft2232 layout -- just like the "ICDI" boards. > But the old LM3S811 eval boards should use "evb_lm3s811" > since they're not quite the same. > > I don't happen to know

Re: [Openocd-development] OpenOCD auto-config

2010-02-21 Thread David Brownell
On Thursday 18 February 2010, Xiaofan Chen wrote: > What does it do right now? Just finding out the interface? I actually > have the Luminary EK-LM3S1968 instead of LM3S811. Looks like it's looking at the USB vendor and product IDs, which for "luminary" and "luminary-lm3s811" are the same (just lo

[Openocd-development] Relase 0.4.0 is out ... 0.5.0-dev started

2010-02-21 Thread David Brownell
Archives are in the Berlios and SourceForge "files" areas. Mainline git is now tagged as "0.5.0-dev"; the merge window is open. If we need a bugfix release, it'll branch off from the commit with the "0.4.0" tag. I've committed a few patches from my pending queue, most notably: - Making the ARM

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

2010-02-21 Thread Xiaofan Chen
On Sun, Feb 21, 2010 at 4:51 PM, simon qian wrote: > Does SWD related protocol of J-Link open to the public? > No I do not think so. J-Link is a proprietary product from Segger. There are some documentation from Segger but it is not really complete. I can see the support of J-Link in OpenOCD most

Re: [Openocd-development] SWD vs. SWIM

2010-02-21 Thread Xiaofan Chen
On Mon, Feb 22, 2010 at 4:52 AM, Spencer Oliver wrote: > On 21/02/2010 08:49, simon qian wrote: >> Hi, >> As I know, ST-Link supports JTAG for STM32 and SWIM for STM8, but it >> doesn't support SWD. >> If you want to reflash STM32 of ST-Link to be supported by OpenOCD, you >> can try Versaloon dri

Re: [Openocd-development] SWD vs. SWIM

2010-02-21 Thread Spencer Oliver
On 21/02/2010 08:49, simon qian wrote: > Hi, > As I know, ST-Link supports JTAG for STM32 and SWIM for STM8, but it > doesn't support SWD. > If you want to reflash STM32 of ST-Link to be supported by OpenOCD, you > can try Versaloon driver, but you will lost ST-Link's functionality. > The ST-LINK

Re: [Openocd-development] Recover command for a "Locked" TI/Luminary LM3Sxxxx Microcontroller

2010-02-21 Thread David Brownell
On Sunday 21 February 2010, Arne Pagel wrote: > > Wait a bit until the "send arbitrary TMS bitsequence" > > patches get merged, after the 0.5 merge window opens. > > (I sent a preview a while back.  SWD support needs them.) E.g. if you look at http://repo.or.cz/w/openocd/dave.git in the "swd" bran

Re: [Openocd-development] Recover command for a "Locked" TI/Luminary LM3Sxxxx Microcontroller

2010-02-21 Thread David Brownell
On Sunday 21 February 2010, Arne Pagel wrote: > > Wait a bit until the "send arbitrary TMS bitsequence" > > patches get merged, after the 0.5 merge window opens. > > (I sent a preview a while back. SWD support needs them.) > > > > Then define a Stellaris-specific command to use that > > (assert S

Re: [Openocd-development] Hint in Documentation, running openocd as normal user under linux, udev rules

2010-02-21 Thread David Brownell
On Sunday 21 February 2010, Arne Pagel wrote: > Hello, > perhaps this is my fault but I can't find a hint in the OpenOCD-Docs for > enabling USB Dongles as > normal user on Linux Systems. One hint is in the README file: == Installing OpenOCD == On Linux,

Re: [Openocd-development] Recover command for a "Locked" TI/Luminary LM3Sxxxx Microcontroller

2010-02-21 Thread Arne Pagel
> Wait a bit until the "send arbitrary TMS bitsequence" > patches get merged, after the 0.5 merge window opens. > (I sent a preview a while back. SWD support needs them.) > > Then define a Stellaris-specific command to use that > (assert SRST, do the magic sequences, release SRST, > wait 400 msec

[Openocd-development] Hint in Documentation, running openocd as normal user under linux, udev rules

2010-02-21 Thread Arne Pagel
Hello, perhaps this is my fault but I can't find a hint in the OpenOCD-Docs for enabling USB Dongles as normal user on Linux Systems. I created a new rule-file for udev to get my Luminary ICDI Board working as normal user on my ubuntu system: /etc/udev/rules.d/99-openocd.rules # Luminary ICD

Re: [Openocd-development] SWD vs. SWIM

2010-02-21 Thread simon qian
SWD is working in my branch of OpenOCD, but ONLY on Versaloon dongle. Official OpenOCD will maybe add SWD support in 0.5 release. FT2232H is USB-HS device, I don't think there is any chance for USB-FS STM32 Device to be faster. But it's almost impossible for FT2232H to support SWIM. If you want ST

Re: [Openocd-development] SWD vs. SWIM

2010-02-21 Thread CeDeROM
On Sun, Feb 21, 2010 at 8:49 AM, simon qian wrote: > Hi, > As I know, ST-Link supports JTAG for STM32 and SWIM for STM8, but it doesn't > support SWD. > If you want to reflash STM32 of ST-Link to be supported by OpenOCD, you can > try Versaloon driver, but you will lost ST-Link's functionality. O

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

2010-02-21 Thread simon qian
Does SWD related protocol of J-Link open to the public? 2010/2/19 Piotr Esden-Tempski > Hi! > > On Feb 19, 2010, at 11:36 AM, Xiaofan Chen wrote: > > > On Fri, Feb 19, 2010 at 5:00 PM, Spencer Oliver > wrote: > > > >> The latest jlink version i have here is v8. > >> > > > > That is quite new. H

Re: [Openocd-development] SWD vs. SWIM

2010-02-21 Thread simon qian
Hi, As I know, ST-Link supports JTAG for STM32 and SWIM for STM8, but it doesn't support SWD. If you want to reflash STM32 of ST-Link to be supported by OpenOCD, you can try Versaloon driver, but you will lost ST-Link's functionality. 2010/2/20 Michel Catudal > Le 20/02/2010 00:05, simon qian a