Re: [Openocd-development] 0.2.0 Status Report

2009-05-25 Thread Xiaofan Chen
On Sun, May 24, 2009 at 12:36 PM, Zach Welch wrote: > The following issues have been reported and should try to be resolved: > - flashing on LPC-P2148 (Xiaofan Chen) Just want to say that this problem is now solved. Please refer to the other thread about the solution. I need to erase the first ba

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread Zach Welch
On Sun, 2009-05-24 at 15:28 -0700, David Brownell wrote: > On Sunday 24 May 2009, Zach Welch wrote: > > The OpenOCD User Guide: (aka The Guide) > > "Someone" needs to change the name of the document then; > it's now "Open On-Chip Debugger (OpenOCD)". Agreed that > calling it a "User's Guide" wou

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread David Brownell
On Sunday 24 May 2009, Zach Welch wrote: > The OpenOCD User Guide:  (aka The Guide) "Someone" needs to change the name of the document then; it's now "Open On-Chip Debugger (OpenOCD)". Agreed that calling it a "User's Guide" would clarify. > - should start to focus on _using_ OpenOCD > - written

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread David Brownell
On Sunday 24 May 2009, Duane Ellis wrote: > DAVID> > > Ways other folk can help with the doc+code audits > > are to pick a section of the texi and convert it to > > use the @deffn presentation style ... then crosscheck > > against the code. > > Can you expand on this, explain a little bit more wha

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread Zach Welch
On Sun, 2009-05-24 at 17:51 -0400, Duane Ellis wrote: > DAVID> > > Ways other folk can help with the doc+code audits > > are to pick a section of the texi and convert it to > > use the @deffn presentation style ... then crosscheck > > against the code. > > > > Can you expand on this, explain a

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread Duane Ellis
DAVID> > Ways other folk can help with the doc+code audits > are to pick a section of the texi and convert it to > use the @deffn presentation style ... then crosscheck > against the code. > Can you expand on this, explain a little bit more what you mean. I think, @deffn -is a "texi" type docu

Re: [Openocd-development] 0.2.0 Status Report

2009-05-24 Thread David Brownell
On Saturday 23 May 2009, Zach Welch wrote: > - others? Areas where I'd like to see continued improvement during the remainder of this cycle: - Less server message spam. Servers should only log messages when something's *seriously* wrong, and should not rely on stdout except maybe during

[Openocd-development] 0.2.0 Status Report

2009-05-23 Thread Zach Welch
Hi all, At this point, I believe almost all of the outstanding patches have been brought up-to-date and applied to the trunk, with the two following exceptions: - FTD2XX high-speed device support - remove cmd_queue_cur_state - add target examination check in cortex m3 The following issues have b