Re: Re: Ethernet Trouble

Re: Re: Ethernet Trouble

[clark]

At 02:31 AM 10/7/00 +0200, you wrote:
>In message <1.5.4.32.20001006222031.006b6ab0@pop.esteem.com> you wrote:
>>
>> Looking up port of RPC 100003/2 on 100.100.100.11
>> Looking up port of RPC 100005/1 on 100.100.100.11
>> VFS: Mounted root (NFS filesystem).
>> Freeing unused kernel memory: 40k init
>>
>> It hangs here.
>>
>> It seems like it is not running init and/or loading inittab.
>>
>> Whats up with this?????
>
>You're running vwith Root over NFS, so you can use  a  sniffer  (like
>ethereal)  to  check  which  files  it's  trying to access. Check all
>failing accesses...
>
>Either it can't find init, or it's a shared library problem, or  your
>console device is missing, or ...

        I did some tracing with ethereal. The first thing it does after
mounting the NFS drive look up the dev directory then the console. Next it
looks in the sbin directory (realy just a link to the bin directory) and
loads the init program. Finally it goes to the lib directory an loads
ld.so.1 (which is a link to ld-2.1.3.so). After this I can't decipher the
binary messages in the packets. Then it quits.

        Right now I think that it can't talk to the console or init uses a
function in ld.so.1 to spit a message to the console and is failing to load
the library correctly. Does PPCBOOT tell the kernel to use its console or do
I need to do that somehow? I have tried to stick "console=/dev/ttyS00" in
the bootargs but then I don't get any messages after the uncompresssing
kernel message.

        I am using Hardhat version 1.2 for my development and using thier
target directory for my NFS.

>You may install a STATICALLY linked shell (like the standalone  shell
>"sash" or the simple shell "ash") and pass the boot arguments
>
>	... init=/bin/sash
>or	... init=/bin/ash
>
>This will make the situation less complex...

        Tried this. It looked up the /dev/console just as before then It
loaded sash but, I still didn't get anything on the console screen.


>
>Wolfgang Denk
>
>--
>Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
>Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
>Any technology distinguishable from magic is insufficiently advanced.
>

        Sorry to be such a pain in your side lately.

        Conn Clark


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

Re: Ethernet Trouble

[Wolfgang Denk]

In message <1.5.4.32.20001010000239.006b54d8@pop.esteem.com> Conn Clark wrote:
>
> >Either it can't find init, or it's a shared library problem, or  your
> >console device is missing, or ...
...
>         Right now I think that it can't talk to the console or init uses a
> function in ld.so.1 to spit a message to the console and is failing to load

So what is /dev/console on your system?

I know that it used to be  a  symlink  to  /dev/ttyS0  on  sme  older
systems,  which doesn't work any more. Make sure you have a character
device major 5 minor 1, i. e. something like that:

crw-r--r--   1 root     root       5,   1 Mar 22  2000 /dev/console


Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
He'd been wrong, there _was_ a light at the end of the tunnel, and it
was a flamethrower.                         - Terry Pratchett, _Mort_

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

Re: Ethernet Trouble

[Michael Pruznick]

>         Right now I think that it can't talk to the console or init uses a
> function in ld.so.1 to spit a message to the console and is failing to load
> the library correctly. Does PPCBOOT tell the kernel to use its console or do
> I need to do that somehow? I have tried to stick "console=/dev/ttyS00" in
> the bootargs but then I don't get any messages after the uncompresssing
> kernel message.
Unless its a typo, try "console=/dev/ttyS0" (1 zero, not 2).

Also, if its just a console print problem, you should still be able to
telnet into the box and do things like "cat <file> > /dev/ttyS0" and
"od -x /dev/ttyS0", just to show that the serial device is good and
the problem is with the console device attached to the serial port.

Your console,tty should look something like this:

> ls -l console ttyS0
crw-------   1 root     root       5,   1 Aug  4 10:34 console
crw-------   1 root     tty        4,  64 Aug  4 10:34 ttyS0

I also like to use the following inttab file, instead of
default we ship.   It means there are more places for problems
to exist, but I've seen direct bash drop errors that getty
picks up, like "serial input buffer overrun".

