Thank you all for the help. I didn't understand how all of this fit together
and was taking a completely incorrect approach.
I was able to get the board to boot just fine with your suggestions. The PCI
network drivers seemed to install successfully. I am able to ping from the
target from the host but I can't ping the host from the target. The network
interfaces are set up as follows:
Host:
6 > ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:06:5B:2F:24:44
inet addr:131.179.187.20 Bcast:131.179.187.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5239573 errors:0 dropped:0 overruns:161 frame:0
TX packets:1347440 errors:0 dropped:0 overruns:0 carrier:837
collisions:2858 txqueuelen:100
Interrupt:11 Base address:0xe880
eth1 Link encap:Ethernet HWaddr AA:00:00:00:00:00
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:46895 errors:0 dropped:0 overruns:0 frame:0
TX packets:46895 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
-note: I removed the vmware interfaces-
and for the target:
[root@Linux /]$ifconfig -a
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:01
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Routing is setup as follows:
Host:
7 > route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
131.179.187.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
172.16.230.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
192.168.139.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 131.179.187.1 0.0.0.0 UG 0 0 0 eth0
Target:
[root@Linux /]$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 eth0
Any suggestions what could the be problem?
Also, I wanted to clarify exactly how this system works. The host now has an
ethernet interface called eth1 that is really a link into the pci bus. This
interface talks to the target's interface (eth0) through the pci bus. These
packets never leave the network.
Why did intel and Radisys decide to have this communication occur over ethernet
interfaces? Is this to make communication between the host and target easier?
I assumed that ifconfig on the target would also show interfaces for each of the
four RJ-45 jacks that are on the card . Since they didn't show up I assume that
I access these through the strong arm? Do these ports get interfaces in linux?
Thanks for the help.
GKP
----------------------------------------------------------------------
Greg Prier Previously: A Mudder
3564 Boelter Hall Currently: A Bruin working
UCLA CA 90095 towards a PhD
(310) 825-8899 After that: No idea
"Hell, there are no rules here. We're trying to accomplish something."
Thomas Edison
On Wed, 17 Apr 2002, Brandewie, Dirk J wrote:
> The ENP2505 does not have an on board 82559, the tftp option
> requires an ethernet card to be installed in the PMC site.
>
> The firmware on the board you have is setup to boot the board
> by downloading the kernel and ramdisk over the PCI interface.
> There is a bug in the cygmon on the board that keeps the
> ethernet interface from working. This is my bug :-( but you
> are the first person of all the boards we have donated who
> has wanted to use tftp for download. You should have gotten
> a CD with the linux drivers needed to boot the board in a
> Linux host.
>
> --Dirk
>
> > -----Original Message-----
> > From: Gregory Prier [mailto:greg@lever.cs.ucla.edu]
> > Sent: Tuesday, April 16, 2002 3:06 PM
> > To: ixp1200(a)CS.Princeton.EDU
> > Subject: [ixp1200] Booting Intel ixp boards from tftp
> >
> >
> > Our lab has two intel IXP 1200 evaluation boards. These fit
> > in a standard PC
> > (they have pci slots) and have serial access like an
> > evaluation board. The
> > boards are made by RadiSys and have the part number ENP2505.
> > I have been trying
> > for a few weeks to get them to boot linux via tftp and I
> > haven't had any luck.
> >
> > When the board starts it immediately boots into Cygmon. When
> > HOST mode is
> > enabled Cygmon then counts down and starts automatically
> > booting linux. At this
> > point I get this error message:
> >
> > Failed to initialize TFTP transfer, check network connection
> > and IP addr.
> >
> > When I am in FTP mode I immediately get this message:
> >
> > Press space bar to abort host download mode....
> > Press space bar to abort host download mode....
> >
> > If I don't push space then this will continue forever.
> >
> > The bootoptions are set as follows:
> >
> > cygmon> bo
> > [BootOptions]:
> > 1 BOOTP/Manual (manual)
> > 2 Local IP (131.179.187.21)
> > 3 Remote IP (131.179.187.20)
> > 4 Linux kernel file name (zImage)
> > 5 Linux ramdisk file name (ramdisk_img.gz)
> > 6 Linux kernel load offset (C4008000)
> > 7 Linux boot command line string ()
> > 8 Countdown to auto-boot linux (60)
> > 9 Starting SDRAM offset for host PCI access (0 MB)
> > 10 SDRAM window size for host PCI access (256 MB)
> > 11 Linux download mode [1] 0=FTP 1=HOST
> > Enter option number (1 to 11), "q" to quit, "s" to save:
> >
> > 131.179.187.20 is a machine on the same ethernet segment as
> > the ixp card. It
> > is running a tftp server that has been tested and seems to work fine.
> > Furthermore, I can run tcpdump on 131.179.187.20 and the ixp
> > card never tries
> > to get anything from the tftp server. It doesn't send any
> > traffic onto the
> > network, not even arp.
> >
> > I tried using the System Monitor mode on the board but this
> > just hung when the
> > board tried to boot. I also can't get to the boot manager
> > because Cygmon seems
> > to immediately start up instead. I can't find a way to make
> > sure that the
> > ethernet interfaces are up and that I have configured
> > everything correctly
> > before declaring the ROM bad and reflashing it.
> >
> > Specifically, my questions are:
> >
> > - What exactly is the "on-board 82559 (or 82559ER) Ethernet Interface"
> > mentioned in the manuals? Does this refer to all of the 4
> > RJ-45 jacks on the
> > board or some jack that I don't have or don't see? Since the
> > board supposedly
> > uses this for the tftp transfer I want to make sure that I am
> > plugging the
> > cables into the right jacks on the card. Is there a specific
> > jack that I am
> > supposed to use? I have tried all four and haven't had any luck yet.
> >
> > - Any idea why I can't get to the boot manager or the system
> > monitor when
> > booting the board? Were these removes to make room for Cygmon?
> >
> > - Does any one know of a way to hard reboot the card from
> > inside cygmon? It
> > would be a big help for testing.
> >
> > - Any idea why the board won't boot from the tftp server?
> >
> > - Has anyone seen better documentation on setting up the
> > boards and what to do
> > when they don't work?
> >
> > Any suggestions would be greatly appreciated.
> >
> > Thank you,
> > Greg Prier
> >
> > ----------------------------------------------------------------------
> > Greg Prier Previously: A Mudder
> > 3564 Boelter Hall Currently: A
> > Bruin working
> > UCLA CA 90095 towards a PhD
> > (310) 825-8899 After that: No idea
> >
> > "Hell, there are no rules here. We're trying to accomplish
> > something."
> > Thomas Edison
> >
> >
> >
>
