- ixp1200 - lists.cs.princeton.edu

Tornado Prototyper
by Brandewie, Dirk J 16 Nov '00

16 Nov '00

Thought some on the list would be interested in this. WindRiver Has tornado for download for non-commercial use. Enjoy --Dirk http://www.wrs.com/prototyper/index.html

1 0

IXP1200 Measurement Results
by Scott C. Karlin 15 Nov '00

15 Nov '00

For those interested in what we have been up to with regard to the IXP1200 processor, you might want to check out the following paper, available at http://www.cs.princeton.edu/nsg/papers/ixp.ps The abstract is given below. Scott ----------------------- Evaluating Network Processors in IP Forwarding Tammo Spalink, Scott Karlin, Larry Peterson This paper evaluates the performance of emerging network processors---in particular, designs that employ multiple hardware contexts to hide memory latency---in constructing IP routers. Such processors are designed to forward minimum-sized IP packets at line speeds, with the advantage (over ASIC-based solutions) of being programmable. However, programming such network processors involves two challenges. The first is how to effectively employ the multiple contexts in a way that fully utilizes the memory bandwidth. The second is how to allow the network processor to be programmed dynamically (so it can support new functionality) without violating the processor's tight timing constraints. This paper addresses both of these challenges on a prototype board that uses the IXP1200 network processor. We demonstrate that it is possible to support 8 x 100Mbps ports with enough headroom to access up to 224 bytes of state information for each minimum-sized IP packet.

1 0

RE: VxWorks on IXP
by Heaton, Eric D 14 Nov '00

14 Nov '00

Just for some basic setup info: There are two documents (which should be found on the Developer's Workbench CD) which are invaluable in setting up the Eval System and running the reference designs, the Evaluation System User's Guide and the Example Software User's Guide. There is information sepcific to loading VxWorks without using Tornado in Section 2.5.6 in the Evaluation System User's Guide, but please read through the rest of the document for general setup information. -----Original Message----- From: Varnell, Frank [mailto:frank.varnell@intel.com] Sent: Monday, November 13, 2000 12:06 PM To: 'Alok Kumar'; Kelley Jr, Patrick T Cc: 'Taroon Mandhana'; ixp1200(a)CS.Princeton.EDU Subject: RE: VxWorks on IXP The vxworks_gig image includes the RTM netapp application. The only thing you would then use Tornado for is to have a shell. The developers didn't use a serial port shell, so you have to buy or obtain an eval Tornado for ARM (version 2.0 NOT 2.0.1) to connect to the target if you need a shell. To be more specific, set up your eval card to boot vxworks via the instructions provided with your boad. Then set the vxworks parameters to load vxworks_gig. Thats all you have to do. Packets will be routed according to the compiled in tables. These comments apply to the 1.0 release of the ixp eval. > -----Original Message----- > From: Alok Kumar [mailto:alok@cs.utexas.edu] > Sent: Sunday, November 12, 2000 7:46 AM > To: Kelley Jr, Patrick T > Cc: 'Taroon Mandhana'; ixp1200(a)CS.Princeton.EDU > Subject: RE: VxWorks on IXP > > > How can we run netapp application without tornado? What does netapp > application do and how will it affect if we dont run it? > > Thanks > Alok > > On Fri, 10 Nov 2000, Kelley Jr, Patrick T wrote: > > > 1. No. > > 2. This is fine! The "WDB: Ready." is the key that the > image is loaded and > > you are ready to run. > > > > You should be able to connect with the Workbench no problem now. > > > > (Just make sure you have the NetApp application running on > the core.) > > > > Best Regards, > > Pat > > ___________________________________ > > Patrick T. Kelley > > Technical Marketing Engineer > > Network Processor Operation - Network Communications Group > > > > Intel Corporation > > 77 Reed Road HD2-141 > > Hudson, Massachusetts 01749-2895 > > patrick.t.kelley.jr(a)intel.com > > http://www.intel.com > > > > > > -----Original Message----- > > From: Taroon Mandhana [mailto:mandhana@cs.utexas.edu] > > Sent: Friday, November 10, 2000 3:34 PM > > To: ixp1200(a)CS.Princeton.EDU > > Subject: VxWorks on IXP > > > > Hi, > > > > 1. Is tornado a MUST to download the reference designs on > the board ? > > > > 2. Without Tornado, I tried downloading the default VxWorks image > > ixp1200/boardsupport/bin/vp/vxworks_gig on the board > and landed into > > the errors. Here is how the output looks like > > > > Attached TCP/IP interface to eeE0. > > Attaching network interface lo0... done. > o > > > > Loading... 8488 + 14136 + 228816 > > Starting at 0x1000... > > > > BSP IXP Version: 1.0.1129, built on May 31 2000, 10:28:04 > > > > Early serial debug initialized > > muxDevLoad failed for device entry 0! > > Attached TCP/IP interface to eeE unit 0 > > Attaching network interface lo0... done. > > 0x7ffe64 (tRootTask): dc0 - Failed to read ethernet address > > NFS client support not included. > > > > > > VxWorks > > > > Copyright 1984-1998 Wind River Systems, Inc. > > > > CPU: Intel ixp1200eb - ARM IXP1200 > > VxWorks: 5.4 > > BSP version1.2/1 > > Creation date: May 31 2000 > > WDB: Ready. > > > > STATUS OF intConnect = 0 > > BigMacDriver CTOR OctalMacNumber = 0 > > status = 0 > > status = ffffffff > > > > ----- > > > > Is is erroneous? Is there some troubleshooting guide in the > > documentation ? > > > > Any help is greatly appreciated. > > > > > > Thanks, > > Taroon Mandhana > > > > > > > > > > ______________________________________________________________ > _________________ > > Alok Kumar > > Residence: > 3401 Red River St #201 > Austin, TX 78705 > > Office: > Dept of Computer Science > ACES Building > University of Texas > Austin, TX 78712 > > Ph: Home - (512) 472-6443 > Office - (512) 232-7883 > Fax: (401) 679 8171 > > Homepage: http://www.cs.utexas.edu/~alok > ______________________________________________________________ > _________________ > >

2 1

RE: Schematics for Eval Boards
by Kelley Jr, Patrick T 14 Nov '00

14 Nov '00

The 002 sticker reflects the revision update for B0 200MHz. The schematics number matches the PCB (look under the sticker!) Best Regards, Pat ___________________________________ Patrick T. Kelley Technical Marketing Engineer Network Processor Operation - Network Communications Group Intel Corporation 77 Reed Road HD2-141 Hudson, Massachusetts 01749-2895 patrick.t.kelley.jr(a)intel.com http://www.intel.com -----Original Message----- From: Scott C. Karlin [mailto:scott@CS.Princeton.EDU] Sent: Thursday, November 09, 2000 3:09 PM To: ixp1200(a)CS.Princeton.EDU Subject: Schematics for Eval Boards We just received a new version of the IXP1200 development board with the B0 stepping of the IXP1200 chip. Included in the shipment is the version 1.1.109 of the development environment CD-ROM. I would like to verify that the schematics on this CD-ROM match the board we just received. The evb_p1.pdf page title block states "TOP DOCUMENT NUMBER K-DD-54-30296-0-1" dated 13-AUG-99. Our older board was marked in the copper layer "A13033-001 A01 L1". Our new boards have a sticker in the same place marked "A13033-002". Can anyone confirm that the 13-AUG-99 schematics match the board we just received? Thanks, Scott PS: Early versions of the CD-ROM have the schematics in both pdf and PostScript format. Any chance we can see the PostScript versions again? -------------------------------------------------------------------------- Scott C. Karlin Princeton University PhD Candidate Department of Computer Science Voice: (609) 258-5386 35 Olden Street Email: scott(a)cs.princeton.edu Princeton, NJ 08544-2087 WWW: http://www.cs.princeton.edu/~scott --------------------------------------------------------------------------

2 1

RE: VxWorks on IXP
by Varnell, Frank 13 Nov '00

13 Nov '00

The vxworks_gig image includes the RTM netapp application. The only thing you would then use Tornado for is to have a shell. The developers didn't use a serial port shell, so you have to buy or obtain an eval Tornado for ARM (version 2.0 NOT 2.0.1) to connect to the target if you need a shell. To be more specific, set up your eval card to boot vxworks via the instructions provided with your boad. Then set the vxworks parameters to load vxworks_gig. Thats all you have to do. Packets will be routed according to the compiled in tables. These comments apply to the 1.0 release of the ixp eval. > -----Original Message----- > From: Alok Kumar [mailto:alok@cs.utexas.edu] > Sent: Sunday, November 12, 2000 7:46 AM > To: Kelley Jr, Patrick T > Cc: 'Taroon Mandhana'; ixp1200(a)CS.Princeton.EDU > Subject: RE: VxWorks on IXP > > > How can we run netapp application without tornado? What does netapp > application do and how will it affect if we dont run it? > > Thanks > Alok > > On Fri, 10 Nov 2000, Kelley Jr, Patrick T wrote: > > > 1. No. > > 2. This is fine! The "WDB: Ready." is the key that the > image is loaded and > > you are ready to run. > > > > You should be able to connect with the Workbench no problem now. > > > > (Just make sure you have the NetApp application running on > the core.) > > > > Best Regards, > > Pat > > ___________________________________ > > Patrick T. Kelley > > Technical Marketing Engineer > > Network Processor Operation - Network Communications Group > > > > Intel Corporation > > 77 Reed Road HD2-141 > > Hudson, Massachusetts 01749-2895 > > patrick.t.kelley.jr(a)intel.com > > http://www.intel.com > > > > > > -----Original Message----- > > From: Taroon Mandhana [mailto:mandhana@cs.utexas.edu] > > Sent: Friday, November 10, 2000 3:34 PM > > To: ixp1200(a)CS.Princeton.EDU > > Subject: VxWorks on IXP > > > > Hi, > > > > 1. Is tornado a MUST to download the reference designs on > the board ? > > > > 2. Without Tornado, I tried downloading the default VxWorks image > > ixp1200/boardsupport/bin/vp/vxworks_gig on the board > and landed into > > the errors. Here is how the output looks like > > > > Attached TCP/IP interface to eeE0. > > Attaching network interface lo0... done. > o > > > > Loading... 8488 + 14136 + 228816 > > Starting at 0x1000... > > > > BSP IXP Version: 1.0.1129, built on May 31 2000, 10:28:04 > > > > Early serial debug initialized > > muxDevLoad failed for device entry 0! > > Attached TCP/IP interface to eeE unit 0 > > Attaching network interface lo0... done. > > 0x7ffe64 (tRootTask): dc0 - Failed to read ethernet address > > NFS client support not included. > > > > > > VxWorks > > > > Copyright 1984-1998 Wind River Systems, Inc. > > > > CPU: Intel ixp1200eb - ARM IXP1200 > > VxWorks: 5.4 > > BSP version1.2/1 > > Creation date: May 31 2000 > > WDB: Ready. > > > > STATUS OF intConnect = 0 > > BigMacDriver CTOR OctalMacNumber = 0 > > status = 0 > > status = ffffffff > > > > ----- > > > > Is is erroneous? Is there some troubleshooting guide in the > > documentation ? > > > > Any help is greatly appreciated. > > > > > > Thanks, > > Taroon Mandhana > > > > > > > > > > ______________________________________________________________ > _________________ > > Alok Kumar > > Residence: > 3401 Red River St #201 > Austin, TX 78705 > > Office: > Dept of Computer Science > ACES Building > University of Texas > Austin, TX 78712 > > Ph: Home - (512) 472-6443 > Office - (512) 232-7883 > Fax: (401) 679 8171 > > Homepage: http://www.cs.utexas.edu/~alok > ______________________________________________________________ > _________________ > >

1 0

RE: VxWorks on IXP
by Kelley Jr, Patrick T 12 Nov '00

12 Nov '00

1. No. 2. This is fine! The "WDB: Ready." is the key that the image is loaded and you are ready to run. You should be able to connect with the Workbench no problem now. (Just make sure you have the NetApp application running on the core.) Best Regards, Pat ___________________________________ Patrick T. Kelley Technical Marketing Engineer Network Processor Operation - Network Communications Group Intel Corporation 77 Reed Road HD2-141 Hudson, Massachusetts 01749-2895 patrick.t.kelley.jr(a)intel.com http://www.intel.com -----Original Message----- From: Taroon Mandhana [mailto:mandhana@cs.utexas.edu] Sent: Friday, November 10, 2000 3:34 PM To: ixp1200(a)CS.Princeton.EDU Subject: VxWorks on IXP Hi, 1. Is tornado a MUST to download the reference designs on the board ? 2. Without Tornado, I tried downloading the default VxWorks image ixp1200/boardsupport/bin/vp/vxworks_gig on the board and landed into the errors. Here is how the output looks like Attached TCP/IP interface to eeE0. Attaching network interface lo0... done. o Loading... 8488 + 14136 + 228816 Starting at 0x1000... BSP IXP Version: 1.0.1129, built on May 31 2000, 10:28:04 Early serial debug initialized muxDevLoad failed for device entry 0! Attached TCP/IP interface to eeE unit 0 Attaching network interface lo0... done. 0x7ffe64 (tRootTask): dc0 - Failed to read ethernet address NFS client support not included. VxWorks Copyright 1984-1998 Wind River Systems, Inc. CPU: Intel ixp1200eb - ARM IXP1200 VxWorks: 5.4 BSP version1.2/1 Creation date: May 31 2000 WDB: Ready. STATUS OF intConnect = 0 BigMacDriver CTOR OctalMacNumber = 0 status = 0 status = ffffffff ----- Is is erroneous? Is there some troubleshooting guide in the documentation ? Any help is greatly appreciated. Thanks, Taroon Mandhana

2 1

VxWorks on IXP
by Taroon Mandhana 10 Nov '00

10 Nov '00

Hi, 1. Is tornado a MUST to download the reference designs on the board ? 2. Without Tornado, I tried downloading the default VxWorks image ixp1200/boardsupport/bin/vp/vxworks_gig on the board and landed into the errors. Here is how the output looks like Attached TCP/IP interface to eeE0. Attaching network interface lo0... done. o Loading... 8488 + 14136 + 228816 Starting at 0x1000... BSP IXP Version: 1.0.1129, built on May 31 2000, 10:28:04 Early serial debug initialized muxDevLoad failed for device entry 0! Attached TCP/IP interface to eeE unit 0 Attaching network interface lo0... done. 0x7ffe64 (tRootTask): dc0 - Failed to read ethernet address NFS client support not included. VxWorks Copyright 1984-1998 Wind River Systems, Inc. CPU: Intel ixp1200eb - ARM IXP1200 VxWorks: 5.4 BSP version1.2/1 Creation date: May 31 2000 WDB: Ready. STATUS OF intConnect = 0 BigMacDriver CTOR OctalMacNumber = 0 status = 0 status = ffffffff ----- Is is erroneous? Is there some troubleshooting guide in the documentation ? Any help is greatly appreciated. Thanks, Taroon Mandhana

1 0

Schematics for Eval Boards
by Scott C. Karlin 09 Nov '00

09 Nov '00

We just received a new version of the IXP1200 development board with the B0 stepping of the IXP1200 chip. Included in the shipment is the version 1.1.109 of the development environment CD-ROM. I would like to verify that the schematics on this CD-ROM match the board we just received. The evb_p1.pdf page title block states "TOP DOCUMENT NUMBER K-DD-54-30296-0-1" dated 13-AUG-99. Our older board was marked in the copper layer "A13033-001 A01 L1". Our new boards have a sticker in the same place marked "A13033-002". Can anyone confirm that the 13-AUG-99 schematics match the board we just received? Thanks, Scott PS: Early versions of the CD-ROM have the schematics in both pdf and PostScript format. Any chance we can see the PostScript versions again? -------------------------------------------------------------------------- Scott C. Karlin Princeton University PhD Candidate Department of Computer Science Voice: (609) 258-5386 35 Olden Street Email: scott(a)cs.princeton.edu Princeton, NJ 08544-2087 WWW: http://www.cs.princeton.edu/~scott --------------------------------------------------------------------------

1 0

RE: PCI Configuration Space
by Krueger, Jon 20 Oct '00

20 Oct '00

Solution. The exception was not due to a bug in the IXP hardware. The exception was a result of incomplete/incorrect information given in the IXP1200 Hardware Reference Manual, Section 5.3.1.3. The Type 0 data in Table 5-4 states that StrongARM core address bits 23:22 are NOT equal to 11. This should read: If bits 23:22 are NOT equal to 11, then AD25:AD11 will be a copy of the StrongARM core address -- note that AD31:AD26 are not usable in this mode. If bit 23:22 are EQUAL to 11, the StrongARM core address AD15:AD11 will be decoded, and the appropriate bit in AD31:AD11 will be set. When bits 23:22 are set to 11 (0x3) the proper configuration address is decoded, and the entire configuration space (AD31:AD11) is available. jk > -----Original Message----- > From: Krueger, Jon > Sent: Friday, October 13, 2000 3:50 PM > To: ixp1200(a)CS.Princeton.EDU > Cc: Varsanyi, Eric > Subject: PCI Configuration Space > > I found an interesting "problem" with the IXP1200. > > When doing Type 0/1 configuration reads with the IXP, > any attempt to access devices using AD26-AD31 for their > IDSEL decoding will produce nasty results. > > With VxWorks, you'll get an exception, killing process execution. > With the custom OS I'm running now, I drop into the debugger and the > ARM PC is off in deep space... :-( > > This may be a design decision by the IXP engineers. They do support > a full 10 devices, but they assume that the devices will be decoded > within the config space of AD11-AD25. I'm guessing a bit here, but > it seems that this is the case. > > There are SBCs and "passive" backplanes which hardwire device IDSELs to > the > higher areas of config space AD26-AD31. > > Something to watch out for... > > > jk > > > > Jon Krueger > Senior Engineer > Intel Corporation > Network Equipment Division > > 13280 Evening Creek Drive > San Diego, CA 92128 > (858) 391-1710 > jon.krueger(a)intel.com > >

1 0

PCI Configuration Space
by Krueger, Jon 13 Oct '00

13 Oct '00

I found an interesting "problem" with the IXP1200. When doing Type 0/1 configuration reads with the IXP, any attempt to access devices using AD26-AD31 for their IDSEL decoding will produce nasty results. With VxWorks, you'll get an exception, killing process execution. With the custom OS I'm running now, I drop into the debugger and the ARM PC is off in deep space... :-( This may be a design decision by the IXP engineers. They do support a full 10 devices, but they assume that the devices will be decoded within the config space of AD11-AD25. I'm guessing a bit here, but it seems that this is the case. There are SBCs and "passive" backplanes which hardwire device IDSELs to the higher areas of config space AD26-AD31. Something to watch out for... jk > Jon Krueger > Senior Engineer > Intel Corporation > Network Equipment Division > > 13280 Evening Creek Drive > San Diego, CA 92128 > (858) 391-1710 > jon.krueger(a)intel.com > >

1 0