NSLU2-Linux
view · edit · print · history

Main.UpSlug History

Hide minor edits - Show changes to markup

February 13, 2009, at 11:17 PM by bcrowell -- didn\'t work for me
Changed lines 146-150 from:

--tlhackque

to:

--tlhackque

I tried using upslug2, and it didn't work for me. Upslug couldn't find the slug. I had the two machines connected directly via the ethernet port (no hub or router), and the slug was flashing red/green.

--bcrowell

July 06, 2008, at 07:07 PM by Jac Goudsmit --
Changed lines 3-4 from:

UpSlug has been verified to work with the NAS200, but you will have to use a NAS200 image of course, and you will have to use the -f option because NAS200 images don't have the SerComm signature. This is great if you flashed the NAS200 with a bad image but you can still access Redboot through the serial port or via Telnet. Unfortunately it will not save you if you bricked your NAS200 by typing "flash" at the command prompt.

to:

UpSlug has been verified to work with the NAS200, but you will have to use a NAS200 image of course, and you will have to use the -f option because NAS200 images don't have the SerComm signature (if you make a mistake, you can always do it again because the Redboot area in memory will not be overwritten as long as you use -u, not -U). This is great if you flashed the NAS200 with a bad image but you can still access Redboot through the serial port or via Telnet. Unfortunately it will not save you if you bricked your NAS200 by typing "flash" at the command prompt.

July 06, 2008, at 06:45 PM by Jac Goudsmit --
Added lines 3-4:

UpSlug has been verified to work with the NAS200, but you will have to use a NAS200 image of course, and you will have to use the -f option because NAS200 images don't have the SerComm signature. This is great if you flashed the NAS200 with a bad image but you can still access Redboot through the serial port or via Telnet. Unfortunately it will not save you if you bricked your NAS200 by typing "flash" at the command prompt.

August 22, 2007, at 08:52 PM by anonymous --
Added lines 24-26:
August 10, 2007, at 04:30 AM by dharple -- upslug2 wireless issues
Added lines 103-108:
  • 10 Aug 2007; while uploading di-nslu2.bin (Debian 4.0), upslug2 (v11-1) would repeatedly time out at:
    * 5bd87f+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU*------------------

Switching from a wireless NIC to a wired one fixed it. (dharple)

December 31, 2006, at 01:02 AM by tlhackque -- Describe a cause of no slugs found (Gobble, Gobble.)
Changed lines 126-135 from:

(jbowler: these changes, plus others, are in upslug 1.14)

to:

(jbowler: these changes, plus others, are in upslug 1.14)

For upslug -r to work, the download process must be running. /etc/rc.d/rc.1 should start it, but - at least in my environment - this is commented out. I did this a long time ago because I don't like the idea of an unsecured service that will reboot (and reflash) hardware. I think this is also true in the current release. In any case, if upslug reports

Finding Slugs... 0 found upslug: no slugs found, turkey problems?

and you have routes and cables properly configured, telnet into the slug and do a ps | grep download. If it's not running, ru /sbin/download to start it.

--tlhackque

April 24, 2006, at 02:15 PM by ironstorm --
Changed lines 1-2 from:

UpSlug is a (Linux / MacOS? X / but not Windows) tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed; it won't work if you have routers or NAT devices between you and the NSLU2, though WiFi? via a wireless router is OK).

to:

UpSlug is a (Linux / MacOS? X / but not Windows - Windows users use SercommFirmwareUpdater) tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed; it won't work if you have routers or NAT devices between you and the NSLU2, though WiFi? via a wireless router is OK).

January 17, 2006, at 11:38 PM by frankvh --
Changed lines 1-2 from:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed; it won't work if you have routers or NAT devices between you and the NSLU2, though WiFi? via a wireless router is OK).

to:

UpSlug is a (Linux / MacOS? X / but not Windows) tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed; it won't work if you have routers or NAT devices between you and the NSLU2, though WiFi? via a wireless router is OK).

November 29, 2005, at 11:55 PM by vapier -- make the upgrade details more prominent by giving them their own section
Changed lines 21-23 from:

UpSlug must be run as root or with the sudo command.
If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter RedBoot upgrade mode. There are two ways to do this. First, you can interrupt RedBoot in the normal way described here and then type upgrade at the RedBoot prompt. If this fails (it can be difficult to get the timing right):

to:

UpSlug must be run as root or with the sudo command.

Switch the nslu2 into Upgrade mode

If you want to upgrade your slug without letting your NSLU2 reach the "running" state, you need to enter RedBoot upgrade mode. There are two ways to do this. First, you can interrupt RedBoot in the normal way described here and then type upgrade at the RedBoot prompt. If this fails (it can be difficult to get the timing right):

September 11, 2005, at 05:42 PM by Phil Endecott -- UpSlug works via WiFi
Changed lines 1-2 from:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed, it doesn't work if you have anything between you and the NSLU2 like routers or NAT devices)

to:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed; it won't work if you have routers or NAT devices between you and the NSLU2, though WiFi? via a wireless router is OK).

September 05, 2005, at 04:36 AM by jbowler --
Changed lines 10-11 from:

The release at the time this page was last updated is 1.14 (of upslug.c).

to:

The release at the time this page was last updated is 1.17 (of upslug.c).

September 05, 2005, at 04:36 AM by jbowler -- Update for changes in upslug 1.17
Changed lines 39-40 from:

Verification of the flash image seems to be non-functional, however the download command has never been seen to produce a bad image if it succeeds.

to:

Verification of the flash image is non-functional in this version, however this is fixed in 1.17 and later.

1.16 (and later) also fixes a problem on heavily loaded networks when responses from the NSLU2 may get dropped.

Even in 1.17 there are probably still errors in the protocol handling. UpSlug2 should fix all of these since the protocol return codes are verified correctly.

Added lines 53-54:

If NSLU2 response packets are duplicated (resulting in an out of sequence response) upslug will output a + character and continue looking for the expected response packet (changed in 1.16).

Changed lines 61-62 from:

The following entries refer to problems with upslug which should now all be fixed. Please report any occurence of these problems with the latest (1.14) version, as well as any new problems!

to:

The following entries refer to problems with upslug which should now all be fixed. Please report any occurence of these problems with the latest (1.17) version, as well as any new problems!

Added lines 109-110:

[jbowler: UpSlug2 does this by checking the hardware ID - this comes out of the tail of the RedBoot partition when it is written by LinkSys?. This may cause UpSlug2 to fail to recognise some slugs, if they have a different ID.]

September 04, 2005, at 06:24 PM by jbowler -- Added note about UpSlug2
Added lines 3-4:

UpSlug2 is a completely rewritten version of this tool which is more robust and flexible, though it still requires an ethernet connection to the NSLU2.

June 13, 2005, at 08:38 PM by tman --
Changed lines 1-2 from:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed, it doesn't work if between you and the NSLU2 are routers or NAT devices).

to:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed, it doesn't work if you have anything between you and the NSLU2 like routers or NAT devices)

Changed lines 12-18 from:
-i [interface name]interface is set to the interface specified. Defaults to eth0.
-s [slug_id]will communicate with the slug specified instead of letting the user choose. Format: 00:11:22:33:44:55
-u [image_name]uploads the firmware specified.
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm JTAG support before testing this.
-rresets the slug.
-fdoes not give warning messages.
to:
-i [interface name]Interface is set to the interface specified. Defaults to eth0.
-s [slug_id]Will communicate with the slug specified instead of letting the user choose. Format: 00:11:22:33:44:55
-u [image_name]Uploads the firmware specified.
-U [image_name]Same as -u but erases the entire contents of the flash (including redboot). Please confirm JTAG support before testing this.
-rResets the slug.
-fForce the reflash. Suppress prompts.
Changed lines 20-21 from:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described here and then type upgrade at the redboot prompt. If this fails (it can be difficult to get the timing right):

to:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter RedBoot upgrade mode. There are two ways to do this. First, you can interrupt RedBoot in the normal way described here and then type upgrade at the RedBoot prompt. If this fails (it can be difficult to get the timing right):

Changed line 33 from:
  1. upslug hangs (the download stops) in the presence of high levels of network activity.
to:
  1. UpSlug hangs (the download stops) in the presence of high levels of network activity.
Changed lines 49-50 from:

With the current OpenSlug and possibly with LinkSys? software the NSLU2 must be in upgrade mode before upslug can see it. This is because OpenSlug does not currently listen for the packets used in the upgrade protocol.

to:

With the current OpenSlug, new (> v4.20 beta) Unslung versions the NSLU2 must be in upgrade mode before UpSlug can see it. This is because OpenSlug does not currently listen for the packets used in the upgrade protocol.

Changed lines 98-100 from:

1) maybe by product ID (though that wont for for me since I stuffed mine up a while back) 2) By MAC Address 00:04:5a:xx:yy:zz

to:
  1. Maybe by product ID (though that wont for for me since I stuffed mine up a while back)
  2. By MAC Address 00:04:5a:xx:yy:zz
Changed lines 104-111 from:

I decided to fix it myself since my NSLU2 is not bootable anyway. I made some changes and it worked. upslug restored the firmware without any trouble. The major change is to ignore the error and let it continue to write.

I hacked upslug.c a little bit, below are changes:

  • Change strcmp to strcasecmp so it can idetify Mac address in upper case
to:

I decided to fix it myself since my NSLU2 is not bootable anyway. I made some changes and it worked. upslug restored the firmware without any trouble. The major change is to ignore the error and let it continue to write.

I hacked upslug.c a little bit, below are the changes:

  • Change strcmp to strcasecmp so it can identify Mac address in upper case
