This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: GDB with redboot


Tong Chi Wa wrote:
> 1. The host GDB will get "remote packets too long" when
>    connecting, over both serial and ethernet link. This should
>    be from the register dump command.
> 
> 2. On a serial link, the response time of the first memory dump
>    is longer than the following memory dumps. Snooping on the
>    serial link, I've found that there are two request packets
>    sent from the host for the first memory dump. It looks like
>    there is some kind of timeout mechanism on the host side.
> 
> 3. On the ethernet link, host GDB will stuck in the first memory
>    dump. I've checked that the target did respond to the 'm'
>    GDB command and send out the response packet. The target
>    still responds to ping packets so the target should not
>    miss any retry request packets from the host. Unlike the case
>    with the serial link, there is only one request packet sent
>    from the host.
> 
>   I'm not sure if this problem is on Redboot or GDB. Is there
> something need to configured differently for GDB to work with
> the eCos GDB stubs?

There shouldn't be. In the serial case, have you been able to determine
whether the stub actually received the data, and hence why the timeout
seems to happen?

The "remote packets too long" does sound like the register format that GDB
expects now is different from what it used to expect; or it may be a bug. I
can't give any more specific advice than that. Perhaps
gdb@sources.redhat.com may be helpful :-/.

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]