From: Thomas A. <tan...@gr...> - 2003-06-20 17:24:32
|
On Fri, Jun 20, 2003 at 07:44:51AM +0200, Marcel Telka wrote: > JTAG Tools now uses Boundary Scan capability of the JTAG only. This > capability should be included in all chips with JTAG support. So, all > chips could be supported. Your CPU (Micrel/Kendin KS8695) is not > supported OOTB by JTAG Tools, but it is quite easy to add support for > it (if it has Boundary Scan). I just contacted the Micrel FAE in the UK - apparently boundary scan is *not* supported. This is what he said: "Our JTAG does not support boundary scan. But it does not prevent you from using GNU debugger tools. We don't have registers for configuring JTAG, you should just plug in the ICE (hardware) and it should work." Am I correct in saying that "jtag debuuging" has absolutely nothing to do with jtag - it just shares the same I/O lines ? Is there any standard when it comes to jtag debugging ? I mean how does one find out how to drive the I/O lines to set breakpoints, single-step etc etc ? Regards, Thomas |