Changed lines 112-113 from:

I compiled upslug under Redhat 7.2 and used it to flash firmware for my NSLU2 and it worked. I tar and gzip binary and source files to ctsai.erinna.com/upslug.tar.gz. Would someone merge my changes to the source!

to:

I compiled upslug under Redhat 7.2 and used it to flash firmware for my NSLU2 and it worked. I tar and gzip binary and source files to http://ctsai.erinna.com/upslug.tar.gz. Would someone merge my changes to the source!

June 13, 2005, at 06:58 PM by ilg -- don't try this if you do not have direct Ethernet access to the NSLU2
Changed lines 1-2 from:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet.

to:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet (direct Ethernet access is needed, it doesn't work if between you and the NSLU2 are routers or NAT devices).

June 02, 2005, at 05:43 AM by jbowler -- Update for new upslug version
Added lines 8-9:

The release at the time this page was last updated is 1.14 (of upslug.c).

Changed lines 20-21 from:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described here and then type upgrade at the redboot prompt. Secondly, it is reported that holding the reset button in when turning on the slug will put it in upgrade mode though I have not done this personally.

to:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described here and then type upgrade at the redboot prompt. If this fails (it can be difficult to get the timing right):

  1. Power off the slug.
  2. Hold the reset button in (the button is behind the small hole in the back of the case.)
  3. Press and release the power button to turn the slug on (while still holding the reset button on.)
  4. Wait about 10 seconds until the ready/status LED turns from amber to red, immediately release the reset button.

After these steps the slug will be in upgrade mode - the ready/status LED will flash alternately red and green. This continues until the slug is reset by the upload software.

UpSlug status and problems

The changes in release 1.14 of upslug.c are believed to fix the following problems:

  1. upslug hangs (the download stops) in the presence of high levels of network activity.
  2. Some upslug commands could get ignored by the NSLU2 because the network packet containing the command is lost and upslug was not checking for successful receipt.
  3. Some error conditions were not detected.

Verification of the flash image seems to be non-functional, however the download command has never been seen to produce a bad image if it succeeds.

Upslug output

During download upslug outputs a progress indicator every 128KBytes. The indicator is a hexadecimal digit, thus the indicator goes through 4 cycles 0 to f for the 8MByte flash image.

The data is transmitted in 512 byte packets. If the NSLU2 does not acknowledge receipt of a packet it is retransmitted and a single * character is output.

Because the erase takes a long time a number of * characters are output initially (while upslug waits for response to the first write packet), then upslug outputs the message Writing flash and starts outputting progress digits.

The importance of upgrade mode

With the current OpenSlug and possibly with LinkSys? software the NSLU2 must be in upgrade mode before upslug can see it. This is because OpenSlug does not currently listen for the packets used in the upgrade protocol.

Problems with upslug

The following entries refer to problems with upslug which should now all be fixed. Please report any occurence of these problems with the latest (1.14) version, as well as any new problems!

Added lines 116-117:

(jbowler: these changes, plus others, are in upslug 1.14)

May 23, 2005, at 06:32 PM by ChrisE --
Deleted lines 29-35:

Planned Implementations (Christopher's TODO list)

  • eall implementation (done needs tested)
  • Windows version (in progress slowly...)

May 23, 2005, at 06:13 PM by C Tsai --
Changed lines 74-75 from:

Even I used version 1.13 I still got "Erasing Flash...upslug: Resource temporarily unavailable"

to:

Even I used version 1.13 I still got Erasing Flash...upslug: Resource temporarily unavailable

Added line 80:
Changed lines 82-84 from:

1) change strcmp to strcasecmp so it can idetify Mac address in upper case 2) change all &pkt to pkt. I am wondering why it works for others because from a standard C point of view, memset(&pkt, 0, ...) seems not right. 3) Ignore recvfrom() error in write_image

to:
  • Change strcmp to strcasecmp so it can idetify Mac address in upper case
  • Change all &pkt to pkt. I am wondering why it works for others because from a standard C point of view, memset(&pkt, 0, ...) seems not right.
  • Ignore recvfrom() error in write_image
May 23, 2005, at 06:05 PM by C Tsai -- Modify upslug.c to make it to work
Added lines 72-83:

Got upslug to work

Even I used version 1.13 I still got "Erasing Flash...upslug: Resource temporarily unavailable" I decided to fix it myself since my NSLU2 is not bootable anyway. I made some changes and it worked. upslug restored the firmware without any trouble. The major change is to ignore the error and let it continue to write. I hacked upslug.c a little bit, below are changes: 1) change strcmp to strcasecmp so it can idetify Mac address in upper case 2) change all &pkt to pkt. I am wondering why it works for others because from a standard C point of view, memset(&pkt, 0, ...) seems not right. 3) Ignore recvfrom() error in write_image I compiled upslug under Redhat 7.2 and used it to flash firmware for my NSLU2 and it worked. I tar and gzip binary and source files to ctsai.erinna.com/upslug.tar.gz. Would someone merge my changes to the source!

