From: Gideon Zweijtzer (gideonz_at_dds.nl)
Date: 2002-04-22 15:48:23
|LA> That IS really cool, Just the thought of debugging a program *while* it
|LA> is running... (and all the spectatular lockups you will accidentally
get
|LA> when you fudge the wrong instruction!) ;-) Those traps and triggers
|LA> would be useful too for debugging.
|
|just as a sidenode.... if you implement that according to the
|JEDEC/JTAG standard, you had tons of ready-made applications for
|debugging.
AFAIK, the JTAG standard only says something about the access to the chip by
means of the dedicated JTAG pins. I don't think there is a standard for
having access to CPU registers or trace possibilities. Boundary scan
structures are captured in the so called .bsd files. Is there a standard
JTAG command description file for the internal workings? I have never seen
it, but of course that doesn't mean that it doesn't exist.
Gideon
PS. for the people who are interested: I only implemented two commands so
far:
=> 'R' <addr hi> <addr low> <length>
<= <data0> <data1> ...
=> 'W' <addr hi> <addr low> <length> <data0> <data1> ...
<= [none]
=> others
<= '?'
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail 2.1.4.