Re: [Openocd-development] [patch] fix $target_name cget -work-area-backup

2009-06-07 Thread Øyvind Harboe
Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [patch] target list tweaks

2009-06-07 Thread Øyvind Harboe
Committed. Thanks! -- Øyvind Harboe Embedded software and hardware consulting services http://consulting.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] [patch] fix $target_name cget -work-area-backup

2009-06-07 Thread David Brownell
Bugfix: $target_name cget/configure -work-area-backup commands should return the "is it backed up?" flag, not the work area size. --- src/target/target.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Bugfix: $target_name cget/configure -work-area-backup commands should return the "is i

[Openocd-development] [patch] target list tweaks

2009-06-07 Thread David Brownell
TARGET list tweaks: - Don't let disabled TAPs be set as the current target - Improve "targets" output: * Remove undesirable "chain position" number; we discourage using them * TAP and Target column updates: + make them long enough for current usage + improve labels, re

Re: [Openocd-development] FT2232H based dongle with adaptive clocking support

2009-06-07 Thread Ben Dooks
On Sun, Jun 07, 2009 at 12:49:49AM +0200, Patrick Wieland wrote: > This is my first posting to this mailing list, so I friendly say 'hello' to > everyone :-) > I am working on a OpenOCD dongle based on the FT2232H. I want to support > adaptive clocking, but I don't know how to accomplish this tas

Re: [Openocd-development] [patch] just ignore disabled targets

2009-06-07 Thread Zach Welch
On Sat, 2009-06-06 at 19:43 -0700, David Brownell wrote: > Let disabled targets be ignored during normal operation: > > - In target_examine(), ignore disabled TAPs > > - Reset handling must not poke at them either: > * fail $target_name arp_* operations on disabled TAPs > * in startup

Re: [Openocd-development] [patch] evb_lm3s811 docs

2009-06-07 Thread Zach Welch
On Fri, 2009-06-05 at 02:55 -0700, David Brownell wrote: > Clarify docs for the evb_lm3s811 layout: works in > two modes, not just one. > --- > doc/openocd.texi |5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) Committed, r2099. --Z ___

Re: [Openocd-development] [PATCH] Make mdw output readable again

2009-06-07 Thread Zach Welch
On Thu, 2009-06-04 at 17:34 +0200, Magnus Lundin wrote: > Regards > Magnus Committed, r2098. Sorry for causing this regression. --Z ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/open

Re: [Openocd-development] [patch] openocd.texi - final commands (ch12/cpu config)

2009-06-07 Thread Zach Welch
On Fri, 2009-06-05 at 01:06 -0700, David Brownell wrote: > Rework chapter 12 (CPU configuration) to use @deffn, match > the code more closely, and present things more clearly. > > Includes the *current* list of targets. > > Whew ... this should be the last set of "reference matter" > changes, I t

Re: [Openocd-development] [patch] openocd.texi misc cleanup

2009-06-07 Thread Zach Welch
On Thu, 2009-06-04 at 01:59 -0700, David Brownell wrote: > Various minor tweaks for the User's guide. > > - Fix various minor (but repeated) typographic goofs; > - Talk about TAP "declaration" not "creation" (they exist >even if OpenOCD never learns about their board); > - Encourage board.c

[Openocd-development] Retired endstate command

2009-06-07 Thread Øyvind Harboe
Committed. Retired endstate(and updated docs). Background polling would overwrite any changes to the endstate. From the command line point of with the recent changes to ir/drscan the "endstate" command wasn't used anyway. The best I can do for the beagleboard config files that use "endstate" is to

Re: [Openocd-development] endstate command

2009-06-07 Thread Øyvind Harboe
On Sun, Jun 7, 2009 at 7:45 PM, David Brownell wrote: > On Sunday 07 June 2009, David Brownell wrote: >> > How about retiring the "endstate" command? >> >> No current in-tree users, FWIW. > > ... except beagleboard init, sorry. Does that usage happen to be broken anyway? -- Øyvind Harboe Embed

Re: [Openocd-development] Target AJAX like support - User Interface Thread

2009-06-07 Thread Duane Ellis
duane> I think your view is more (A), and mine is more (B). david> Yet my example of a "flash download" tool seems more like (B) to me. :) Seems like we both sit at two different ends of the spectrum, you see "de-bricking/flashing" a board as day to day I don't. That is perhaps good, it makes

Re: [Openocd-development] Target AJAX like support - User Interface Thread

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, Duane Ellis wrote: > So what should we focus on? > > (A)  Wizard type features to help *new*users* get started >   > (B)  Day to day operational features. > > I think your view is more (A), and mine is more (B). Yet my example of a "flash download" tool seems more like (

Re: [Openocd-development] endstate command

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, David Brownell wrote: > > How about retiring the "endstate" command? > > No current in-tree users, FWIW. ... except beagleboard init, sorry. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists

Re: [Openocd-development] Target AJAX like support - User Interface Thread

2009-06-07 Thread Duane Ellis
duane> [ajax] david> Saying "AJAX" or talking about any other implementation tech feels to me like putting the cart before the horse. Correct, I should have given more examples. What I ment was - 2 parts: 1) the GUI interface (a) could be built-in webserver + javascript (ajax) OR (b)

Re: [Openocd-development] endstate command

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, Øyvind Harboe wrote: > How about retiring the "endstate" command? No current in-tree users, FWIW. Make sure you remove the openocd.texi references to it too ... might want to first merge the openocd.texi "user's guide tweaks" patch I sent last week, so you don't break its

Re: [Openocd-development] [PATCH] Do not try to examine targets with disabled taps

2009-06-07 Thread David Brownell
On Sunday 07 June 2009, Duane Ellis wrote: > But - today I think what you mean is this: > > Today, all target reset handlers are done like this:   >     $_targetname  configure -event reset-init  { CURLYBRACE } They aren't "all" like that, though. So the solution you list below can't always work

Re: [Openocd-development] [PATCH] Do not try to examine targets with disabled taps

2009-06-07 Thread Duane Ellis
duane> $TARGETNAME mdw david> Though "mdw" is really impractical for scripting. yea, it's probably a very bad example, one probably needs to use '$targetname mem2array" or "$targetname array2mem", or we can create a helper sub-command david> A third option: too painful to use. How exactly is

Re: [Openocd-development] FT2232H based dongle with adaptive clocking support

2009-06-07 Thread Joern Kaipf
Patrick Wieland wrote: >> The ftdi-2232-H monitors the RTCK signal on GPIOL4 If you find this pin, its okay. On design I use GPIOL3 ;) The PCB of the OOCDLink with RTCK support is laying in front of me, but I ran out of FT2232Hs to assemble it, so I have to wait until I get the ic from the dis

Re: [Openocd-development] [PATCH] Do not try to examine targets with disabled taps

2009-06-07 Thread David Brownell
On Saturday 06 June 2009, Rick Altherr wrote: > > Again, we don't have such cases today.  We can speculate all kinds > > of things, but in the absence of real hardware I don't think the > > results of speculation are compelling.  Plus, "$target_name curstate" > > has a very limited range of state o

[Openocd-development] endstate command

2009-06-07 Thread Øyvind Harboe
How about retiring the "endstate" command? This command can't work unless polling is turned off as the global endstate gets overwritten by the background polling. If other commands such as "drscan" does not have a clearly defined default end-state then the endstate of such commands is effectively