Re: [Openocd-development] patch[1/2]: insert space before left parenthesis

I tested it OK in VSProg, but in OpenOCD, no reply from the bug reporter. > The patch reads a bit oddly -- why would any type of parsing > code *add* characters instead of taking them out of the buffer?? It simply add a space as a delimiter. Below is the report: > Looking at svf.c, the code wrong

Re: [Openocd-development] [PATCH] ARMV7M: handle bkpt instruction on resume/step

On Monday 18 January 2010, Spencer Oliver wrote: > Skip over a bkpt instruction if found on resume/step. This is a bugfix for RAM-based code, yes? > +int armv7m_check_bkpt_inst(struct target *target) This name leaves a lot to be desired. How about using "maybe_skip" instead of "check"? And th

[Openocd-development] [PATCH] ARMV7M: handle bkpt instruction on resume/step

Skip over a bkpt instruction if found on resume/step. Only software breakpoints known to openod are handled. So this handles the special case of a user added bkpt, eg. semi-hosting. Signed-off-by: Spencer Oliver --- src/target/armv7m.c| 31 +++ src/target/armv

Re: [Openocd-development] patch[1/2]: insert space before left parenthesis

On Mon, Jan 18, 2010 at 10:13 PM, David Brownell wrote: > On Sunday 17 January 2010, Øyvind Harboe wrote: >> On Sun, Jan 17, 2010 at 9:56 PM, simon qian >> wrote: >> > see http://forum.sparkfun.com/viewtopic.php?p=90983#90983. >> > Can anybody try this? >> >> If you can confirm that this solves

Re: [Openocd-development] patch[1/2]: insert space before left parenthesis

On Sunday 17 January 2010, Øyvind Harboe wrote: > On Sun, Jan 17, 2010 at 9:56 PM, simon qian > wrote: > > see http://forum.sparkfun.com/viewtopic.php?p=90983#90983. > > Can anybody try this? > > If you can confirm that this solves the problem, I would want > a comment that explains why this is

Re: [Openocd-development] Problem with STM32 HardFault-Handler

On Monday 18 January 2010, Thomas Kindler wrote: > > My own runtime code enables all faults, so that if I > > override the default loop-to-self handler (by just > > providing a non-weak symbol) it will always kick in. > > I tried that, also. But as I understand, the HardFault handler can be > use

Re: [Openocd-development] Problem with STM32 HardFault-Handler

David Brownell wrote: > On Monday 11 January 2010, Thomas Kindler wrote: >> Joseph Yiu suggested this code to cause a hard-fault: >> >>__asm( >> "movs r0, #1 \t\n" // unaligned .. >> "ldm r0, {r1-r2} \t\n" // .. load-multiple >> "bx lr \t\n" >>); >> >>

Re: [Openocd-development] Problem with STM32 HardFault-Handler

David Brownell wrote: > On Monday 11 January 2010, Thomas Kindler wrote: >>> To clarify: it behaves fine after adding that line, >>> no wierdness? >> Not really - I still have to do one additional system reset using the >> push-button. But it's way better than having to power-cycle for my >

[Openocd-development] [PATCH] commands: allow scan_chain command to be executed during config

Adding taps and then dumping them is quite reasonable thing to do in a config script. Signed-off-by: Øyvind Harboe --- src/jtag/tcl.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/jtag/tcl.c b/src/jtag/tcl.c index f48993f..ffb5d27 100644 --- a/src/jtag/tcl.c +++ b

Re: [Openocd-development] OpenOCD on MX51

Hi David, On 1/18/10, David Brownell wrote: > On Sunday 17 January 2010, Alan Carvalho de Assis wrote: >> Now I need to find a way to place the processor on halt mode. I tried >> many commands, including "imx51.cpu arp_halt" with no success. > > Use plain old "halt". > > "arp_halt" looks to be un

Re: [Openocd-development] patch[2/2]: read target voltage first in vsllink or Amontec JTAGkey / Amontec JTAGkey-2

2010/1/18 David Brownell : > On Sunday 17 January 2010, Øyvind Harboe wrote: >> The OpenOCD model is currently just to report this as a LOG_USER() and >> not do anything else clever about it. To do anything clever upon these >> events > > ... voltage drop, or target issued reset ... > >> would requ

Re: [Openocd-development] patch[2/2]: read target voltage first in vsllink

On Mon, Jan 18, 2010 at 8:52 AM, David Brownell wrote: > On Sunday 17 January 2010, simon qian wrote: >> In most cases, it works, but as I tested under Ubuntu9.04, there is a chance >> that the USB will fail. >> If I read target voltage first, the problem disappear. >> >> For the lastest Versaloon

Re: [Openocd-development] patch[2/2]: read target voltage first in vsllink or Amontec JTAGkey / Amontec JTAGkey-2

On Sunday 17 January 2010, Øyvind Harboe wrote: > The OpenOCD model is currently just to report this as a LOG_USER() and > not do anything else clever about it. To do anything clever upon these > events ... voltage drop, or target issued reset ... > would require the error propagation handling in

Re: [Openocd-development] patch[2/2]: read target voltage first in vsllink or Amontec JTAGkey / Amontec JTAGkey-2

On Sunday 17 January 2010, Laurent Gauch wrote: > > > > >/ On Sun, Jan 17, 2010 at 9:58 PM, simon qian > >gmail.com > > > >wrote: > > />/ > The very first command after init command should be "read target > > voltage". > > />/ > > /