Re: [Openocd-development] SWD vs. SWIM

2010-02-19 Thread simon qian
Hi, I have implemented SWIM interface in Versaloon. So I know SWIM is NOT SWD, SWIM is more complex. 2010/2/20 Michel Catudal > Le 19/02/2010 16:55, CeDeROM a écrit : > > Ive just found an interesting STM8Discovery DevelKit with STM8S105C6T6 > > microcontroller (8-bit, 32 KB Flash, 2 KB RAM, 1 K

Re: [Openocd-development] JLink cable versions (was: FYI -- SWD work)

2010-02-19 Thread Xiaofan Chen
On Sat, Feb 20, 2010 at 3:25 AM, CeDeROM wrote: > I have searched a bit and it looks that new JLink costs about 250EUR > that if far too much for me for one-time-use.  But  I have searched a > bit and found something like below - I would be grateful for more > details (especially JLink/JLink2 dif

Re: [Openocd-development] SWD vs. SWIM

2010-02-19 Thread Michel Catudal
Le 19/02/2010 16:55, CeDeROM a écrit : > Ive just found an interesting STM8Discovery DevelKit with STM8S105C6T6 > microcontroller (8-bit, 32 KB Flash, 2 KB RAM, 1 KB EEPROM) onboard > for extremely low price (~$10) with supplied JTAG programmer (Embedded > ST-LINK). Anyone knows/use this St-Link ca

[Openocd-development] SWD vs. SWIM

2010-02-19 Thread CeDeROM
Ive just found an interesting STM8Discovery DevelKit with STM8S105C6T6 microcontroller (8-bit, 32 KB Flash, 2 KB RAM, 1 KB EEPROM) onboard for extremely low price (~$10) with supplied JTAG programmer (Embedded ST-LINK). Anyone knows/use this St-Link cable? Is this SWIM a SWD implementation? More de

Re: [Openocd-development] OpenOCD auto-config

2010-02-19 Thread Austin, Alex
For interface, it just tries all the interface definitions in /usr/local/share/openocd/scripts/interface. Whichever one is detected last is then loaded with an empty scan chain, and it should report all the detected TAPs on the chain. Note, that's just the test code which tests a wrapper class.

Re: [Openocd-development] JLink cable versions (was: FYI -- SWD work)

2010-02-19 Thread CeDeROM
Hello all! On Fri, Feb 19, 2010 at 10: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. Here at work I have seen a few V3 (IAR), many V6 > (Segger, IAR and Atmel Sam-ICE), V7 (Analog Devi

Re: [Openocd-development] OpenOCD with libftdi-1.0

2010-02-19 Thread Xiaofan Chen
On Fri, Feb 19, 2010 at 10:12 PM, Xiaofan Chen wrote: > So I just built libftdi 1.0 from git and tested it under Ubuntu 9.10 > 32bit with OpenOCD. > > But I will compare with the same build with libftdi-0.17. > > ./StellarisWare/boards/ek-lm3s1968/qs_ek-lm3s1968/gcc/qs_ek-lm3s1968.bin > in 10.2794

[Openocd-development] OpenOCD with libftdi-1.0

2010-02-19 Thread Xiaofan Chen
On Tue, Feb 16, 2010 at 3:17 PM, David Brownell wrote: > On Monday 15 February 2010, Freddie Chopin wrote: >> I wonder whether that would work as fast as ftd2xx... I see that there >> won't be support for isochronous transfers, and I've heard somewhere >> that this is important for applications li

Re: [Openocd-development] OpenOCD segfaults when the permission is not yet set

2010-02-19 Thread Xiaofan Chen
On Wed, Feb 17, 2010 at 4:01 AM, David Brownell wrote: > On Tuesday 16 February 2010, Xiaofan Chen wrote: >> I have not set up the udev permission of the EK-LM3S1968 on board debugger. >> Then >> it segfaults if running as normal user. Running as root it is okay. > > Seems buglike.  You should ge

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

2010-02-19 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] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-19 Thread Xiaofan Chen
On Thu, Feb 18, 2010 at 5:23 AM, CeDeROM wrote: >> Error: J-Link command 0xdf failed (-6) >> Error: usb_bulk_write failed (requested=6, result=-6) >> Error: jlink_tap_execute, wrong result -107 (expected 1) >> Command handler execution failed >> Warn : jtag initialization failed; try 'jtag init' a

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

2010-02-19 Thread 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. Here at work I have seen a few V3 (IAR), many V6 > (Segger, IAR and Atmel Sam-ICE), V7 (Analog Device mIDAS

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

2010-02-19 Thread Xiaofan Chen
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. Here at work I have seen a few V3 (IAR), many V6 (Segger, IAR and Atmel Sam-ICE), V7 (Analog Device mIDAS-Link) and one or two V8 units. We also got one J-Link Pro with the E

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

2010-02-19 Thread Spencer Oliver
On 19/02/2010 00:25, Xiaofan Chen wrote: > On Fri, Feb 19, 2010 at 5:22 AM, CeDeROM wrote: >> Thank you Igor I will try to do this also for a J-Link interface, but >> I dont have one (is it expensive, maybe Ill get one?). > > J-Link is not too expensive, especially the OEM ones from IAR or > other