NSLU2-Linux
view · edit · print · history

Development.DownloadingTheIntelSourceCode History

Hide minor edits - Show changes to markup

May 10, 2008, at 09:00 PM by Rob Lockhart -- changed NPE to 2.4
Changed lines 16-17 from:

I just tried the "make slugosle" and it apparently is looking for v2.3, so v2.1 won't help you.

to:

I just tried the "make slugosle" and it apparently is looking for v2.4, so v2.1 won't help you.

Changed lines 20-21 from:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader. Current brings you to a page labelled Hardware Access Software & Development Environments. At present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader. Current brings you to a page labelled Hardware Access Software & Development Environments. At present we use version 2.1 2.4 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx. Note that there is a v3.0 but don't use that - use 2.4 for now.

Changed lines 23-24 from:

[SlugOS LE, requires version 2.3 without Crypto : Rob Lockhart]

to:

[SlugOS LE/BE, requires vers 2.4 without Crypto : Rob Lockhart]

Changed lines 47-52 from:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum file as well.

The Makefile now works with version 2.3.2, so it is no longer necessary to rename the zip-file. To generate the MD5sum file, use the follwing command when in the download-directory to where you copied the zip-file:

md5sum -b IPL_ixp400NpeLibrary-2_3_2.zip | awk '{print $1}' > IPL_ixp400NpeLibrary-2_3_2.zip.md5

to:

The Makefile now works with version 2.4, so it is no longer necessary to rename the zip-file. To generate the MD5sum file, use the following command when in the download-directory to where you copied the zip-file:

md5sum -b IPL_ixp400NpeLibrary-2_4.zip | awk '{print $1}' > IPL_ixp400NpeLibrary-2_4.zip.md5

August 16, 2007, at 11:37 PM by fcarolo -- removed false wikilinks
Changed lines 18-19 from:

That page may change as Intel updates its web site. You must register on this site to access the software. You may find that the registration processes do not work with your web browser - they don't work with Konqueror 3.4.x - there is no choice but to use one which is supported. It also doesn't work with Firefox 2.0, so I had to use IE7? (worked). Once you have registered you will be able to access the main software download page.

to:

That page may change as Intel updates its web site. You must register on this site to access the software. You may find that the registration processes do not work with your web browser - they don't work with Konqueror 3.4.x - there is no choice but to use one which is supported. It also doesn't work with Firefox 2.0, so I had to use IE7 (worked). Once you have registered you will be able to access the main software download page.

Changed lines 38-41 from:

Once the files are in the downloads directory openslug and ucslugc builds should work. bitbake will still attempt to download the files from the deliberately incorrect URI in the relevant .bb files, however when it fails it should still find the complete files in the downloads directory. At this point bitbake generates a 32 character MD5? checksum for the file and stores it in file.zip.md5, this prevents bitbake attempting the download again.

If you find the build still errors out at the fetch step (this has been observed though there may have been another error) you can generate the MD5? checksum file yourself with the following command (for a file 'file'):

to:

Once the files are in the downloads directory openslug and ucslugc builds should work. bitbake will still attempt to download the files from the deliberately incorrect URI in the relevant .bb files, however when it fails it should still find the complete files in the downloads directory. At this point bitbake generates a 32 character MD5 checksum for the file and stores it in file.zip.md5, this prevents bitbake attempting the download again.

If you find the build still errors out at the fetch step (this has been observed though there may have been another error) you can generate the MD5 checksum file yourself with the following command (for a file 'file'):

Changed lines 47-50 from:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum? file as well.

The Makefile now works with version 2.3.2, so it is no longer necessary to rename the zip-file. To generate the MD5sum? file, use the follwing command when in the download-directory to where you copied the zip-file:

to:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum file as well.

The Makefile now works with version 2.3.2, so it is no longer necessary to rename the zip-file. To generate the MD5sum file, use the follwing command when in the download-directory to where you copied the zip-file:

Changed line 53 from:

After generating the MD5sum? file, call make again. The build should continue now without further errors.

to:

After generating the MD5sum file, call make again. The build should continue now without further errors.

