How to Reflash using Redboot and TFTP
You probably don't want to do this: there are better ways to reflash your Slug. In particular, see UpSlug2 and SercommFirmwareUpgrade. If you have read those pages and still think that you want to use the method described here, I encourage you to ask for advice on the mailing lists before continuing.
The method described here involves accessing the Redboot bootloader's command prompt and then transferring the new flash data from a TFTP or HTTP server on your PC. You first transfer the data into the Slug's RAM and then program it into the flash. The danger with this method is that you need to enter various memory addresses at the Redboot command prompt, and if you get them wrong you will write to the wrong areas of the flash. If you accidentally write over Redboot itself, your Slug will require special JTAG hardware to repair. The authors of this page do not guarantee that the commands listed here are correct, so you should be sure that you personally understand the memory map and believe them to be right before continuing.
Installing a TFTP or HTTP server
The first thing you will need to do is set up a TFTP or HTTP server on your PC, if you do not already have one installed. Linux users have a variety of TFTP servers available. Apparently one is available on MacOS X (someone wrote "If you're using OS X, feel free to contact me for details", but exactly who wrote that is now lost). On MS-Windows, see SetupTFTPServer. For Linux, there's a plethora of instructions available, with some distributions having a TFTP server installed by default, and files being served from its /tftpboot directory (but read-only access). The best advise would be to seek the wikis and manuals for your distribution as such things as inetd may need to be modified and/or created.
Although TFTP is the "traditional" choice, apparently HTTP can also be used. Mac users could use something called "personal web services".
Obtain the firmware and place it in the TFTP or HTTP serving directory
One option is to re-flash with the Linksys firmware: NSLU2 Firmware 2.3R63 - unzip this file and put the 8 MiB? firmware file in the TFTP directory. Alternatively you can use a firmware file distributed by this project, or one you have saved yourself using "cat /dev/mtdblock* > firmware". In any case you should have an 8 MiB? file.
MacOS "personal web services" users should place the file in
Connect to Redboot
You have two choices for accessing the Redboot command prompt: you can either connect over the network (see HowTo.TelnetIntoRedBoot) or you can use the serial port, if you have the necessary hardware (see HowTo.AddASerialPort).
Tell the NSLU2 where the TFTP server is
At the RedBoot prompt, type the following command:
ip_address -h 192.168.0.99
where 192.168.0.99 is the IP of the TFTP server. This tells RedBoot where to download the data from. You should get your prompt back after each command; I've occasionally had it hang, in which case restart and do the Ctrl-C dance again.
Load the firmware
To get the firmware from a TFTP server, type:
load -r -v -b 0x01000000 -h 192.168.0.99 NSLU2_V23R25.bin
again, in this article 192.168.0.99 is the assumed IP of the TFTP server. (assuming, of course, that you're using the R25 firmware). This will load the firmware into the slug's RAM over the network.
RedBoot also supports HTTP. Here's an example of using that:
Don't use the -v flag in HTTP mode, it will cause the transfer to fail.
Verify the firmware
For safety's sake, you can now do a checksum on the file to ensure it didn't get corrupted in transit. Simply type:
and you should get a set of numbers calculated from the file. Run the "cksum" program on your TFTP server for comparison (cksum should be available on all Linux systems; not sure about Windows and Macs). Apparently the checksums for the Linksys firmware are:
R25: 3007264634 8388608 NSLU2_V23R63.bin: 4056400472 8388608
If this doesn't match, try again. DO NOT CONTINUE with a wrong checksum.
Write the firmware to the flash.
This is your last chance to change your mind and use Upslug2 instead. If you're sure you want to continue, cross your fingers and type:
fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
This will write the kernel, ramdisk and trailer portions of the firmware to the right position in the flash. This may take up to 5 minutes. When it's finished and you get your Redboot prompt back, your slug should be fixed.
Because you didn't overwrite the SysConf part of the flash, your slug will still be using the same IP address as before. Remember to set your subnets appropriately, and ensure you're looking for it in the right place. If you wish to erase the SysConf as well then follow the instructions to reset the SysConf
Restart the slug
With fingers still crossed, type:
Be ready to celebrate when you hear that strangled little beep it makes as it finishes booting and is ready to be used.