May 09, 2005, at 05:57 AM by Cory Sharp -- May need RedBook \"upgrade\" for upslug to detect the nslu2
Added lines 63-64:
  • 8 May 2005: upslug suddenly stopped detecting my nslu2 even though I could still arping it. With access to the RedBoot prompt, putting RedBoot into upgrade mode with "upgrade" allowed upslug to detect the nslu2 and proceed with the upload. Thanks jbowler for the tip. (corys)
April 20, 2005, at 10:35 AM by tman --
Changed lines 4-7 from:

The code can be found here:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup (this is the "upslug" module in the nslu.sf.net CVS repository).

to:

The code can be found in the upslug module of the nslu.sf.net CVS repository

Changed lines 41-45 from:
 Verifying File Contents...
 Counted Blocks:1073851176
 Needed Blocks:16384
 Error: File not large enough, use --upload-force to override
to:
Verifying File Contents...
Counted Blocks:1073851176
Needed Blocks:16384
Error: File not large enough, use --upload-force to override
Changed lines 66-68 from:
 I'm not sure how we can do that...
 1) maybe by product ID (though that wont for for me since I stuffed mine up a while back)
 2) By MAC Address 00:04:5a:xx:yy:zz
to:

I'm not sure how we can do that... 1) maybe by product ID (though that wont for for me since I stuffed mine up a while back) 2) By MAC Address 00:04:5a:xx:yy:zz

February 13, 2005, at 01:18 PM by rwhitby --
Changed line 6 from:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

to:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup (this is the "upslug" module in the nslu.sf.net CVS repository).

January 14, 2005, at 11:22 PM by ChrisE --
Changed line 60 from:

This issue has been resolved.

to:

This issue has been resolved in version 1.13.

January 14, 2005, at 11:22 PM by ChrisE --
Changed lines 59-60 from:

but I don't know beans about Unix socket programming so I stopped there.

to:

but I don't know beans about Unix socket programming so I stopped there.
This issue has been resolved.

January 13, 2005, at 04:03 PM by MikeB --
Changed line 52 from:
  • 13 Jan 2005: mikeb reports a bug on his system: upslug dies with an error (Gentoo Linux, kernel v2.6.9-r1, gcc v3.3.4) Here's a section of the output:
to:
  • 13 Jan 2005: mikeb reports a bug on his system: upslug dies with an error (upslug version:1.12, from CVS. Gentoo Linux, kernel v2.6.9-r1, gcc v3.3.4) Here's a section of the output:
January 13, 2005, at 03:58 PM by MikeB --
Changed lines 52-61 from:

to:
  • 13 Jan 2005: mikeb reports a bug on his system: upslug dies with an error (Gentoo Linux, kernel v2.6.9-r1, gcc v3.3.4) Here's a section of the output:
 Do you really want to upgrade the slug(y/n)? y
 Requesting upgrade...comfirmed
 Erasing Flash...upslug: Resource temporarily unavailable

I tracked this message down to the first call to recvfrom() in the write_image() routine, but I don't know beans about Unix socket programming so I stopped there.

My slug was hosed after upslug crashed (blinking red light; I presume it was waiting for more data) but after spending a couple minutes emerging TFTP and fiddling with ifconfig (to move my server to the 192.168.0.* subnet where it was visible to the slug) I got unslung installed using the HowTo.RecoverFromABadFlash TFTP instructions?. My thanks to all of you for figuring out all these methods! (mikeb)

January 11, 2005, at 07:28 AM by ChrisE --
Changed lines 34-38 from:
  • partial erases/writes (might not be possible)
  • eall implementation (for complete redboot included upgrades)
  • Process for easy 3.x upgrades (in progress...)
  • a reset function that works more reliably (may not be possible)
  • Windows version (in progress slowly
to:
  • eall implementation (done needs tested)
  • Windows version (in progress slowly...)
January 08, 2005, at 07:24 PM by devil26 --
Changed line 53 from:
to:

Works for me (devil26)

January 08, 2005, at 07:43 AM by ChrisE --
Changed lines 51-52 from:

The image being loaded is built by oe.

to:

The image being loaded is built by oe.
This should be fixed now, please test.

Deleted lines 53-55:

FIX --> This is because variable "counted_blocks" in function verify_file_contents() is not properly initialised to 0.
Thank you for catching this. I will fix it ASAP.

January 07, 2005, at 10:11 PM by ChrisE --
Changed lines 54-55 from:

verify_file_contents() is not properly initialised to 0. Thank you for catching this. I will fix it ASAP

to:

verify_file_contents() is not properly initialised to 0.
Thank you for catching this. I will fix it ASAP.

January 07, 2005, at 10:11 PM by ChrisE --
Added line 55:

Thank you for catching this. I will fix it ASAP

January 07, 2005, at 07:44 PM by devil26 --
Added lines 53-54:

FIX --> This is because variable "counted_blocks" in function verify_file_contents() is not properly initialised to 0.

December 30, 2004, at 07:26 AM by dyoung --
Changed lines 58-61 from:
to:
  • It might be nice to have upslug only talk to slugs. Right now it detects other stuff on my net like print server. (dyoung)
 I'm not sure how we can do that...
 1) maybe by product ID (though that wont for for me since I stuffed mine up a while back)
 2) By MAC Address 00:04:5a:xx:yy:zz
