[Openocd-development] arm116jzf-s

Hi Is arm116jzf-s known to be supported by openocd? Regards. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] xsvf patch

My previous patch only fix the BUG that error message display the wrong information. Yes, data should be compared bit by bit, not byte by byte. And buf_cmp_mask can be called to do the comparation. I'll provide a patch for this. PS: P.S. It isn't really easy to read source code if it has long

Re: [Openocd-development] jtag_get_tms_path() - changes the 7 bit issue.

duane A while ago a number of us noticed that OpenOCD *ASSUMES* that all TAP duane transitions require 7 TMS clocks, which is quite wrong, and problematic. oyvind You can use the pathmove if you need something else. E.g. XScale and xsvf do this. The problem is not there, the problem is in

[Openocd-development] Support to interfaces except JTAG

Hi, I noticed there is a thread about supporting other programming interfaces except JTAG. How is it going? I'll release a program with these support. I tested it on AVR_ISP/JTAG, C51_ISP, C8051F_C2/JTAG, PSOC_ISSP, MSP430_JTAG(non-standard JTAG), and even STM32_ISP(Comm port). If such

Re: [Openocd-development] STM32 flash performance

Does anyone have any objections to committing this patch? It's relatively straightforward to revert and reportely improves performance significantly and hurts noone(so far). When we commit it we have a record of it at least Fine with me, i would also #if 0 the first

Re: [Openocd-development] arm116jzf-s

Hi On 4/2/09, plarroy plar...@promax.es wrote: Hi Is arm116jzf-s known to be supported by openocd? I think you are asking about arm1136jf-s. Yes, it is supported! Thank a look on i.MX31 and i.MX35. Regards. Best Regards, Alan ___

Re: [Openocd-development] arm116jzf-s

s/Thank/Take/ :-D On 4/2/09, Alan Carvalho de Assis acas...@gmail.com wrote: Hi On 4/2/09, plarroy plar...@promax.es wrote: Hi Is arm116jzf-s known to be supported by openocd? I think you are asking about arm1136jf-s. Yes, it is supported! Thank a look on i.MX31 and i.MX35.

Re: [Openocd-development] Support to interfaces except JTAG

Hi SimonQian, On 4/2/09, SimonQian simonq...@simonqian.com wrote: Hi, I noticed there is a thread about supporting other programming interfaces except JTAG. How is it going? I don't know much about it. I'll release a program with these support. I tested it on AVR_ISP/JTAG, C51_ISP,

Re: [Openocd-development] Support to interfaces except JTAG

On Apr 2, 2009, at 3:36 AM, SimonQian wrote: Hi, I noticed there is a thread about supporting other programming interfaces except JTAG. How is it going? There was some talk, but no action. It would require quite a bit of infrastructure work to remove the assumption that every pld and

[Openocd-development] [PATCH] Improve comments of interface files

Add full company name (if any), interface/dongle name, and URL to all interface config files. Please check the infos, I may not have gotten all of them right. Uwe. -- http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org |

Re: [Openocd-development] [PATCH] Improve comments of interface files

Committed. Thanks! -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html ___ Openocd-development mailing list Openocd-development@lists.berlios.de

[Openocd-development] [PATCH] Add missing STM32 BSTAPID to list of available ones

Add missing STM32 0x06412041, Revision A BSTAPID to list of available ones. This is checked against revision 8, 11-Feb-2009, of the RM0008 manual from http://www.st.com/stonline/products/literature/rm/13902.pdf. Also, I noticed that stm32.cfg will _not_ work for some targets per se, as it

[Openocd-development] [PATCH 1/5] plug a memory leak

Allocating a 6-byte memory location with malloc() is rather silly when this can be allocated on the stack. --- src/flash/nand.c |4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/src/flash/nand.c b/src/flash/nand.c index 51755aa..2b3b517 100644 --- a/src/flash/nand.c +++

[Openocd-development] [PATCH 2/5] add some rudimentary erased block accounting

This at least should make the nand info command a little more useful. --- src/flash/nand.c |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/src/flash/nand.c b/src/flash/nand.c index 2b3b517..7946e34 100644 --- a/src/flash/nand.c +++ b/src/flash/nand.c @@ -689,6

[Openocd-development] [PATCH 3/5] software ECC computation for NAND flash

--- src/flash/Makefile.am | 18 --- src/flash/nand.h |1 + src/flash/nand_ecc.c | 126 + 3 files changed, 138 insertions(+), 7 deletions(-) create mode 100644 src/flash/nand_ecc.c diff --git a/src/flash/Makefile.am

[Openocd-development] [PATCH 5/5] write ECC data when reflashing u-Boot on the SheevaPlug

--- src/target/board/sheevaplug.cfg |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/target/board/sheevaplug.cfg b/src/target/board/sheevaplug.cfg index 8e5c265..64e2596 100644 --- a/src/target/board/sheevaplug.cfg +++ b/src/target/board/sheevaplug.cfg @@ -99,8

[Openocd-development] [PATCH 4/5] add standard ECC layout and ECC computation for NAND writing

The ECC data is automatically computed and written to the OOB area when the oob_softecc option is passed to the nand write command. --- src/flash/nand.c | 61 + src/flash/nand.h | 12 ++ 2 files changed, 68 insertions(+), 5

Re: [Openocd-development] [PATCH] Add missing STM32 BSTAPID to list of available ones

Committed. Thanks! -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] [PATCH 1/5] plug a memory leak

Committed patches 1 through 5 inclusive. Please check that the patches went in correctly. Thanks! -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html ___

[Openocd-development] LPC2103 config file

I attach a config file for LPC2103 - hope that I've done that right (; 4\/3!! Index: src/target/target/lpc2103.cfg === --- src/target/target/lpc2103.cfg (revision 0) +++ src/target/target/lpc2103.cfg (revision 0) @@ -0,0

[Openocd-development] [Patch] Add board file for Olimex STM32-H103

Hi,I added a board file for the Olimex STM32-H103 eval board.Patch is attached.Cheers Esden --My blog: http://www.esden.netMy projects: http://open-bldc.org, http://multicopter.orgProjects I am involved in: http://ng.uavp.ch openocd-svn-1440-olimex_stm32_h103.patch Description: Binary data

Re: [Openocd-development] [PATCH] Oocdlink interface

On Wed, Mar 25, 2009 at 10:42:13PM +0100, joern kaipf wrote: Index: src/target/interface/oocdlink.cfg === --- src/target/interface/oocdlink.cfg (Revision 0) +++ src/target/interface/oocdlink.cfg (Revision 0) It seems this patch

Re: [Openocd-development] flash driver buffer size

Spencer Oliver We have just changed the stm32 flash driver buffer to 16k (was 8k). Spencer Oliver Is this worth doing on other flash drivers ?? Actually, I think coming up with a common architecture to do ARM flash would be better, or is more important. By that I specifically mean: 1) Download

Re: [Openocd-development] [Patch] Add board file for Olimex STM32-H103

Committed. Thanks! -- Øyvind Harboe PayBack incident management system Reduce costs and increase quality, free Starter Edition http://www.payback.no/index_en.html ___ Openocd-development mailing list Openocd-development@lists.berlios.de

Re: [Openocd-development] flash driver buffer size

It would be *great* to crack this problem once and for all. It's been discussed in the past on the list. 4)   That algorithm should/could use a *COMMON* set of commands    That is *common* to *ALL* targets. For MIPS as well as ARM targets? So each target type has a compiler built in?