remote debugging with m68k-stub
Quality Quorum
qqi@theworld.com
Wed Aug 7 07:22:00 GMT 2002
On Wed, 7 Aug 2002, Squal wrote:
> Hello!
>
> I have done all the remote target gdb instructions:
> - define all the low level routines
> - insert set_debug_traps(); and breakpoints(); at
> the beginning of the program
> - compiling stub and program together
>
> After that, I downloaded my program and the m68k-stub in the target.
> My problem is when I start the program in the remote target, the program
> stop and never restart (the halt indicator is set).
> Normally, the program will stop at the breakpoint (TRAP #1) and will
> continue after gdb be connected to the stub but the program seems to
> be stopped.
If you this is not the first time you are running gdb in this environment
check changes you made. If it is the first time it is quite possible that
you have conflict between you ROM monitor (I suspect this is what you call
target) initialization and gdb initialization.
>
> Somebody can help me ?
1. Use ICE if it is available
or
2. Trace the thing with characters sent to serial port.
>
> Thanks
>
> Pascal
>
There are simply no smart ways to debug initialization, also do not forget
to read you target doc, it is quite possible that they have some
debugging help.
Thanks,
Aleksey
More information about the Gdb
mailing list