August 14, 2007, at 07:28 PM by Lars Bager --
Changed lines 47-53 from:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum? file as well.

to:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum? file as well.

The Makefile now works with version 2.3.2, so it is no longer necessary to rename the zip-file. To generate the MD5sum? file, use the follwing command when in the download-directory to where you copied the zip-file:

md5sum -b IPL_ixp400NpeLibrary-2_3_2.zip | awk '{print $1}' > IPL_ixp400NpeLibrary-2_3_2.zip.md5

After generating the MD5sum? file, call make again. The build should continue now without further errors.

April 08, 2007, at 01:50 AM by Rob Lockhart -- added notes about copying 2_3_2.zip to 2_3.zip for makefile
Added lines 46-47:

Note that I had errors whereby the version of the file I downloaded was IPL_ixp400NpeLibrary-2_3_2.zip but the makefile for make slugosle was looking for IPL_ixp400NpeLibrary-2_3.zip , so I copied that file to IPL_ixp400NpeLibrary-2_3.zip and also created an MD5sum? file as well.

April 08, 2007, at 01:25 AM by Rob Lockhart -- added more specific info for URL
Changed lines 20-21 from:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader. Current brings you to a page labelled Hardware Access Software & Development Environments. At present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

April 08, 2007, at 01:23 AM by Rob Lockhart -- removed wrong info from URL referenced
Changed lines 20-21 from:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader NPE Microcode (without crypto), at present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

April 08, 2007, at 01:21 AM by Rob Lockhart -- un-linethrough\'ed the URL
Changed lines 11-13 from:

http://developer.intel.com/design/network/products/npfamily/download_ixp400.htm ( as of 22/12/2006 )

Now v2.1 is located in the Archives:

to:

http://developer.intel.com/design/network/products/npfamily/download_ixp400.htm

Note that v2.1 is located in the Archives:

Changed lines 16-17 from:

I just tried the "make slugosle" and it apparently is looking for version 2.3

to:

I just tried the "make slugosle" and it apparently is looking for v2.3, so v2.1 won't help you.

April 08, 2007, at 01:19 AM by Rob Lockhart -- Updated version to 2.3, as this is what is requierd for slugosle
Added lines 16-17:

I just tried the "make slugosle" and it apparently is looking for version 2.3

Changed lines 20-21 from:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader NPE Microcode (without crypto), at present we use version 2.1 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader NPE Microcode (without crypto), at present we use version 2.1 2.3 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

Changed lines 23-24 from:
to:

[SlugOS LE, requires version 2.3 without Crypto : Rob Lockhart]

April 08, 2007, at 01:00 AM by Rob Lockhart -- minor formatting edits
Added line 12:
Changed line 24 from:

# Intel Hardware Access Software (the driver software). => no longer needed because alternative open-source version is available.

to:
  1. Intel Hardware Access Software (the driver software). => no longer needed because alternative open-source version is available.
April 08, 2007, at 01:00 AM by Rob Lockhart -- Updated with newer locations, new open-source driver, slashed-thru most errored details
Changed lines 11-16 from:

http://developer.intel.com/design/network/products/npfamily/download_ixp400.htm ( as of 22/12/2006 )

That page may change as Intel updates its web site. You must register on this site to access the software. You may find that the registration processes do not work with your web browser - they don't work with Konqueror 3.4.x - there is no choice but to use one which is supported. Once you have registered you will be able to access the main software download page.

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.1 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

http://developer.intel.com/design/network/products/npfamily/download_ixp400.htm ( as of 22/12/2006 ) Now v2.1 is located in the Archives: http://developer.intel.com/design/network/products/npfamily/ixp400_archives.htm

That page may change as Intel updates its web site. You must register on this site to access the software. You may find that the registration processes do not work with your web browser - they don't work with Konqueror 3.4.x - there is no choice but to use one which is supported. It also doesn't work with Firefox 2.0, so I had to use IE7? (worked). Once you have registered you will be able to access the main software download page.

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader NPE Microcode (without crypto), at present we use version 2.1 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

Changed lines 21-23 from:

