NSLU2-Linux
view · edit · print · history

HowTo.RecoverFromABadFlashUsingOnlyTheSerialPort History

Hide minor edits - Show changes to markup

November 17, 2008, at 05:23 AM by Rob Lockhart -- Cosmetic fixes for bad spelling/grammar
Changed lines 8-9 from:

This procedure can be used to recover a dead slug using the inbuilt serial port, only no ethernet connection is required.

to:

This procedure can be used to recover a dead slug using the internal serial port, only no ethernet connection is required.

Changed lines 17-18 from:

Not sure which legal values are available for baudrate, admittedly your not likely to want to go at a slower speed

to:

Not sure which legal values are available for baudrate, admittedly you're not likely to want to go at a slower speed

Changed line 28 from:

When the download is completed, statistics are outputted like:

to:

When the download is completed, statistics are output like:

January 12, 2008, at 12:03 PM by Bullfrog -- zmodem not supported - ymodem is and it\'s quicker.
Changed lines 33-36 from:

You can use zmodem if required command is

load -r -v -b 0x01000000 -m zmodem

to:

You can use ymodem if required command is

load -r -v -b 0x01000000 -m ymodem

(use ymodem-g within hyperterminal - at 115200 upload takes 20mins)

March 01, 2007, at 04:27 AM by mrkzander --
Changed lines 1-2 from:

Warning!! This document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please try the http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash procedures first.

to:

Warning!! This document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please try the RecoverFromABadFlash procedures first.

March 01, 2007, at 04:26 AM by mrkzander --
Changed lines 1-2 from:

Warning!! This document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List.

<< http://tech.groups.yahoo.com/group/nslu2-general/ >>

to:

Warning!! This document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please try the http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlash procedures first.

March 01, 2007, at 03:27 AM by mrkzander --
Changed line 1 from:

Warning!! The document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List.

to:

Warning!! This document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List.

Changed lines 5-6 from:
to:



March 01, 2007, at 03:26 AM by mrkzander --
Changed lines 1-2 from:

Warning!! The document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List. <<http://tech.groups.yahoo.com/group/nslu2-general/>>

to:

Warning!! The document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List.

<< http://tech.groups.yahoo.com/group/nslu2-general/ >>

March 01, 2007, at 03:26 AM by mrkzander --
Changed lines 2-5 from:
  The procedure below carries a strong risk of damaging your NSLU2!!
to:

The procedure below carries a strong risk of damaging your NSLU2!!

March 01, 2007, at 03:25 AM by mrkzander --
Added lines 1-5:

Warning!! The document describes an advanced procedure! If you are trying to recover from a bad upgrade and are new to the NSLU2, please ask for assistance on the NSLU2-General Mailing List. <<http://tech.groups.yahoo.com/group/nslu2-general/>>

  The procedure below carries a strong risk of damaging your NSLU2!!
October 14, 2006, at 01:38 PM by Reedy Boy --
Changed lines 21-22 from:

When the download is completed, statistics are outputted like:\\

to:

When the download is completed, statistics are outputted like:

October 14, 2006, at 01:38 PM by Reedy Boy --
Changed line 12 from:

Enter the command:

to:

Enter the command:\\

Changed line 21 from:

When the download is completed, statistics are outputted like:

to:

When the download is completed, statistics are outputted like:\\

Changed lines 31-32 from:

For safety's sake, you can now do a checksum on the file to ensure it didn't get corrupted in transit. Simply type: \\

to:

For safety's sake, you can now do a checksum on the file to ensure it didn't get corrupted in transit. Simply type: \\

October 14, 2006, at 01:37 PM by Reedy Boy --
Deleted line 12:
Changed lines 21-22 from:

It outputs some statistics like this when it completes the download

to:

When the download is completed, statistics are outputted like:

October 14, 2006, at 01:37 PM by Reedy Boy --
Changed line 24 from:

Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000

to:

Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000\\

October 14, 2006, at 01:36 PM by Reedy Boy --
Changed lines 5-6 from:

connect the serial cable as indicated here at the redboot> prompt it is possible to enter various commands.

to:

Connect the serial cable as indicated here at the redboot> prompt it is possible to enter various commands.

Changed lines 22-23 from:

It outputs some statistics like so, Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000,

to:

It outputs some statistics like this when it completes the download

Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000

October 13, 2006, at 09:14 PM by Reedy Boy --
Changed lines 1-2 from:

This procedure can be used to recover a dead slug using the inbuilt serial port only no ethernet connection is required.

