On Fri, 2009-05-29 at 13:02 +0800, Xiaofan Chen wrote:
> On Fri, May 29, 2009 at 10:04 AM, Zach Welch <z...@superlucidity.net> wrote:
> > The following tasks appear to be pending for the 0.2.0 release:
> > - fix OMAP3 problems reported by Dick Behme (or did these get resolved?)
> > - final packaging fix-ups (RPM file layout)
> > - reporting/testing tools
> > - documentation:
> >  - updates and clean-ups for The Guide (openocd.texi):
> >    - document commands for str9pec, ocl, xscale, arm11, and others
> >    - remove 'variant' test from most of The Guide.
> >    - add expiration dates for all deprecated calls.
> >  - update and review The Manual (doxygen)
> >  - add Quick/Full/Hardware References? (seems possible and worth doing)
> > - updates for configuration files:
> >  - c01.cfg and c02.cfg
> >  - others?
> >
> 
> What about the J-Link issues with various target in the thread "TMS470 
> Scripts"?
> TMS470:
> https://lists.berlios.de/pipermail/openocd-development/2009-May/007391.html
> USR8200 (IXP422):
> https://lists.berlios.de/pipermail/openocd-development/2009-May/007403.html
> STM32:
> https://lists.berlios.de/pipermail/openocd-development/2009-May/007406.html
> 
> For my short time experiences with OpenOCD/J-Link, it has been
> much more usable now. But it seems there are still quite some issues
> with J-Link (different versions). Maybe this will not make it to 0.2.0
> though.

At this point, it remains unclear to me what the problems might be, and
the v6 unit that I have to test works better than it has in the past.
Several major problems have been resolved, but I am not surprised that
the driver has not reached full stability and support. 

Unless Magnus or others have pending patches to test, this will require
more information and time to debug properly, so I do not think it is
reasonable to expect further work do be done on it for 0.2.0.  It would
be nice to find the bugs, but I think it is more than we can expect.

Certainly, the J-Link driver will remain on The List for future work.

Cheers,

Zach
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to