[ELDK] gdb does not connect to BDI2000

[Detlev Zundel]

Hi Dirk,

> I am trying to debug u-boot on a 460EX platform with ppc_4xxFP-gdb from
> ELDK 4.2 and BDI 2000.
>
> As soon as I try to connect I get:
>
> (gdb) tar rem 10.3.0.12:2001
> Remote debugging using 10.3.0.12:2001
> Remote 'g' packet reply is too long:
> 00069200c0261f90c024a4a800000001c024d2e800000000000000a1524c6199c0268c38
> 00021000229e8574000000003b99a747fffdff160ffb1900000000000ffa5eec0ffabef4
> 00000000000000000000000000000000000000000000000e000000000000000000000f60
> c0268dc0c0268cfcc026003400000008c0260000deadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
> deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefc00171740006920024a44f28
> c0006c08c001716420000007deadbeef
>
> Any ideas what I am doing wrong here?

The current gdb has the nasty habit of not taking its command name
seriously, i.e. the name you call the debugger is *not* the ultimate
configuration choice.  Rather "CROSS_COMPILE" overrides this.  Please be
sure that CROSS_COMPILE=ppc_4xxFP- and check again.

It is also helpful to check what architecture gdb thinks it debugs, so
check 

(gdb) show architecture 
The target architecture is set automatically (currently powerpc:403)

Cheers
  Detlev

-- 
Some mathematicians become so tense these days that they do not go to
sleep during seminars.
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de