Re: GDB using Angel error on an OKI board

[Grant Edwards <grante at visi dot com>]

> I have tried this command "set rdiheatbeat off" but the result
> is the same, with the "maint rdilogen on" as :

> tx: [T=0 L=36] 03 01 00 01 05 00 03 00 00 00 00 00 ff ff ff ff ff ff ff ff 01 00 00 00 00 c0 00 00 01 00 00 00 80 25 00 00
> R=00030005 H->T CI_HBOOT:  ADP_ParamNegotiate 00000001 0000c000 00000001 00002580
> rx: [T=0 L=36] 03 02 01 01 05 00 03 80 00 00 00 00 ff ff ff ff ff ff ff ff 00 00 00 00 01 00 00 00 00 c0 00 00 80 25 00 00
> R=80030005 H<-T CI_HBOOT:  ADP_ParamNegotiate 00000000 00000001 0000c000 00002580
> tx: [T=0 L=20] 03 02 00 01 06 00 03 00 00 00 00 00 ff ff ff ff ff ff ff ff 
> R=00030006 H->T CI_HBOOT:  ADP_LinkCheck

Ah yes.  That link check command isn't sent by the heartbeat
feature -- it's part of the serial-port negotiation sequence.
It's possible for both ends to switch baud rates after the
initial parmeter negotiation, so a link check is sent to make
sure both ends are still talking.

The board isn't responding to the link check command.  It is
supposed to reply with another link check frame.  [At least
that is what happens with the ADP devices I have.]

I suppose you could go into the rdi code and try to skip over
that step in the start-up process to see if the board handles
the rest of the ADP commands correctly.

Or, you could try to capture the sequence used by the debugger
that works.  

[Please cc: the mailing list, since it is the collective memory
of the gdb community.  We certainly don't want to depend upon
either my memory or my record-keeping skills.]

-- 
Grant Edwards
grante@visi.com