Re: [Openocd-development] Keil AGDI interface to openOCD?

2009-04-27 Thread Dario Vecchio
See also: http://www.keil.com/appnotes/docs/apnt_173.asp Dario - Original Message - From: Dario Vecchio To: SimonQian ; Pedro Martos ; openocd-development@lists.berlios.de Sent: Monday, April 27, 2009 6:12 PM Subject: Re: [Openocd-development] Keil AGDI interface to openOCD

Re: [Openocd-development] Keil AGDI interface to openOCD?

2009-04-27 Thread Dario Vecchio
It seems they have just released a new version: http://www.keil.com/appnotes/docs/apnt_145.asp my project is built around the old version Dario - Original Message - From: SimonQian To: Dario Vecchio ; Pedro Martos ; openocd-development@lists.berlios.de Sent: Monday, April 27

Re: [Openocd-development] Breakpoint handling in run_agorithm

2008-07-31 Thread Dario Vecchio
Hi Magnus, I see another problem if we are not lucky and an existing application breakpoint is exactly at the same address of the temporary breakpoint used by the algorithm. As breakpoints are stored with respect to their address here is what happens: > b) Add the temporary breakpoint used by

Re: [Openocd-development] 'flash write_image' and 'verify_image' commands fail if there are no more hardware breakpoints available

2008-07-31 Thread Dario Vecchio
> You could define a few step/breakpoint commands in tcl that has this > functionality. The existing functions would then be the low level > implementation > of hardware/software breakpoints. with the "breakpoints list/save/restore" patch one can use a similar script: ---

[Openocd-development] 'flash write_image' and 'verify_image' commands fail if there are no more hardware breakpoints available

2008-07-31 Thread Dario Vecchio
Hi all, I found that after manually setting hardware breakpoints 'flash write_image' and 'verify_image' commands fail if there are no more hardware breakpoints available. I think they should be removed before command execution and then restored.

Re: [Openocd-development] Breakpoints list/save/restore patch

2008-07-28 Thread Dario Vecchio
> Dario Vecchio wrote: >> if is omitted it defaults to "BreakPoints.bpt" in the current >> working dir. > I have a nit to pick with that. > > I do not think MixeDCaseFilEnames are good, all filenames should be lower > case. > > Reason: Openocd

Re: [Openocd-development] Breakpoints list/save/restore patch

2008-07-28 Thread Dario Vecchio
> --- > Note that this patch also modify the "rbp" command: without arguments it > clear all breakpoints: > > "bp" : clear all breakpoints > > --- sorry: "rbp

[Openocd-development] Breakpoints list/save/restore patch

2008-07-28 Thread Dario Vecchio
Here is the patch to list/save/restore breakpoints. Usage: --- "bpsave " : saves a script file that can be used to restore breakpoints in this format: bp 0x0040 0x0004 hw bp 0x0100 0x0004 hw bp 0x0200 0x00

Re: [Openocd-development] STR9 reset behaviour

2008-07-28 Thread Dario Vecchio
> What openocd svn version are you using? Right now I have updated to the latest svn (879) and the behaviour is the same. (compiled without modifications with mingw inside Code::Blocks in WinXP) The modified version I use is a pre-tcl version modified to compile with VC6. The behaviour is the s

[Openocd-development] STR9 reset behaviour

2008-07-28 Thread Dario Vecchio
Dear developers, I'm using str9comstick and, having to debug some problems, I would like to know the following things: - nSRST only resets the core or also resets the embeddedICE (e.g. clear all breakpoints)? - the reset halt sequence can be done in this way? - reset all (nSRST and nTRST asserte