Re: [Openocd-development] [PATCH 1/6] Add cscope to .gitignore

Aaron Carroll wrote: Signed-off-by: Aaron Carroll aar...@cse.unsw.edu.au Acked-by: Peter Stuge pe...@stuge.se ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH 2/6] Add '-coreid' target option to support multiple cores per TAP.

Aaron Carroll wrote: ARM Cortex-A9 multi-core chips expose a single TAP/DAP which connects to both cores. The '-coreid' option selects which core the target should connect to. Note that at present, OpenOCD can connect to either core, but not both simulatenously, until ADI contexts can be

Re: [Openocd-development] [PATCH 4/6] cortex_a9: add source files for Cortex A9 support.

Aaron Carroll wrote: Signed-off-by: Aaron Carroll aar...@cse.unsw.edu.au --- src/target/cortex_a9.c | 2181 src/target/cortex_a9.h | 89 ++ 2 files changed, 2270 insertions(+), 0 deletions(-) create mode 100644 src/target/cortex_a9.c

Re: [Openocd-development] [PATCH 6/6] TCL configs for OMAP4430 and Pandaboard

Aaron Carroll wrote: +# GDB target: Cortex-A9, using DAP +# +# The debugger can connect to either core of the A9, but currently +# not both simultaneously. Change -coreid to 1 to connect to the +# second core. +# +set _TARGETNAME $_CHIPNAME.cpu +target create $_TARGETNAME cortex_a9

Re: [Openocd-development] [PATCH 6/6] TCL configs for OMAP4430 and Pandaboard

On 24 January 2011 19:29, Peter Stuge pe...@stuge.se wrote: Aaron Carroll wrote: +# GDB target: Cortex-A9, using DAP +# +# The debugger can connect to either core of the A9, but currently +# not both simultaneously.  Change -coreid to 1 to connect to the +# second core. +# +set _TARGETNAME

[Openocd-development] NAND Flash Bad Block Density - What is reasonable?

Hi All, I¹m working on a project that will require an ODM to program a NAND flash. I¹m providing 4 partitions worth of content to be programmed starting at 4 specific physical addresses on the chip. I understand from the ODM, that Hynix considers that up to 2% of the flash might be in bad blocks

Re: [Openocd-development] [PATCH 0/6] OMAP4430/Cortex-A9 Support

Hi Aaron, thanks for submitting this! I am looking forward to having a closer look when I get back next week. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale

[Openocd-development] segfault in cortex_m3_assert_reset

Hi all, Has anyone else problem with segfaults on current git? As soon as I issue a reset, openocd dies. This is with a STM32 target. Same result with both rlink and a jtagkey interface. Bisection was successful and pointed to commit '8f93c0a3... target: do not expose error numbers to users' by

[Openocd-development] [PATCH] fix segfault from stack corruption in ahbap_debugport_init

ahbap_debugport_init was queueing reads to a local stack variable but didn't execute the queue before returning. Since the result of the reads are not used anyway, it's better to pass NULL as the destination instead of a dummy variable. I changed this throughout the function, even for the reads

Re: [Openocd-development] NAND Flash Bad Block Density - What isreasonable?

openocd-development-boun...@lists.berlios.de wrote: I was asking the ODM to ensure that no more than 2 bad blocks occur in any 4M range of the flash as a requirement. You have a pretty good chance of hitting that ime. Anyone have any place to get something official about bad block density?