The problem with starting up PalmDebugger on the Tungsten/T is an issue with
the serial/USB Y cable I am using. Reset works normally if I disconnect the
Y
cable before doing the reset, then reconnect the serial portion. USB
debugging
doesn't work, but at least I have a consistent serial debugging capability.
The problem with MOVEM.W is still real. Took out another one...
Tracing has a bizare problem. Given the sequence
jsr foo
move.w #1, d0
move.w #2, d1
move.w #3.d2
When you are stopped in the debugger at the JSR, step over the JSR with F10,
it looks normal (new instruction is the "move.w #1...". Do another step
with
F10 and the debugger steps to the "move.w #3...". It does not stop and show
the
"move.w #2....", although register d1 will now contain 2 (the skipped
instruction
is executed, but not displayed by the debugger. The F10 over the jsr has
left
some residual status in the debugger that causes the next step to execute 2
instructions.
ROM routine names are not displayed. Most show as "ILLEGAL ADDRESS", or
just _TD xxx. Obviously there are no routine names following the RTS
instructions
since the 68k is just a figment of our imagination...
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
