Re: BDI-2000

Thanks Wolfgang,

You are right, my ethernet mac address was not passed in properly.
Furthermore, I had
too many ethernet device configured for this board.  Should be only one
ethernet devices.
Once I fixed the problem, my linux kernel is now up and running on the
custom board.

Thanks for all those who help.

As to the PPC native gdb, i don't see it in my distribution from timeSys.
Do you
have a suggestion as to where can i get a copy?

Thanks

Cecilia

-----Original Message-----
From: Wolfgang Denk [mailto:<redacted>]
Sent: Wednesday, January 08, 2003 4:09 PM
To: Muaddi, Cecilia
Cc: <redacted>
Subject: Re: BDI-2000


In message [ref]
you wrote:

So, after changed the kernel address to 0xc0000000 the kernel did
bootup with the following dump:

...
eth0: CPM ENET Version 0.2 on SCC1, 00:00:00:00:00:00
eth1: FEC ENET Version 0.2, FEC irq 3, addr 00:00:00:80:00:00

Ummm... does not look like valid MAC addresses to me.

Looking up port of RPC 100003/2 on 192.168.0.59
RPC: sendmsg returned error 101
portmap: RPC call returned error 101

errno=101 -- Network is unreachable

Looks like my IP has some problem.  I will like to use the BDI with the

ddd

It's more that your MAC address is bogus.

on my linux server.  When i start the ddd with the following command as
suggested
by the appnote
ddd -debugger gdb -gdb vmlinux

Which appnote? Doesn't it mention that you  need  to  run  a  PowerPC
version of GDB, either natively or a cross-GDB?

(gdb)target remote bdi:2001
Remote packet too long:
c00021a00040b..............

It seems there is a problem between the BDI and the DDD on my linux PC.  I
am running
redHat 8.0, GNU DDD 3.3.1 (i686-pc-linux-gnu)

The problem is that "gdb" will start the native GDB, which  does  not
work on PowerPC systems. You have to specify the name of your PowerPC
Cross-GDB.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/