How to Boot the Ethernet Evaluation System?

[Scott C. Karlin]

In case anyone is interested, Tammo and I solved the problem by
setting jumpers J28 (GP3) and J27 (GP2) to the "factory settings"
as described in the documentation (rather than the settings they
were in when they arrived from the factory).

-Scott


Tammo Spalink writes:
> 
> IXP1200 board and ethernet card are both in the correct PCI slots.
> 
> Using the dc0 device doesn't seem to make any difference at all.
> Using the "@" command instead of the "l" command makes no difference
> at all either.
> 
> Regarding FTP: I set the boot flags for TFTP, so I believe no
> username/password should be needed.  Also, we never saw the box
> generate a single packet, so I doubt this is it.  To be sure, we tried
> with real FTP and no luck there either (with a username & passwd).
> Yes scout-7 is running a TFTP server.
> 
> Is the boot prompt "n" command really supposed to fail?
> 
> Tammo
> 
> On Mon, 27 Mar 2000, "Johnson, Erik J" <erik.j.johnson at intel.com> wrote:
> > 
> > Here is what I know, maybe this will help (some of it just
> > repeats what you already know)
> > 
> > dc0 is the correct boot device (at least for the A-steppings of
> > the board, which is what I assume you have).  Make sure you have
> > the given NIC on the correct slot on the backplane provided
> > (it should be the farthest from the system slot where the
> > IXP1200 is).
> > 
> > just a sanity check: you are running a
> > ftp server on scout-7.  Also 128.xx.yy are all in the same subnet (or
> > else you need to set the gateway value).  There should be two other options
> > in
> > the vxworks boot loader one for username and password (these
> > should be for the ftp server and the home directory of this
> > user should be where the vxWorks binary is located).  I don't
> > see those in your print of the boot options, were they perhaps left
> > blank?  you can use anonymous, just fill that in as the username and
> > put the standard x at y password
> > 
> > I assume that if all of the above is okay, then the only other difference is
> > that I have never tried to load the image (then jump to the entry
> > point) on this board, I simply do it all with the @ command.
> > 
> > I can go and dump out our boot loader settings if needed.  Let me
> > know
> > 
> > erik
> > 
> > > -----Original Message-----
> > > From: Tammo Spalink [mailto:tspalink at CS.Princeton.EDU]
> > > Sent: Monday, March 27, 2000 11:43 AM
> > > To: ixp1200 at CS.Princeton.EDU
> > > Subject: How to Boot the Ethernet Evaluation System?
> > > 
> > > 
> > > 
> > > Following the "Ethernet Evaluation System User's Guide":
> > > 
> > > I am trying to get a VxWorks image to load on the chip, but am having
> > > no success.  Maybe someone has a suggestion as to what I should expect
> > > or am not doing.
> > > 
> > > I have configured the system as follows:
> > > 
> > > > [VxWorks Boot]: p
> > > > 
> > > > boot device          : eeE
> > > > unit number          : 0
> > > > processor number     : 0
> > > > host name            : scout-7
> > > > file name            : vxWorks
> > > > inet on ethernet (e) : 128.xx.yy.100
> > > > host inet (h)        : 128.xx.yy.27
> > > > flags (f)            : 0x80
> > > > target name (tn)     : ixp1200
> > > > 
> > > 
> > > By which I am intending that it should fetch the "vxWorks" file (the
> > > one provided in /boardsuppoort/bin/vb on the CD) from the machine
> > > scout-7(128.xx.yy.27) via TFTP.  It may use the IP address
> > > 128.xx.yy.100.
> > > 
> > > However, trying a load command results in:
> > > 
> > > > [VxWorks Boot]: l
> > > > 
> > > > boot device          : eeE
> > > > unit number          : 0
> > > > processor number     : 0
> > > > host name            : scout-7
> > > > file name            : vxWorks
> > > > inet on ethernet (e) : 128.xx.yy.100
> > > > host inet (h)        : 128.xx.yy.27
> > > > flags (f)            : 0x80
> > > > target name (tn)     : ixp1200
> > > > 
> > > > Early serial debug initialized
> > > > muxLoad failed!
> > > > muxLoad
> > > >
> > > > [VxWorks Boot]:
> > > 
> > > Thinking this might be the wrong boot device since the boot help says:
> > > 
> > > > [VxWorks Boot]: ?
> > > > 
> > > 
> > > ... help stuff omitted ...
> > > 
> > > >  n netif               - print network interface device address
> > > 
> > > ... help stuff omitted ...
> > > 
> > > > 
> > > > available boot devices:Enhanced Network Devices
> > > >  dc0 eeE0
> > > > [VxWorks Boot]:
> > > 
> > > I tried dc0 as well, with the same results.  Then I tried the 
> > > following:
> > > 
> > > > [VxWorks Boot]: n dc0
> > > > Network interface dc unknown.
> > > > Cannot initialize interface named "dc0"
> > > > [VxWorks Boot]: n eeE0
> > > > Network interface eeE unknown.
> > > > Cannot initialize interface named "eeE0"
> > > > [VxWorks Boot]:
> > > 
> > > Repeating this process with a packet sniffer on, we did not see
> > > anything that looked like it came from the system.  I think I am
> > > stuck.  Any suggestions?
> > > 
> > > Thanks,
> > > 
> > > Tammo
> > > 
> > 
> 
> ------- End of Forwarded Message
>