Re: [Openocd-development] AVR32 support

2010-08-31 Thread simon qian
It should be same for UC3C series, because the port is 5V tolarent. I'm using KiCAD, eagle has a limitation on the size of the PCB. I have released the AVR32 code, but it will be tested later this week. http://code.google.com/p/vsprog/source/browse/trunk/dongle/firmware/STK500v2 http://code.google

Re: [Openocd-development] AVR32 support

2010-08-31 Thread Michel Catudal
On 31/08/2010 11:18, simon qian wrote: My AVR32 debugger/programmer will be released next week. I'll get some sample(UC3B0256) from Atmel this week. I think I can do the test after next week. Are you planning to support the UC3C series as well? They are +5V devices and not +3.3V devices a

Re: [Openocd-development] ULink

2010-08-31 Thread gladio
I think it will be easier to work with segger jlink.. But I have one more question are there any restrictions on devices? I plan to get either the stm32f013 or the lpc1768, but I dont know if there are some devices which are not supported or not.. regards -

Re: [Openocd-development] ULink

2010-08-31 Thread Spencer Oliver
On 30/08/2010 21:23, gla...@hotmail.de wrote: Hi guy's I was thinking about to get the segger jlink or the ulink2. But since I only found the cfg File for JLink I was wondering wheter uLink2 is supported or not. thx Not directly, but this may help http://lists.berlios.de/pipermail/openocd-dev

Re: [Openocd-development] AVR32 support

2010-08-31 Thread simon qian
My AVR32 debugger/programmer will be released next week. I'll get some sample(UC3B0256) from Atmel this week. I think I can do the test after next week. 2010/8/17 Michel Catudal > On 16/08/2010 21:54, David Brownell wrote: > >> >> --- On Mon, 8/16/10, Michel Catudal wrote: >> >> >> >>> Irreleva

[Openocd-development] Numonyx M29W160ET patch

2010-08-31 Thread Wookey
Someone called David Carne popped up on IRC and offered a fix (as he's not on this list so can;t post here). I am just passing it on. (thanx David) 10:54 < davidc__> Basically; the Numonyx M29W160ET has an incorrect CFI PRI block; it describes the erase blocks backwards 10:54 < davi

Re: [Openocd-development] invalid command name "jtag"

2010-08-31 Thread gcembed
Hello, I am very sorry to have disturbed you. It was my fault. With this version, I have to call jlink-segger.cfg before stm32.cfg. Everything is working now. Gaƫtan On 08/31/2010 02:40 PM, gcembed wrote: Hello, I have just downloaded and compiled devel version of OpenOCD from Git repo (Open O

[Openocd-development] invalid command name "jtag"

2010-08-31 Thread gcembed
Hello, I have just downloaded and compiled devel version of OpenOCD from Git repo (Open On-Chip Debugger 0.5.0-dev-00494-g5c98e06) and when I try to run OpenOCD with script files provided in tcl/target/, I have following error : (I comment jtag_ntrst_delay because it is also an invalid command