In current builds you need two pieces of software contained in two separate downloadable .zip files:

  1. Intel Hardware Access Software (the driver software).
to:

In current builds you need two one pieces of software contained in two one separate downloadable .zip files:

# Intel Hardware Access Software (the driver software). => no longer needed because alternative open-source version is available.

Changed lines 26-27 from:

Download both .zip files - you have to accept the respective license agreement for each download.

to:

Download both .zip files - you have to accept the respective license agreement for each download.

December 22, 2006, at 02:38 PM by Peter Taylor -- new intel link
Changed lines 11-12 from:

http://developer.intel.com/design/network/products/npfamily/ixp425swr1.htm

to:

http://developer.intel.com/design/network/products/npfamily/download_ixp400.htm ( as of 22/12/2006 )

January 07, 2006, at 05:09 PM by jbowler -- update Intel version number
Changed lines 15-16 from:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.0 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

to:

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.1 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

January 03, 2006, at 04:07 PM by cwatts -- Added note regards if crypto necessary
Added lines 17-18:

[Unslung 6, requires version 2.1 without Crypto : cwatts ]

October 24, 2005, at 10:16 PM by jbowler -- Download and install instructions
Added lines 24-37:

Storing the downloaded source

It is probably a good idea to keep a copy of the source somewhere outside the master makefile build tree, because it is sometimes convenient and even necessary to delete the whole tree in order to ensure a clean build.

To use the .zip files however they must be copied or linked into the bitbake downloads directory - defined by the variable DL_DIR in the bitbake configuration. This defaults to the directory downloads at the top of the master makefile build tree.

Once the files are in the downloads directory openslug and ucslugc builds should work. bitbake will still attempt to download the files from the deliberately incorrect URI in the relevant .bb files, however when it fails it should still find the complete files in the downloads directory. At this point bitbake generates a 32 character MD5? checksum for the file and stores it in file.zip.md5, this prevents bitbake attempting the download again.

If you find the build still errors out at the fetch step (this has been observed though there may have been another error) you can generate the MD5? checksum file yourself with the following command (for a file 'file'):

md5sum file | while read checksum file
do
echo -n "$checksum" >"$file".md5
done
October 24, 2005, at 10:05 PM by jbowler --
Added lines 1-23:

You must download the source code for the IXP420 Network Processing Engines (NPE) yourself before building either OpenSlug or UcSlugC.

This is because using this source requires that you agree to the corresponding Intel license - this license restricts how you redistribute the resultant binaries. The OpenSlug EULA is an example of how this can be done.

To use the Intel source after downloading it the downloaded .zip files must be placed in the bitbake downloads directory (named ${DL_DIR} within the bitbake .bb files). In a standard build from the master makefile this is just the subdirectory downloads, if you changed DL_DIR or have a different build structure it may be somewhere else.

Downloading the source

Use the web site http://developer.intel.com, the source download page is accessible from the web page for the Intel® IXP420 Network Processor, at present this is:

http://developer.intel.com/design/network/products/npfamily/ixp425swr1.htm

That page may change as Intel updates its web site. You must register on this site to access the software. You may find that the registration processes do not work with your web browser - they don't work with Konqueror 3.4.x - there is no choice but to use one which is supported. Once you have registered you will be able to access the main software download page.

The software you require is the Intel® IXP400 Software and RedBoot* Boot Loader, at present we use version 2.0 and this is the current version, but in the future you may need to access this version off the archived link. The exact names and version specific names can be found in the bitbake .bb files for the ixp4xx package - look at the files in openembedded/packages/ixp4xx.

In current builds you need two pieces of software contained in two separate downloadable .zip files:

  1. Intel Hardware Access Software (the driver software).
  2. NPE Microcode (the binary for the NPE encoded as arrays of C constants).

Download both .zip files - you have to accept the respective license agreement for each download.

view · edit · print · history · Last edited by Rob Lockhart.
Based on work by fcarolo, Lars Bager, Rob Lockhart, Peter Taylor, jbowler, and cwatts.
Originally by jbowler.
Page last modified on May 10, 2008, at 09:00 PM