Coocox CoDebugger v0.12 has been released. It supports CDT project and Cobuilder project(A ELF file built by GCC tools is also supported).
It integrates Flash Programmer base on CoLink. Before debugging with Codebugger,a colink is essential.But this is not a problem, Colink is open, Everyone can make it.
Colink: http://www.coocox.org/Colink.htm
Codebugger: http://www.coocox.org/CooCox_CoDebugger.htm
Is this bypassing the normal OpenOCD step in the debugger? Or is it just the Eclipse layer to perform the normal program/debug magic with OpenOCD?
Coocox has no relationship with OpenOCD. It is a new debug tool build on Eclipse with gcc+gcc server.
And we do a lot job to adjust Eclipse interface to adapt developer’s habit, it may give you some surprise.
Try it, and you will love it.
Is your debugger compatible with Amontec Jtagkey, olimex ARM-USB-xyz or others ???
Angelo
We design gcc-server by ourselves.
Ok for the software part. But I don’t want to build/buy another JTAG interface just to try your softwares. That’s why I asked about compatibility with existing tools from Amonteg, Olimex or others.
Angelo
I am sorry that I misunderstood what you mean.
Now CoDebug is incompatible with other another JTAG interface except Colink. But for later we will open the API interface.
Thank you for your attention.
I just looked over the project and the schematic and it appears the CooCox Colink is just another FT2232-based debugger such as the JTAGKey, Turtelizer, Flyswatter, OOCDLink, or others.
The project mentions their Debugger is compatible with the Luminary ICDI interface (also FT2232-based):
http://www.coocox.org/CooCox_CoDebugger.htm
Compare the Colink schematic:
http://www.coocox.org/images/Circuit%20 … agramc.pdf
with the Luminary ICDI interface schematic on Pg.31 of the “LM3S9B96 Development Kit User’s Manual” found at:
http://www.luminarymicro.com/products/dk-lm3s9b96.html
It also appears Colink’s JTAG pinout is compatible with the Flyswatter. Schematic at:
http://www.tincantools.com/assets/FLYSWATTER_REV-B.pdf
So it should just be a matter of programming your particular FT2232-based debugger’s EEPROM with Colink’s VID/PID.
I also saw the interface is based on FT2232, differences are probably in signals assignation on FT2232 outputs.
Just my 2 cents: Why reinvent the wheel, and not create something compatible with existing designs, so everyone could instantly try the software. For me, the only brake to not try the software, wich look great, is not having the right jtag interface.
Angelo
Yes,Coocox link is based on FT2232. Of course we want to compatible with all existing designs, but there are so much link, but we have been compatible with Luminary ICDI interface now.
There will been more compatible existing designs later,thanks!