Hi, Le Fri, 24 Sep 2010 10:59:43 +0200, Drasko DRASKOVIC <[email protected]> a écrit : > > Both are compatible, or at least not very different (ie maybe only > > the JTAG register to which the commands are written may change). > > So I should get Milkymist sources, and examine JTAG code, then based > on this add OpenOCD target ?
The LM32 JTAG debugger is made of several parts: * the debug interface built into the LM32 processor which processes the debug commands. It is unmodified in Milkymist and therefore compatible with the original LM32. * the interface to the technology-dependent JTAG port to communicate the commands (also included in the LM32 core), which Michael ported from Lattice FPGAs to the Spartan6 in Milkymist (as well as Spartan3 for Das Labor's soc-lm32). * a monitor ROM that contains software stubs to implement some JTAG commands and provide debug exception handlers. It was originally a binary array part of LM32, but Michael rewrote it (source is in software/monitor and is GPL, ask Michael if you need another license) and it was made external on Milkymist (as a separate Wishbone bus peripheral, see cores/monitor). * there was also originally a PC trace module, but we have not ported it yet. Then you have the host-side software, e.g. OpenOCD. S. _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkym...@freenode Webchat: www.milkymist.org/irc.html Wiki: www.milkymist.org/wiki
