Re: [ECOS] GDB remote debug problem ??

[Jonathan Larmour <jlarmour at redhat dot com>]

??? wrote:
>     Thank you for your reply!! I describe my steps
> 1. Reset my borad by pressing the reset buttom.
> 2. Run powerpc-eabi-gdb
> 3. press the 'RUN' buttom
> 4. select the hello.exe I want to debug
> 5. select target Remote TCP & set breakpoint at main
> 6. download OK & I see my serial console print $T ...
> 7. I can't do anything but press the stop buttom on powerpc-eabi-gdb
> 8. powerpc-eabi-gdb get no response from from by board & dettach from it.
> 
> But if step 5. I select Remote serial , then everything will be OK. I can
> stop
> the hello program at main and run step by step.
> What problem may it happen?? Is my ethernet driver's problem?? or something
> ??
> What point may I check??

Ah I think I understand what you are describing - you are connecting via
TCP to RedBoot. But then when the board hits a breakpoint, this breakpoint
is being reported over the *serial* line, not the TCP line.

In that case, firstly make sure you are using an up-to-date anonymous CVS
repository. Secondly, in your downloaded application's configuration, have
you done anything like enable included GDB stubs, or claimed virtual
vectors?

Lastly in your port, have you done anything in the hal_diag init that would
cause it to claim the debug channel? Perhaps compare your diag init with
that of another known working target, e.g. look at
hal/arm/sa11x0/var/current/src/hal_diag.c

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine