Re: [Openocd-development] Reset halt issues with EK-LM3S9B92

2010-05-11 Thread Spencer Oliver
On 11/05/2010 18:22, Øyvind Harboe wrote: So should we just apply this patch you think? Do not have any tempest silicon to test, but it sounds as if they forgot to fix this old bug. Tobias, Can you confirm that the srst pin is actually getting asserted/released? Another test is to hold the

[Openocd-development] Outstanding patches

2010-05-11 Thread Øyvind Harboe
Does anyone have patches or fixes that haven't made it into the repository yet? We rely on patch submitters to follow up on patches to make sure that they are not lost Please nag! :-) Does anyone know of modified versions of OpenOCD out there that it would be a good idea to have merged? --

Re: [Openocd-development] [PATCH] fix instruction refilling bug when using software breakpoints on a big-endian arm926ej-s system

2010-05-11 Thread Øyvind Harboe
Looks reasonable to me... Has it been regression tested on a little endian target? If I can get confirmation on regression testing and I don't hear any protests I'm inclined to merge it. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.ht

Re: [Openocd-development] [PATCH] Fujitsu MBM29SL800TE flash support

2010-05-11 Thread Øyvind Harboe
Merged. Thanks! -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@list

Re: [Openocd-development] tcl echo and puts question

2010-05-11 Thread Øyvind Harboe
puts is a tcl command with tcl defined behavior. echo is an OpenOCD command with OpenOCD defined behavior. Probably there is a bit of history and cleanup to be done here, both in terms of behavior & definition. I would expect puts to work w/stdout and echo to work with the currently active channe

Re: [Openocd-development] [PATCH 2/2] Documentation: consistency in GDB command name

2010-05-11 Thread Øyvind Harboe
Merged both. Thanks! -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-developmen

Re: [Openocd-development] JTAG-DP STICKY ERROR

2010-05-11 Thread Anton Fedotov
Hello Rick, in my case this error occures when I try to access memory on illegal address. Mostly it was result of absent MMU support for Cortex-A8 in OpenOCD. After the patch with MMU support this error had almost gone. But it always shows up when I use software breakpoints. It is a bug. And I hav

Re: [Openocd-development] Reset halt issues with EK-LM3S9B92

2010-05-11 Thread Øyvind Harboe
So should we just apply this patch you think? -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing l

[Openocd-development] JTAG-DP STICKY ERROR

2010-05-11 Thread Rick Bronson
Hi, I'm getting STICKY ERROR's when I startup, just wondered if this is normal or not? My setup: 1. Beagleboard Rev B4 2. Flyswatter (new May 2010) with EMUL0, EMUL1 not pulled down, SRST not connected. 3. Debian When I do: sudo openocd -s /home/rick/in/openocd/tcl -f interface/flyswat

[Openocd-development] [rfc/patch] CFI with strict bus_width usage

2010-05-11 Thread Antonio Borneo
Hi, branch "cfi" inside http://git.infradead.org/users/borneoa/openocd.git contains a set of patches I would propose for being merged in OpenOCD. My development is mainly a review of memory accesses to CFI flash to guarantee that every access is performed at CFI bus_width size. Current version of

Re: [Openocd-development] [PATCH] cfi: add Numonyx M29W128G reset workaround

2010-05-11 Thread Spencer Oliver
On 11/05/2010 07:47, Michael Schwingen wrote: Spencer Oliver wrote: The ST/Numonix M29W128G has an issue when a 0xff cmd is sent, it cause an internal undefined state. The workaround according to the Numonyx is to send another 0xf0 reset cmd. Looks good to me. I have had similar problems in ou