to:

This procedure can be used to recover a dead slug using the inbuilt serial port, only no ethernet connection is required.

Changed lines 18-21 from:

Windows Hyperterminal

Click Transfer - Send File - select xmodem and browse for your file. You haven't much time before the command will time out, so don't take too long browsing for your file.

to:

In Windows Hyperterminal, Click Transfer - Send File - select xmodem and browse for your file. You haven't much time before the command will time out, so don't take too long browsing for your file.

October 13, 2006, at 09:13 PM by Reedy Boy --
Changed lines 59-62 from:

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

It should just be the following command, but recheck here in case it has changed recently

to:

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

It should just be the following command, but recheck here in case it has changed recently

October 13, 2006, at 09:12 PM by Reedy Boy --
Changed lines 12-13 from:

Enter the command

to:

Enter the command:

Changed lines 20-23 from:

Click Transfer - Send File - select xmodem and browse for your file.

You haven't much time before the command will time out, so don't take too long browsing for your file.

to:

Click Transfer - Send File - select xmodem and browse for your file. You haven't much time before the command will time out, so don't take too long browsing for your file.

Changed line 32 from:
  1. Verify the firmware.\\
to:

Verify the firmware.\\

Changed line 51 from:
  1. Write the firmware to the flash.\\
to:

Write the firmware to the flash.\\

Changed line 68 from:
  1. Restart the slug.\\
to:

Restart the slug.\\

October 13, 2006, at 09:11 PM by Reedy Boy --
Changed lines 1-3 from:

This procedure can be used to recover a dead slug using the inbuilt serial port only no ethernet connection is required.

to:

This procedure can be used to recover a dead slug using the inbuilt serial port only no ethernet connection is required.

Changed lines 12-13 from:

Eter the command

to:

Enter the command

Changed lines 24-25 from:

Wn it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps.

to:

When it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps.

Changed line 41 from:

