March 2000 - ixp1200 - lists.cs.princeton.edu

Re: How to Boot the Ethernet Evaluation System?
by Scott C. Karlin 31 Mar '00

31 Mar '00

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(a)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@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@CS.Princeton.EDU] > > > Sent: Monday, March 27, 2000 11:43 AM > > > To: ixp1200(a)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 >

1 0

RE: How to Boot the Ethernet Evaluation System?
by Johnson, Erik J 27 Mar '00

27 Mar '00

> 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. Ahh, looking at the Beta4 version of the BSP, I see that they are now shipping two drivers with the OS (and presumably with the boot rom). (Check BoardSupport/VxWorks/IXP1200EB/configNet.h). So if your NIC has digital parts on it, go with dc, if it has intel parts, go with eeV (did you try eeV or eeE? Make sure you try eeV0 and eeE0. eeVconfig.h would seem to indicate that it uses eeE0, but I can't be sure).. I am still in the past with the dc NIC so I cannot attest to how things work with the intel part. hopefully the driver for the intel nic has been compiled into the bootrom. I wonder if anyone else out there can verify this(?) I don't know of a symbol table lookup command from the boot loader (i.e., like lkup() does once you get the full version of vxworks loaded). I tried to do an nm on the vxWorks_rom and vxWorks image in the bin/vb directory and vxWorks turns up hits for both eeVEndLoad and dec21x4xEndLoad (the dc driver). The vxWorks_rom image must be partly stripped because it does not turn up hits for 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. Ahhh, perhaps that explains your flags being set to 0x80. I just checked our settings and our flags are 0, which may explain why we are using ftp rather than tftp (if I read sysLib.h correctly, 0x80 is for tftp). One simple test would be to change the flags to 0, but I doub't this will help. > Is the boot prompt "n" command really supposed to fail? I would assume that it fails because both the dc and eeV are END drivers and the n command (if I read code correctly) is dealing with BSD-style drivers. (I am looking at configNet.h and bootConfig.c. In bootConfig.c I assume bootCmdLoop is producing the prompt you are getting. This calls netifAdrsPrint in response to the 'n' command). Following these calls through, I don't see the code calling muxDevLoad, rather it calls the attach routine in the device structure, which, correct me if I am wrong, is the older BSD-style interface. Anyway, it would not surprise me if it fails because of this (BTW, it fails on our "working" system). You could fix the n command to do the right thing (say call muxShow() instead of netifAdrsPrint), but of course since you can't boot vxworks you can't overwrite the boot rom and you are stuck. sorry for not being any help, I guess the best I can do is point you back to the person who shipped you the system and have them verify the version of your bootrom, and then, maybe replace your NIC. erk

1 0

Re: How to Boot the Ethernet Evaluation System?
by Tammo Spalink 27 Mar '00

27 Mar '00

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(a)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@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@CS.Princeton.EDU] > > Sent: Monday, March 27, 2000 11:43 AM > > To: ixp1200(a)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

1 0

None
by owner-ixp1200＠CS.Princeton.EDU 27 Mar '00

27 Mar '00

>From scott(a)CS.Princeton.EDU Mon Mar 27 14:59:06 2000 Message-ID: <86FFC5B42CDCD211AC4900A0C95D19E3D6160D(a)orsmsx52.jf.intel.com> From: "Johnson, Erik J" <erik.j.johnson(a)intel.com> To: ixp1200(a)CS.Princeton.EDU Subject: RE: How to Boot the Ethernet Evaluation System? Date: Mon, 27 Mar 2000 11:57:10 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-ixp1200 Reply-To: "Johnson, Erik J" <erik.j.johnson(a)intel.com> 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@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@CS.Princeton.EDU] > Sent: Monday, March 27, 2000 11:43 AM > To: ixp1200(a)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 >

1 0

How to Boot the Ethernet Evaluation System?
by Tammo Spalink 27 Mar '00

27 Mar '00

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

1 0

Another Test -- Please Ignore
by Scott C. Karlin 24 Mar '00

24 Mar '00

This is another test message for the ixp1200 list. I am in the process of making sure that the list is properly archiving messages before someone posts a "real" message. -Scott

1 0