> cat etc/inittab
id:3:initdefault:

# System initialization.
si::sysinit:/etc/rc.sysinit

# Single user shell
1:2345:respawn:/sbin/getty console DT9600 linux

l0:0:wait:/sbin/halt -dip
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/sbin/reboot -dip

> cat etc/default/getty
CLEAR=NO


--
Michael Pruznick, michael_pruznick@mvista.com, 408-328-9215
MontaVista Software, 490 Potrero Ave, Sunnyvale, CA 94085
http://www.hardhatlinux.com, V:408-328-9200, F:408-328-9204

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

Ethernet Trouble

[clark]

Hello All,

        I am trying to port the networking portion of linux to work with our
board. Our board uses a MPC850 and SCC2 as its ethernet interface ( almost
identical to the rpxlite ).

 Port A, bit 13 - SCC2 Ethernet Rx
 Port A, bit 12 - SCC2 Ethernet Tx
 Port A, bit  6 (CLK2) - Ethernet Tx Clk
 Port A, bit  4 (CLK4) - Ethernet Rx Clk
 Port B, bit 18 (RTS2) - Ethernet Tx Enable
*Port B, bit 17 - Ethernet Loopback Enable
*Port B, bit 16 - Ethernet Full Duplex Disable
 Port C, bit  8 (CD2) - Ethernet Rx Enable
 Port C, bit  9 (CTS2) - SCC Ethernet Collision

* Differs from rpxlite


        I am using ppcboot for our boot rom and compile the kernel targeting
a MBX board. I have modified the mbx.h file with a customized board info
structure to work with ppcboot. I have also stuck a #define ESTEEM192E so I
could stick my mods within the #ifdef CONFIG_MBX contained in the kernel as
needed. The only mods I think I need to make are in commproc.h and enet.c. I
have made them as follows...

from /arch/ppc/m8xx_io/commproc.h

Code was this ........

#ifdef CONFIG_MBX
/* Bits in parallel I/O port registers that have to be set/cleared
 * to configure the pins for SCC1 use.  The TCLK and RCLK seem unique
 * to the MBX860 board.  Any two of the four available clocks could be
 * used, and the MPC860 cookbook manual has an example using different
 * clock pins.
 */
#define PA_ENET_RXD	((ushort)0x0001)
#define PA_ENET_TXD	((ushort)0x0002)
#define PA_ENET_TCLK	((ushort)0x0200)
#define PA_ENET_RCLK	((ushort)0x0800)
#define PC_ENET_TENA	((ushort)0x0001)
#define PC_ENET_CLSN	((ushort)0x0010)
#define PC_ENET_RENA	((ushort)0x0020)

/* Control bits in the SICR to route TCLK (CLK2) and RCLK (CLK4) to
 * SCC1.  Also, make sure GR1 (bit 24) and SC1 (bit 25) are zero.
 */
#define SICR_ENET_MASK	((uint)0x000000ff)
#define SICR_ENET_CLKRT	((uint)0x0000003d)

#endif

Code is now this ........

#ifdef CONFIG_MBX
#ifndef ESTEEM192E
/* Bits in parallel I/O port registers that have to be set/cleared
 * to configure the pins for SCC1 use.  The TCLK and RCLK seem unique
 * to the MBX860 board.  Any two of the four available clocks could be
 * used, and the MPC860 cookbook manual has an example using different
 * clock pins.
 */
#define PA_ENET_RXD	((ushort)0x0001)
#define PA_ENET_TXD	((ushort)0x0002)
#define PA_ENET_TCLK	((ushort)0x0200)
#define PA_ENET_RCLK	((ushort)0x0800)
#define PC_ENET_TENA	((ushort)0x0001)
#define PC_ENET_CLSN	((ushort)0x0010)
#define PC_ENET_RENA	((ushort)0x0020)

/* Control bits in the SICR to route TCLK (CLK2) and RCLK (CLK4) to
 * SCC1.  Also, make sure GR1 (bit 24) and SC1 (bit 25) are zero.
 */