December 23, 2004, at 09:48 PM by ka6sox --
Changed line 8 from:

Instructions to build are found http://nslu2-linux.org/wiki/Main/UpSlug/UpSlugBuildInstructions here

to:

Instructions to build are found UpSlugBuildInstructions here?

December 23, 2004, at 09:47 PM by ka6sox --
Added lines 8-9:

Instructions to build are found http://nslu2-linux.org/wiki/Main/UpSlug/UpSlugBuildInstructions here

December 21, 2004, at 01:46 AM by ChrisE --
Changed lines 13-14 from:
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm\\

JTAG support before testing this.||

to:
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm JTAG support before testing this.
Changed line 18 from:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described HowTo.TelnetIntoRedBoot here? and then type upgrade at the redboot prompt. Secondly, it is reported that holding the power button in when turning on the slug will put it in upgrade mode though I have not done this personally.

to:

If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described HowTo.TelnetIntoRedBoot here? and then type upgrade at the redboot prompt. Secondly, it is reported that holding the reset button in when turning on the slug will put it in upgrade mode though I have not done this personally.

December 21, 2004, at 01:45 AM by ChrisE --
Changed lines 13-14 from:
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm\\ J

TAG support before testing this.||

to:
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm\\

JTAG support before testing this.||

December 21, 2004, at 01:44 AM by ChrisE --
Changed lines 10-13 from:
--resetResets the slug.
--upload image_name.imgUploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.imgUploads the firmware without checking for the Sercomm signature or proper length.
--slugid 00:11:22:33:44:55 --some_commandSkips the slug selection prompt, looks for the slug ID given and then attempts to perform the command on that slug.
to:
-i [interface name]interface is set to the interface specified. Defaults to eth0.
-s [slug_id]will communicate with the slug specified instead of letting the user choose. Format: 00:11:22:33:44:55
-u [image_name]uploads the firmware specified.
-U [image_name]same as -u but erases the entire contents of the flash (including redboot). Please confirm\\ J

TAG support before testing this.||

-rresets the slug.
-fdoes not give warning messages.
Changed line 33 from:
  • partial erases/writes
to:
  • partial erases/writes (might not be possible)
Changed lines 35-41 from:
  • Process for easy 3.x upgrades
  • clean-up code
  • make it so that options can be used in any order
  • add a --help option that summarizes commands
  • a reset function that works more reliably
  • Better verification of proper parameters
  • Windows version
to:
  • Process for easy 3.x upgrades (in progress...)
  • a reset function that works more reliably (may not be possible)
  • Windows version (in progress slowly
Changed line 57 from:
  • Add a -i option for interface name (which defaults to eth0 if not specifice). Then I can upslug on eth1 without recompiling :)
to:
December 16, 2004, at 07:17 AM by ChrisE --
Changed line 28 from:

Planned Implementations

to:

Planned Implementations (Christopher's TODO list)

Added lines 30-36:
  • partial erases/writes
  • eall implementation (for complete redboot included upgrades)
  • Process for easy 3.x upgrades
  • clean-up code
  • make it so that options can be used in any order
  • add a --help option that summarizes commands
  • a reset function that works more reliably
Changed line 38 from:
  • Windows version (depends on interest level)
to:
  • Windows version
December 15, 2004, at 07:29 PM by g2 --
Changed line 51 from:
to:
  • Add a -i option for interface name (which defaults to eth0 if not specifice). Then I can upslug on eth1 without recompiling :)
December 03, 2004, at 10:30 PM by dyoung --
Changed lines 37-45 from:
  • There has been a report of file size being reported wrongly, please post here and with a bug report if you have a similar issue or any other issue.
to:
  • I must use the --upload force option always. (dyoung)
 (messages)
 Verifying File Contents...
 Counted Blocks:1073851176
 Needed Blocks:16384
 Error: File not large enough, use --upload-force to override

The image being loaded is built by oe.

December 03, 2004, at 10:30 PM by ChrisE --
Changed line 37 from:
to:
  • There has been a report of file size being reported wrongly, please post here and with a bug report if you have a similar issue or any other issue.
November 29, 2004, at 07:44 AM by ChrisE --
Changed lines 15-16 from:

UpSlug must be run as root or with the sudo command.

to:

UpSlug must be run as root or with the sudo command.
If you want to upgrade your slug without letting your NSLU2 reach "running" state first. You need to enter redboot upgrade mode. There are two ways to do this. First, you can interrupt redboot in the normal way described HowTo.TelnetIntoRedBoot here? and then type upgrade at the redboot prompt. Secondly, it is reported that holding the power button in when turning on the slug will put it in upgrade mode though I have not done this personally.

November 23, 2004, at 11:24 PM by ChrisE --
Changed line 1 from:

UpSlug is a tool to flash your NSLU2 from an external computer running linux on the same subnet.

to:

UpSlug is a tool to flash your NSLU2 from an external computer on the same subnet.

November 23, 2004, at 02:14 AM by ChrisE --
Changed line 1 from:

UpSlug is a tool to flash your NSLU2 from a PC running linux on the same subnet.

to:

UpSlug is a tool to flash your NSLU2 from an external computer running linux on the same subnet.

November 23, 2004, at 02:05 AM by ChrisE --
Changed line 1 from:

Upslug is a tool to flash your NSLU2 from within the running linux environment on the NSLU2.

to:

UpSlug is a tool to flash your NSLU2 from a PC running linux on the same subnet.

November 23, 2004, at 01:16 AM by jkpeters_37 --
Changed line 1 from:

Upslug is a tool to flash your NSLU2 from within the running linux environemt on the NSLU2.

to:

Upslug is a tool to flash your NSLU2 from within the running linux environment on the NSLU2.

November 23, 2004, at 01:14 AM by jkpeters_37 --
Changed line 3 from:

Upslug download tool is now in alpha phase.

to:

The UpSlug firmware upload tool is now in alpha phase.

Changed line 12 from:
--upload-force image_name.imgUploads the firmware without checking for the Sercomm signature or propwer length.
to:
--upload-force image_name.imgUploads the firmware without checking for the Sercomm signature or proper length.
Changed line 15 from:

Upslug must be run as root or with the sudo command.

to:

UpSlug must be run as root or with the sudo command.

Changed line 21 from:
  • Upslug now has support for multiple slugs
to:
  • UpSlug now has support for multiple slugs
Changed line 42 from:
to:
November 22, 2004, at 05:48 PM by tman --
Changed lines 7-17 from:


Command Line Options:
(Currently upslug must be run as root or with the sudo command) --reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.img uploads the firmware without checking for the Sercomm signature or propwer length.
--slugid 00:11:22:33:44:55 --some_command Skips the slug selection prompt, looks for the slug Id given and then attempts to perform the command on that slug\\

to:
Command Line Options
--resetResets the slug.
--upload image_name.imgUploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.imgUploads the firmware without checking for the Sercomm signature or propwer length.
--slugid 00:11:22:33:44:55 --some_commandSkips the slug selection prompt, looks for the slug ID given and then attempts to perform the command on that slug.

Upslug must be run as root or with the sudo command.

Changed line 21 from:
  • Upslug now has support for multiple slugs
to:
  • Upslug now has support for multiple slugs
Changed line 23 from:
  • Sometimes the slug ignores the reset command even though it receives it -- please manually reset if upslug says that it is done and your system does not reboot in a couple of minutes. Do not reflash your slug if this occurs as it appears to flash incorrectly if you do not reboot first. Upslug can recover from this condition, but it would be better not to have it in the first place.
to:
  • Sometimes the slug ignores the reset command even though it has been received. If upslug says it is done and the slug does not reboot within a couple of minutes then you must manually reset the slug. Do not try to reflash the slug if this occurs as it will not flash correctly. Upslug can recover from this but it is better to just reset and try again.
Added lines 25-27:

Planned Implementations

Deleted lines 28-29:

Planned Implementations

Changed lines 33-35 from:

Please post any issues that you have with this tool here:

to:

Please post any issues that you have with this tool here

Added line 37:
Changed lines 39-41 from:

Feature Request:

to:

Feature Requests

November 22, 2004, at 06:55 AM by ka6sox --
Changed lines 24-25 from:
  • Sometimes the slug ignores the reset command even though it receives it please manually reset if upslug says that it is done and your system does not reboot in a couple of minutes. Do not reflash your slug if this occurs as it appears to flash incorrectly if you do not reboot first. Upslug can recover fromt this condition, but it would be better not to have it in the first place.
to:
  • Sometimes the slug ignores the reset command even though it receives it -- please manually reset if upslug says that it is done and your system does not reboot in a couple of minutes. Do not reflash your slug if this occurs as it appears to flash incorrectly if you do not reboot first. Upslug can recover from this condition, but it would be better not to have it in the first place.
November 20, 2004, at 08:28 AM by ChrisE --
Deleted line 26:

I will add more information here over the next couple of days.

November 19, 2004, at 10:28 PM by ChrisE --
Changed line 17 from:

Skips the sluf selection prompt, looks for the slug Id given and then attempts to perform the command on that slug\\

to:

Skips the slug selection prompt, looks for the slug Id given and then attempts to perform the command on that slug\\

Changed lines 32-33 from:
  • Ability to tell it which unit to talk to at command line, ie
 upslug --slugid 001122334455 --upload foo.img
to:
November 19, 2004, at 10:24 PM by ChrisE --
Added lines 16-17:

--slugid 00:11:22:33:44:55 --some_command Skips the sluf selection prompt, looks for the slug Id given and then attempts to perform the command on that slug\\

November 19, 2004, at 08:26 AM by ChrisE --
Changed lines 30-31 from:
to:
  • Ability to tell it which unit to talk to at command line, ie
 upslug --slugid 001122334455 --upload foo.img
Changed lines 37-38 from:
  • Ability to tell it which unit to talk to at command line, ie
 upslug --slugid 001122334455 --upload foo.img
to:
November 19, 2004, at 05:38 AM by dyoung --
Changed lines 36-37 from:
to:
  • Ability to tell it which unit to talk to at command line, ie
 upslug --slugid 001122334455 --upload foo.img
November 19, 2004, at 01:02 AM by ChrisE --
Added line 18:
November 19, 2004, at 01:01 AM by ChrisE --
Changed lines 10-13 from:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.img uploads the firmware without checking for the Sercomm signature or propwer length.

to:

--reset
resets the slug
--upload image_name.img\\ uploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.img
uploads the firmware without checking for the Sercomm signature or propwer length.

---------------------------------

November 19, 2004, at 01:01 AM by ChrisE --
Changed lines 9-10 from:

(Currently upslug must be run as root or with the sudo command)
--reset\\

to:

(Currently upslug must be run as root or with the sudo command) --reset

Changed line 12 from:

--upload image_name.img\\

to:

--upload image_name.img

Changed line 14 from:

--upload-force image_name.img\\

to:

--upload-force image_name.img

November 19, 2004, at 01:00 AM by ChrisE --
Changed lines 10-12 from:

--reset resets the slug --upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug. --upload-force image_name.img uploads the firmware without checking for the Sercomm signature or propwer length.

to:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.
--upload-force image_name.img uploads the firmware without checking for the Sercomm signature or propwer length.\\

Changed line 16 from:
  • Upslug now has support for multiple slug
to:
  • Upslug now has support for multiple slugs
Added line 24:
  • Windows version (depends on interest level)
November 19, 2004, at 12:59 AM by ChrisE --
Changed lines 16-17 from:


---------------------------------

to:

November 19, 2004, at 12:59 AM by ChrisE --
Changed line 10 from:

--reset resets the slug\\

to:

--reset resets the slug

November 19, 2004, at 12:58 AM by ChrisE --
Changed line 12 from:

--upload-force image_name.img@ uploads the firmware without checking for the Sercomm signature or propwer length.

to:

--upload-force image_name.img uploads the firmware without checking for the Sercomm signature or propwer length.

November 19, 2004, at 12:58 AM by ChrisE --
Added line 12:

--upload-force image_name.img@ uploads the firmware without checking for the Sercomm signature or propwer length.

Changed line 14 from:

As far as testing goes, I have succesfully uploaded Unslung 2.12 and 2.14 twice each using this tool. This should mean that it will work for most images, though there may be problems for people with custom redboots. This may not be the case though more testing will help to determine the completeness of the tools functionality.

to:

This tool has worked consistently for several people. The support for multiple slugs seems to work as well.

Changed line 16 from:
  • Upslug now has support for multiple slugs (appears to be working for dyoung)
to:
  • Upslug now has support for multiple slug
November 19, 2004, at 12:44 AM by kolla --
Added lines 1-2:

Upslug is a tool to flash your NSLU2 from within the running linux environemt on the NSLU2.

November 15, 2004, at 10:29 PM by ChrisE --
Changed line 14 from:
  • Sometimes the slug ignores the reset command even though it receives it. Do not reflash your slug if this occurs as it appears to flash incorrectly. Upslug can recover fromt this condition, but it would be better not to have it in the first place.
to:
  • Sometimes the slug ignores the reset command even though it receives it please manually reset if upslug says that it is done and your system does not reboot in a couple of minutes. Do not reflash your slug if this occurs as it appears to flash incorrectly if you do not reboot first. Upslug can recover fromt this condition, but it would be better not to have it in the first place.
November 15, 2004, at 09:42 PM by ChrisE --
Changed line 13 from:
  • Upslug now has support for multiple slugs (appears to be working for rwhitby and dyoung)
to:
  • Upslug now has support for multiple slugs (appears to be working for dyoung)
November 15, 2004, at 09:42 PM by ChrisE --
Added line 7:

(Currently upslug must be run as root or with the sudo command)\\