and you should get a set of numbers calculated from the file. For the R25 firmware, these should be: 3007264634 8388608. If not (and you're not using a different firmware version), you should probably try loading the file again. \\

to:

And you should get a set of numbers calculated from the file. For the R25 firmware, these should be: 3007264634 8388608. If not (and you're not using a different firmware version), you should probably try loading the file again. \\

Deleted line 64:
October 13, 2006, at 09:10 PM by Reedy Boy --
Changed lines 4-16 from:

It is especially useful if you can't get the Ethernet Port to work on the NSLU2

connect the serial cable as indicated here

at the redboot> prompt it is possible to enter various commands.

I've done the upgrade at 115200 baud using xmodem you can adjust the baudrate if required using the baudrate -b 9600

command for instance to set 9600 baud , it will ask for confirmation in the new speed. If you fail to answer 'y' at the new speed prompt it

to:

It is especially useful if you can't get the Ethernet Port to work on the NSLU2 in redboot.

connect the serial cable as indicated here at the redboot> prompt it is possible to enter various commands.

I've done the upgrade at 115200 baud using xmodem you can adjust the baudrate if required using the baudrate -b 9600 command for instance to set 9600 baud , it will ask for confirmation in the new speed. If you fail to answer 'y' at the new speed prompt it

Changed lines 11-15 from:

Not sure which legal values are available for baudrate, admittedly your not likely to want to go at a slower speed

enter the command

to:

Not sure which legal values are available for baudrate, admittedly your not likely to want to go at a slower speed

Eter the command

Changed lines 23-27 from:

You haven't much time before the command will time out, so don't take too long browsing for your file.

when it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps.

to:

You haven't much time before the command will time out, so don't take too long browsing for your file.

Wn it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps.

October 13, 2006, at 05:33 PM by Bullfrog --
Changed lines 35-37 from:

when it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps It outputs some statistics like so Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000

to:

when it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps.

It outputs some statistics like so, Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000,

October 13, 2006, at 05:32 PM by Bullfrog --
Changed lines 35-36 from:

when complete takes 50mins at 115200 baud hyper terminal claims 2916cps

to:

when it completes, it will take roughly 50mins at 115200 baud hyper terminal claims 2916cps It outputs some statistics like so Raw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000 xyzModem - CRC mode, 65537(SOH)/0(STX)/0(CAN) packets, 3 retries

Deleted lines 56-58:
  1. Write the firmware to the flash.\\
Added lines 58-64:

The checksum for Unslung 6.8 is:

RedBoot> cksum
Computing cksum for area 0x01000000-0x01800000
POSIX cksum = 1505985901 8388608 (0x59c3856d 0x00800000)
  1. Write the firmware to the flash.
    \\
October 13, 2006, at 05:14 PM by Bullfrog --
Changed lines 7-8 from:

connect the serial cable as indicated here

to:
October 13, 2006, at 05:13 PM by Bullfrog --
Changed lines 66-68 from:

It should just be, but recheck here in case it has changed recently

to:

It should just be the following command, but recheck here in case it has changed recently

October 13, 2006, at 05:12 PM by Bullfrog --
Added lines 66-73:

It should just be, but recheck here in case it has changed recently

fis erase -f 0x50040000 -l 0x20000

Make sure you type it in exactly as you may damage other parts if you make a mistake.

October 13, 2006, at 05:06 PM by Bullfrog --
Changed lines 2-3 from:

using the inbuilt [[AddASerialPort]serial port] only no ethernet connection is required.

to:

using the inbuilt serial port only no ethernet connection is required.

Changed lines 41-46 from:

type cksum

blah de blah de blah

You can us

to:
  1. 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:

    cksum

    and you should get a set of numbers calculated from the file. For the R25 firmware, these should be: 3007264634 8388608. If not (and you're not using a different firmware version), you should probably try loading the file again.

    The checksum for NSLU2_V23R63.bin is:
RedBoot> cksum
Computing cksum for area 0x01000000-0x01800000
POSIX cksum = 4056400472 8388608 (0xf1c7c258 0x00800000)
  1. Write the firmware to the flash.

    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
  2. Restart the slug.

    With fingers still crossed, type:

    reset

    Be ready to celebrate when you hear that strangled little beep it makes as it finishes booting and is ready to be used.

\\

October 13, 2006, at 05:02 PM by Bullfrog --
Changed lines 1-4 from:

This procedure can be used to recover a dead slug using the inbuilt serial port.

It is especially useful if you can't get the Ethernet Port to work on the NSLU2

to:

This procedure can be used to recover a dead slug using the inbuilt [[AddASerialPort]serial port] only no ethernet connection is required.

It is especially useful if you can't get the Ethernet Port to work on the NSLU2

Changed lines 11-15 from:

I've done the upgrade at 115200 baud using xmodem you can adjust the baudrate if required using the baudrate -b 9600 command for instance to set 9600 baud.

Not sure which legal values are available for baudrate admittedly your not likely to want to go at a slower speed

to:

I've done the upgrade at 115200 baud using xmodem you can adjust the baudrate if required using the baudrate -b 9600

command for instance to set 9600 baud , it will ask for confirmation in the new speed. If you fail to answer 'y' at the new speed prompt it reverts back to the original speed.

Not sure which legal values are available for baudrate, admittedly your not likely to want to go at a slower speed

Changed lines 28-31 from:

Windows Hyperterminal click Transfer - Send File - select xmodem and browse for your file.

You haven't much time before the command will time out, so don't take too long browsing for your file.

to:

Windows Hyperterminal

Click Transfer - Send File - select xmodem and browse for your file.

You haven't much time before the command will time out, so don't take too long browsing for your file.

October 13, 2006, at 04:50 PM by Bullfrog -- How to firmware upgrade using only the serial port
Added lines 1-35:

This procedure can be used to recover a dead slug using the inbuilt serial port.

It is especially useful if you can't get the Ethernet Port to work on the NSLU2

connect the serial cable as indicated here

at the redboot> prompt it is possible to enter various commands.

I've done the upgrade at 115200 baud using xmodem you can adjust the baudrate if required using the baudrate -b 9600 command for instance to set 9600 baud.

Not sure which legal values are available for baudrate admittedly your not likely to want to go at a slower speed

enter the command

load -r -v -b 0x01000000 -m xmodem

And using your terminal emulator start an upload using xmodem protocol.

Windows Hyperterminal click Transfer - Send File - select xmodem and browse for your file.

You haven't much time before the command will time out, so don't take too long browsing for your file.

when complete takes 50mins at 115200 baud hyper terminal claims 2916cps

You can use zmodem if required command is

load -r -v -b 0x01000000 -m zmodem

type cksum

blah de blah de blah

You can us

view · edit · print · history · Last edited by Rob Lockhart.
Based on work by Bullfrog, mrkzander, and Reedy Boy.
Originally by Bullfrog.
Page last modified on November 17, 2008, at 05:23 AM