#define SICR_ENET_MASK	((uint)0x000000ff)
#define SICR_ENET_CLKRT	((uint)0x0000003d)

#else
/* ESTEEM192E
 * This ENET stuff is for the MPC850 with ethernet on SCC2. This
 * is very similar to the RPX-Lite configuration.
 * Note TENA , LOOPBACK , FDPLEX_DIS on Port B.
 */
#define PA_ENET_RXD	((ushort)0x0004)
#define PA_ENET_TXD	((ushort)0x0008)
#define PA_ENET_TCLK	((ushort)0x0200)
#define PA_ENET_RCLK	((ushort)0x0800)
#define PB_ENET_TENA	((uint)0x00002000)
#define PC_ENET_CLSN	((ushort)0x0040)
#define PC_ENET_RENA	((ushort)0x0080)

#define SICR_ENET_MASK	((uint)0x0000ff00)
#define SICR_ENET_CLKRT	((uint)0x00003d00)

#define PB_ENET_LOOPBACK ((uint)0x00004000)
#define PB_ENET_FDPLEX_DIS ((uint)0x00008000)

#endif





from /arch/ppc/m8xx_io/enet.c  in function cpm_enet_init

Code was this ........

#ifdef CONFIG_MBX
	immap->im_ioport.iop_pcpar |= PC_ENET_TENA;
	immap->im_ioport.iop_pcdir &= ~PC_ENET_TENA;
#endif

Code is now this ........

#ifdef CONFIG_MBX
#ifndef ESTEEM192E

/* MBX stuff */
	immap->im_ioport.iop_pcpar |= PC_ENET_TENA;
	immap->im_ioport.iop_pcdir &= ~PC_ENET_TENA;

#else

/* ESTEEM192E stuff */
	cp->cp_pbpar |= PB_ENET_TENA;  /* same as rpxlite */
	cp->cp_pbdir |= PB_ENET_TENA;  /* same as rpxlite */

/*** Make sure that the loopback and full duplex are disabled
     just like the rpxlite code. ***/
	cp->cp_pbpar &= ~(PB_ENET_LOOPBACK | PB_ENET_FDPLEX_DIS);
	cp->cp_pbdir |= PB_ENET_LOOPBACK | PB_ENET_FDPLEX_DIS;
	cp->cp_pbdat &= ~PB_ENET_LOOPBACK;
	cp->cp_pbdat |= PB_ENET_FDPLEX_DIS;

#endif
#endif


This is what it looks like when booting.


Initializing...
  CPU:   XPC850xxZTB at 49 MHz: 2 kB I-Cache 1 kB D-Cache
  Board: Esteem 192E
  DRAM:
bank 0 size 8388608
bank 1 size 8388608
16 MB
Command "go": 0x4000dd28 => 0x00fedd28
Command "bootm": 0x4000e8dc => 0x00fee8dc
Command "net": 0x4000f3d4 => 0x00fef3d4
Command "loads": 0x4000ddd8 => 0x00feddd8
Command "md": 0x4000cf74 => 0x00fecf74
Command "mm": 0x4000d1f8 => 0x00fed1f8
Command "nm": 0x4000d228 => 0x00fed228
Command "mw": 0x4000d25c => 0x00fed25c
Command "cp": 0x4000d3e8 => 0x00fed3e8
Command "crc32": 0x4000dabc => 0x00fedabc
Command "base": 0x4000d610 => 0x00fed610
Command "printenv": 0x4000f56c => 0x00fef56c
Command "setenv": 0x4000f6e4 => 0x00fef6e4
Command "saveenv": 0x4000f998 => 0x00fef998
Command "bdinfo": 0x4000db70 => 0x00fedb70
Command "flinfo": 0x4000e0cc => 0x00fee0cc
Command "iminfo": 0x4000ee4c => 0x00feee4c
Command "erase": 0x4000e1a4 => 0x00fee1a4
Command "protect": 0x4000e4dc => 0x00fee4dc
Command "loop": 0x4000d674 => 0x00fed674
Command "mtest": 0x4000d820 => 0x00fed820
Command "icache": 0x4000cdb8 => 0x00fecdb8
Command "dcache": 0x4000ce5c => 0x00fece5c
Command "reset": 0x40013528 => 0x00ff3528
Command "version": 0x4000cc34 => 0x00fecc34
Command "help": 0x4000cc80 => 0x00fecc80
Command "?": 0x4000cc80 => 0x00fecc80
  FLASH:  4 MB