November 15, 2004, at 06:12 PM by ChrisE --
Changed line 12 from:
  • Upslug now has support for multiple slugs (not tested)
to:
  • Upslug now has support for multiple slugs (appears to be working for rwhitby and dyoung)
November 15, 2004, at 06:49 AM by ChrisE --
Added line 13:
  • Sometimes the slug ignores the reset command even though it receives it. Do not reflash your slug if this occurs as it appears to flash incorrectly. Upslug can recover fromt this condition, but it would be better not to have it in the first place.
November 15, 2004, at 05:59 AM by ChrisE --
Added lines 12-13:
  • Upslug now has support for multiple slugs (not tested)
Changed line 18 from:
  • Support for multiple Slugs
to:
  • Better verification of proper parameters
November 15, 2004, at 12:45 AM by ChrisE --
Added lines 14-16:

Planned Implementations

  • Support for multiple Slugs
November 14, 2004, at 07:39 AM by ChrisE --
Changed line 10 from:

As far as testing goes, I have succesfully uploaded Unslung 2.12 and 2.14 twice each using this tool. This should mean that it will work for most images, though there may be problems for people with custom redboots. This may not be the case though more testing will help to determine the completeness of the tools functionallity.

to:

As far as testing goes, I have succesfully uploaded Unslung 2.12 and 2.14 twice each using this tool. This should mean that it will work for most images, though there may be problems for people with custom redboots. This may not be the case though more testing will help to determine the completeness of the tools functionality.

November 14, 2004, at 07:37 AM by ChrisE --
Added lines 10-11:

As far as testing goes, I have succesfully uploaded Unslung 2.12 and 2.14 twice each using this tool. This should mean that it will work for most images, though there may be problems for people with custom redboots. This may not be the case though more testing will help to determine the completeness of the tools functionallity.

Added lines 18-20:

Feature Request:

November 14, 2004, at 06:54 AM by ChrisE --
Changed line 1 from:

Upslug download tool is not in alpha phase.

to:

Upslug download tool is now in alpha phase.

November 14, 2004, at 01:55 AM by ChrisE --
Changed lines 7-8 from:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.

to:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.

November 14, 2004, at 01:54 AM by ChrisE --
Changed lines 5-7 from:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.

to:


Command Line Options:
--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.

November 14, 2004, at 01:52 AM by ChrisE --
Changed line 1 from:

Upslug download tool is now in alpha phase.

to:

Upslug download tool is not in alpha phase.

Changed lines 6-7 from:

--reset resets the box
--upload image_name.img uploads the firware specified to the slug, verifies the upload and then resets the slug.

to:

--reset Will reset the box
--upload image_name.img Will upload that firmware to the box, verify the upload and then reset the box.

Changed lines 9-14 from:

I will add more information here over the next couple of days.

to:

I will add more information here over the next couple of days.


Please post any issues that you have with this tool here:

November 14, 2004, at 01:51 AM by ChrisE --
Changed lines 6-7 from:

--reset Will reset the box
--upload image_name.img Will upload that firmware to the box, verify the upload and then reset the box.

to:

--reset resets the slug
--upload image_name.img uploads the firmware image to the slug, verifies the upload and then resets the slug.

November 14, 2004, at 01:49 AM by ChrisE --
Changed line 1 from:

Upslug download tool is not in alpha phase.

to:

Upslug download tool is now in alpha phase.

Changed lines 6-7 from:

--reset Will reset the box
--upload image_name.img Will upload that firmware to the box, verify the upload and then reset the box.

to:

--reset resets the box
--upload image_name.img uploads the firware specified to the slug, verifies the upload and then resets the slug.

November 14, 2004, at 01:01 AM by ChrisE --
Changed line 6 from:

--reset Will reset the box

to:

--reset Will reset the box\\

November 14, 2004, at 01:01 AM by ChrisE --
Changed lines 1-2 from:

The Upslug download tool is in a very early experimental development stage.

to:

Upslug download tool is not in alpha phase. The code can be found here:

Changed line 4 from:

The current prototype can be found at:

to:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

Changed lines 6-7 from:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

to:

--reset Will reset the box --upload image_name.img Will upload that firmware to the box, verify the upload and then reset the box.

Changed line 9 from:

Please do not ask any questions about this tool. It is not even ready for alpha testing yet. Be patient.

to:

I will add more information here over the next couple of days.

September 13, 2004, at 10:30 AM by rwhitby --
Changed lines 1-7 from:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

to:

The Upslug download tool is in a very early experimental development stage.

The current prototype can be found at:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

Please do not ask any questions about this tool. It is not even ready for alpha testing yet. Be patient.

September 13, 2004, at 10:19 AM by rwhitby --
Changed line 1 from:

Describe {{Upslug}} here.

to:

http://cvs.sourceforge.net/viewcvs.py/nslu/upslug/upslug.c?view=markup

Page last modified on February 13, 2009, at 11:17 PM