Re: [Openocd-development] Switching to Jim Tcl release
Going twice... I'll be merging this beginning of next week not to ruin anyones(especially mine! :-) weekend if there is any fallout. It would mainly be with documenting and build procedures and laying out some bread-crumbs to follow. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
Going once... -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
Øyvind Harboe wrote: Going once... Acked-by: Peter Stuge pe...@stuge.se ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
I've gotten feedback that this builds under Cygwin and -mno-cygwin. Unless I hear protests, I plan to merge this when Jim Tcl is released. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
Øyvind Harboe wrote: I've gotten feedback that this builds under Cygwin and -mno-cygwin. Unless I hear protests, I plan to merge this when Jim Tcl is released. Acked-by: Peter Stuge pe...@stuge.se ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Switching to Jim Tcl release
Hi all, there is a major upcoming release of Jim Tcl. The impact on OpenOCD is that we can switch to using Jim Tcl as a normal module rather than embedding and maintaining Jim Tcl inside OpenOCD. I've made the modifications necessary to start testing w/OpenOCD and added Jim Tcl as a submodule in the oharboe/jimtcl branch. 1. To build install Jim Tcl for use with OpenOCD: cd openocd git remote add oharboe http://repo.or.cz/r/openocd/oharboe.git git fetch oharboe git checkout oharboe/jimtcl git submodule init git submodule update cd jimtcl # The NVP stuff is actually Jim Tcl project maintaining an # OpenOCD invention ./configure --with-jim-ext=nvp make make install 2. Build OpenOCD as usual 3. To check that OpenOCD now uses Jim Tcl 0.63 (instead of 0.51): openocd -c info version = Open On-Chip Debugger 0.5.0-dev-00559-g471a462 (2010-10-15-09:55) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 0.63 Error: Debug Adapter has to be specified, see interface command Runtime Error: Command handler execution failed in procedure 'init' -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
Hi all, there is a major upcoming release of Jim Tcl. The impact on OpenOCD is that we can switch to using Jim Tcl as a normal module rather than embedding and maintaining Jim Tcl inside OpenOCD. I've made the modifications necessary to start testing w/OpenOCD and added Jim Tcl as a submodule in the oharboe/jimtcl branch. 1. To build install Jim Tcl for use with OpenOCD: cd openocd git remote add oharboe http://repo.or.cz/r/openocd/oharboe.git git fetch oharboe git checkout oharboe/jimtcl git submodule init git submodule update cd jimtcl # The NVP stuff is actually Jim Tcl project maintaining an # OpenOCD invention ./configure --with-jim-ext=nvp make make install 2. Build OpenOCD as usual 3. To check that OpenOCD now uses Jim Tcl 0.63 (instead of 0.51): openocd -c info version = Open On-Chip Debugger 0.5.0-dev-00559-g471a462 (2010-10-15-09:55) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 0.63 Error: Debug Adapter has to be specified, see interface command Runtime Error: Command handler execution failed in procedure 'init' The main advantage of the JIM TCL was to embed it in OpenOCD. Now, with new JIM TCL as module, should we use pure TCL instead , see TCL / TK ! Regards, Laurent http://www.amontec.com Amontec JTAGkey USB JTAG CABLE ARM Debugger et Flasher ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Switching to Jim Tcl release
The main advantage of the JIM TCL was to embed it in OpenOCD. And it is still embedded. No change. This is about how Jim and OpenOCD is built and who maintains Jim Tcl. By using the release, OpenOCD no longer needs to maintain Jim Tcl and we get some missing features, e.g arrays. Not that Jim Tcl needs much maintenance or that we're sorely missing more Jim Tcl features in the first place from OpenOCD's point of view. To create a dependency on Tcl and Tcl/Tk is a different kettle of fish entirely. -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