Hit any key to stop autoboot:  0
## Booting Linux kernel at 40020000 ...
   Image Name:   2.2.14 for EST192E
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    413162 Bytes = 403 kB = 0 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Linux version 2.2.14 (root@pokey.esteem.com) (gcc version 2.95.2 19991030 (2.9
5.3 prerelease/franzo)) #14 Thu Oct 5 13:24:22 PDT 2000
Boot arguments: root=/dev/nfs rw nfsaddrs=100.100.100.21:100.100.100.14 nfsroo
t=100.100.100.14:/targ
time_init: decrementer frequency = 183750000/60
Calibrating delay loop... 48.74 BogoMIPS
Memory: 15120k available (748k kernel code, 476k data, 40k init) [c0000000,c10
00000]
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 16384 bhash 16384)
Starting kswapd v 1.5
CPM UART driver version 0.03
ttyS00 at 0x0280 is a SMC
ttyS01 at 0x0380 is a SMC
pty: 256 Unix98 ptys configured
RAM disk driver initialized:  16 RAM disks of 4096K size
loop: registered device at major 7
NET4: Ethernet Bridge 007 for NET4.0
early initialization of device brg0 is deferred
eth0: CPM ENET Version 0.2, 00:10:ec:00:1b:ba
PPP: version 2.3.7 (demand dialling)
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
brg0: network interface for Ethernet Bridge 007/NET4.0
brg0: generated MAC address FE:FD:00:30:24:76
brg0: attached to bridge instance 0
Sending BOOTP and RARP requests............. timed out!
IP-Config: Auto-configuration of network failed.
dev_close: bug eth0 still running
Looking up port of RPC 100003/2 on 100.100.100.14
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
portmap: server 100.100.100.14 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 100.100.100.14
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101

Blah..Blah..Blah..Blah..Blah..Blah..... reboot in 180 seconds

        I know that my BOOTP and NFS server work because I have tested it
with another machine. I don't know if the BOOTP requests are making it to
the server okay.

        At least some of the code works because I can see the TENA go high
and bits being sent (may not be the correct bits ;-) on the transmit line
going to the PHY(I can also see a signal going to the jack from the PHY).
When a packet (any ethernet activity from the net) comes in through the PHY
I can see the RENA line go high and bits coming in on the receive line.

        I noticed that the rpxlite has a colision test disable line in its
BSCR.  Is this needed to get the transmit to work right?

Note: I have not ruled out the PHY to Jack interface as the problem.

Any help appreciated. Many MAny thanks in advance.

        Conn Clark


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

Re: Ethernet Trouble

[Matthew Locke]

clark@esteem.com wrote:
> Sending BOOTP and RARP requests............. timed out!
> IP-Config: Auto-configuration of network failed.
> dev_close: bug eth0 still running
> Looking up port of RPC 100003/2 on 100.100.100.14
> RPC: sendmsg returned error 101
> RPC: sendmsg returned error 101
>

looks like a config problem.  trying turning off RARP in the kernel.

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

Re: Ethernet Trouble

[Jerry Van Baren]

Get ethereal (ethernet sniffer) and listen in to your ethernet.  You
can find problems very quickly by watching what packets get sent, what
is in them, and how the server responds.

http://ethereal.zing.org/

The packet filtering interface is pretty funky until you figure it
out.  I generally have one per target machine (i.e. the host being
debugged).  Set the filter name to the host name and the filter string
to "host w.x.y.z" (no quotes, use the proper IP address for w.x.y.z) to
capture all packets going to or from the given host.

Cliff Notes:
* Click "Capture"
* In the capture dialog, click "Filter"
* Fill in the host name and the "host w.x.y.z" strings in the filter dialog
* Click "New"
Now you should be ready to capture.  The "filter" line will be filled
in with "host w.x.y.z" and the filter will be saved for next time you
need to use it.

