On Dec 3, 2008, at 12:17 PM, Øyvind Harboe wrote:
Either it should be part of the main OpenOCD source base or it should be separate project. If it is just a flash, interface, and target driver, then it should just be part of the mainline source base. If it is more thanthat, it isn't really part of OpenOCD.It *is* part of the main openocd source base. This is just a technicality w.r.t. avoiding excessive download sizes for those that don't need those bits.
It looks like it contains the build environment for the zy1000 firmware which _uses_ OpenOCD but isn't part of OpenOCD.
It is also an embedded version of openocd, so it is built very differentlyfrom openocd hosted on a developer OS.
Exactly, it isn't part of OpenOCD, but rather a user of OpenOCD. Just because OpenOCD does a release doesn't mean that the zy1000 build environment needs to be changed. For example, OpenOCD might release 1.0.1 that contains a big bug that makes the zy1000 non-functional. It is completely reasonable in that case for the zy1000 build scripts to use OpenOCD 1.0 instead with no real impact.
The ZY1000 is a commercial product built on top of OpenOCD. The scripts and files necessary to build the ZY1000 firmware are not part of OpenOCD. They are part of the ZY1000 software. OpenOCD is simply a component of the ZY1000 software.
-- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer
-- Rick Altherr [EMAIL PROTECTED]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