Incidentally, you have to be root to sniff packets.

gvb


At 08:56 AM 10/6/00 -0700, clark@esteem.com wrote:

>Hello All,
>
>         I am trying to port the networking portion of linux to work
> with our
>board. Our board uses a MPC850 and SCC2 as its ethernet interface ( almost
>identical to the rpxlite ).
>
>  Port A, bit 13 - SCC2 Ethernet Rx
>  Port A, bit 12 - SCC2 Ethernet Tx
>  Port A, bit  6 (CLK2) - Ethernet Tx Clk
>  Port A, bit  4 (CLK4) - Ethernet Rx Clk
>  Port B, bit 18 (RTS2) - Ethernet Tx Enable
>*Port B, bit 17 - Ethernet Loopback Enable
>*Port B, bit 16 - Ethernet Full Duplex Disable
>  Port C, bit  8 (CD2) - Ethernet Rx Enable
>  Port C, bit  9 (CTS2) - SCC Ethernet Collision
>
>* Differs from rpxlite
>
>
>         I am using ppcboot for our boot rom and compile the kernel
> targeting
>a MBX board. I have modified the mbx.h file with a customized board info
>structure to work with ppcboot. I have also stuck a #define ESTEEM192E
>so I
>could stick my mods within the #ifdef CONFIG_MBX contained in the
>kernel as
>needed. The only mods I think I need to make are in commproc.h and
>enet.c. I
>have made them as follows...
>
>from /arch/ppc/m8xx_io/commproc.h
>
>Code was this ........
>
>#ifdef CONFIG_MBX
>/* Bits in parallel I/O port registers that have to be set/cleared
>  * to configure the pins for SCC1 use.  The TCLK and RCLK seem unique
>  * to the MBX860 board.  Any two of the four available clocks could be
>  * used, and the MPC860 cookbook manual has an example using different
>  * clock pins.
>  */
>#define PA_ENET_RXD     ((ushort)0x0001)
>#define PA_ENET_TXD     ((ushort)0x0002)
>#define PA_ENET_TCLK    ((ushort)0x0200)
>#define PA_ENET_RCLK    ((ushort)0x0800)
>#define PC_ENET_TENA    ((ushort)0x0001)
>#define PC_ENET_CLSN    ((ushort)0x0010)
>#define PC_ENET_RENA    ((ushort)0x0020)
>
>/* Control bits in the SICR to route TCLK (CLK2) and RCLK (CLK4) to
>  * SCC1.  Also, make sure GR1 (bit 24) and SC1 (bit 25) are zero.
>  */
>#define SICR_ENET_MASK  ((uint)0x000000ff)
>#define SICR_ENET_CLKRT ((uint)0x0000003d)
>
>#endif
>
>Code is now this ........
>
>#ifdef CONFIG_MBX
>#ifndef ESTEEM192E
>/* Bits in parallel I/O port registers that have to be set/cleared
>  * to configure the pins for SCC1 use.  The TCLK and RCLK seem unique
>  * to the MBX860 board.  Any two of the four available clocks could be
>  * used, and the MPC860 cookbook manual has an example using different
>  * clock pins.
>  */
>#define PA_ENET_RXD     ((ushort)0x0001)
>#define PA_ENET_TXD     ((ushort)0x0002)
>#define PA_ENET_TCLK    ((ushort)0x0200)
>#define PA_ENET_RCLK    ((ushort)0x0800)
>#define PC_ENET_TENA    ((ushort)0x0001)
>#define PC_ENET_CLSN    ((ushort)0x0010)
>#define PC_ENET_RENA    ((ushort)0x0020)
>
>/* Control bits in the SICR to route TCLK (CLK2) and RCLK (CLK4) to
>  * SCC1.  Also, make sure GR1 (bit 24) and SC1 (bit 25) are zero.
>  */
>#define SICR_ENET_MASK  ((uint)0x000000ff)
>#define SICR_ENET_CLKRT ((uint)0x0000003d)
>
>#else
>/* ESTEEM192E
>  * This ENET stuff is for the MPC850 with ethernet on SCC2. This
>  * is very similar to the RPX-Lite configuration.
>  * Note TENA , LOOPBACK , FDPLEX_DIS on Port B.
>  */
>#define PA_ENET_RXD     ((ushort)0x0004)
>#define PA_ENET_TXD     ((ushort)0x0008)
>#define PA_ENET_TCLK    ((ushort)0x0200)
>#define PA_ENET_RCLK    ((ushort)0x0800)
>#define PB_ENET_TENA    ((uint)0x00002000)
>#define PC_ENET_CLSN    ((ushort)0x0040)
>#define PC_ENET_RENA    ((ushort)0x0080)
>
>#define SICR_ENET_MASK  ((uint)0x0000ff00)
>#define SICR_ENET_CLKRT ((uint)0x00003d00)
>
>#define PB_ENET_LOOPBACK ((uint)0x00004000)
>#define PB_ENET_FDPLEX_DIS ((uint)0x00008000)
>
>#endif
>
>
>
>
>
>from /arch/ppc/m8xx_io/enet.c  in function cpm_enet_init
>
>Code was this ........
>
>#ifdef CONFIG_MBX
>         immap->im_ioport.iop_pcpar |= PC_ENET_TENA;
>         immap->im_ioport.iop_pcdir &= ~PC_ENET_TENA;
>#endif
>
>Code is now this ........
>
>#ifdef CONFIG_MBX
>#ifndef ESTEEM192E
>
>/* MBX stuff */
>         immap->im_ioport.iop_pcpar |= PC_ENET_TENA;
>         immap->im_ioport.iop_pcdir &= ~PC_ENET_TENA;
>
>#else
>
>/* ESTEEM192E stuff */
>         cp->cp_pbpar |= PB_ENET_TENA;  /* same as rpxlite */
>         cp->cp_pbdir |= PB_ENET_TENA;  /* same as rpxlite */
>
>/*** Make sure that the loopback and full duplex are disabled
>      just like the rpxlite code. ***/
>         cp->cp_pbpar &= ~(PB_ENET_LOOPBACK | PB_ENET_FDPLEX_DIS);
>         cp->cp_pbdir |= PB_ENET_LOOPBACK | PB_ENET_FDPLEX_DIS;
>         cp->cp_pbdat &= ~PB_ENET_LOOPBACK;
>         cp->cp_pbdat |= PB_ENET_FDPLEX_DIS;
>
>#endif
>#endif
>
>
>This is what it looks like when booting.
>
>
>Initializing...
>   CPU:   XPC850xxZTB at 49 MHz: 2 kB I-Cache 1 kB D-Cache
>   Board: Esteem 192E
>   DRAM:
>bank 0 size 8388608
>bank 1 size 8388608
>16 MB
>Command "go": 0x4000dd28 => 0x00fedd28
>Command "bootm": 0x4000e8dc => 0x00fee8dc
>Command "net": 0x4000f3d4 => 0x00fef3d4
>Command "loads": 0x4000ddd8 => 0x00feddd8
>Command "md": 0x4000cf74 => 0x00fecf74
>Command "mm": 0x4000d1f8 => 0x00fed1f8
>Command "nm": 0x4000d228 => 0x00fed228
>Command "mw": 0x4000d25c => 0x00fed25c
>Command "cp": 0x4000d3e8 => 0x00fed3e8
>Command "crc32": 0x4000dabc => 0x00fedabc
>Command "base": 0x4000d610 => 0x00fed610
>Command "printenv": 0x4000f56c => 0x00fef56c
>Command "setenv": 0x4000f6e4 => 0x00fef6e4
>Command "saveenv": 0x4000f998 => 0x00fef998
>Command "bdinfo": 0x4000db70 => 0x00fedb70
>Command "flinfo": 0x4000e0cc => 0x00fee0cc
>Command "iminfo": 0x4000ee4c => 0x00feee4c
>Command "erase": 0x4000e1a4 => 0x00fee1a4
>Command "protect": 0x4000e4dc => 0x00fee4dc
>Command "loop": 0x4000d674 => 0x00fed674
>Command "mtest": 0x4000d820 => 0x00fed820
>Command "icache": 0x4000cdb8 => 0x00fecdb8
>Command "dcache": 0x4000ce5c => 0x00fece5c
>Command "reset": 0x40013528 => 0x00ff3528
>Command "version": 0x4000cc34 => 0x00fecc34
>Command "help": 0x4000cc80 => 0x00fecc80
>Command "?": 0x4000cc80 => 0x00fecc80
>   FLASH:  4 MB
>Hit any key to stop autoboot:  0
>## Booting Linux kernel at 40020000 ...
>    Image Name:   2.2.14 for EST192E
>    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>    Data Size:    413162 Bytes = 403 kB = 0 MB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Uncompressing Kernel Image ... OK
>Linux version 2.2.14 (root@pokey.esteem.com) (gcc version 2.95.2
>19991030 (2.9
>5.3 prerelease/franzo)) #14 Thu Oct 5 13:24:22 PDT 2000
>Boot arguments: root=/dev/nfs rw
>nfsaddrs=100.100.100.21:100.100.100.14 nfsroo
>t=100.100.100.14:/targ
>time_init: decrementer frequency = 183750000/60
>Calibrating delay loop... 48.74 BogoMIPS
>Memory: 15120k available (748k kernel code, 476k data, 40k init)
>[c0000000,c10
>00000]
>Dentry hash table entries: 2048 (order 2, 16k)
>Buffer cache hash table entries: 16384 (order 4, 64k)
>Page cache hash table entries: 4096 (order 2, 16k)
>POSIX conformance testing by UNIFIX
>Linux NET4.0 for Linux 2.2
>Based upon Swansea University Computer Society NET3.039
>NET4: Unix domain sockets 1.0 for Linux NET4.0.
>NET4: Linux TCP/IP 1.0 for NET4.0
>IP Protocols: ICMP, UDP, TCP, IGMP
>TCP: Hash tables configured (ehash 16384 bhash 16384)
>Starting kswapd v 1.5
>CPM UART driver version 0.03
>ttyS00 at 0x0280 is a SMC
>ttyS01 at 0x0380 is a SMC
>pty: 256 Unix98 ptys configured
>RAM disk driver initialized:  16 RAM disks of 4096K size
>loop: registered device at major 7
>NET4: Ethernet Bridge 007 for NET4.0
>early initialization of device brg0 is deferred
>eth0: CPM ENET Version 0.2, 00:10:ec:00:1b:ba
>PPP: version 2.3.7 (demand dialling)
>TCP compression code copyright 1989 Regents of the University of
>California
>PPP line discipline registered.
>brg0: network interface for Ethernet Bridge 007/NET4.0
>brg0: generated MAC address FE:FD:00:30:24:76
>brg0: attached to bridge instance 0
>Sending BOOTP and RARP requests............. timed out!
>IP-Config: Auto-configuration of network failed.
>dev_close: bug eth0 still running
>Looking up port of RPC 100003/2 on 100.100.100.14
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>portmap: server 100.100.100.14 not responding, timed out
>Root-NFS: Unable to get nfsd port number from server, using default
>Looking up port of RPC 100005/1 on 100.100.100.14
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>RPC: sendmsg returned error 101
>
>Blah..Blah..Blah..Blah..Blah..Blah..... reboot in 180 seconds
>
>         I know that my BOOTP and NFS server work because I have tested it
>with another machine. I don't know if the BOOTP requests are making it to
>the server okay.
>
>         At least some of the code works because I can see the TENA go
> high
>and bits being sent (may not be the correct bits ;-) on the transmit line
>going to the PHY(I can also see a signal going to the jack from the PHY).
>When a packet (any ethernet activity from the net) comes in through
>the PHY
>I can see the RENA line go high and bits coming in on the receive line.
>
>         I noticed that the rpxlite has a colision test disable line
> in its
>BSCR.  Is this needed to get the transmit to work right?
>
>Note: I have not ruled out the PHY to Jack interface as the problem.
>
>Any help appreciated. Many MAny thanks in advance.
>
>         Conn Clark
>
>


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