List Info

Thread: N12NSLU2Upgrade10FlashErrorE; bricked (can't use Redboot)




N12NSLU2Upgrade10FlashErrorE; bricked (can't use Redboot)
user name
2006-11-22 18:10:03
Bad:  I got a hardware error from my NSLU2 when trying to
reflash it.
 I think the recent thunderstorms and flickering power might
have had
something to do with it.

Worse:  I messed up RedBoot and can no longer telnet in.

Any advice, either to recover from this or to fix/avoid it
next time?
 See below for details...


I successfully flashed my new NSLU2 with Unslung 6.8.  A few
days
later, I attempted to flash it with the unofficial
debian-installer
RC1 image.

First I tried to use the web upgrade UI.  After about a
minute, I got
a Javascript alert saying something like "Bad image or
filename."  I
retried and got the same error.

Then I tried using upslug2, and got this error repeatedly:

> $ sudo upslug2 -i di-nslu2.bin 
> LKG7E999B 00:0f:66:7e:99:9b Product ID: 1 Protocol ID:0
Firmware
Version: R23V63 [0x2363]
> Upgrading LKG7E999B 00:0f:66:7e:99:9b
>     . original flash contents  * packet timed out
>     ! being erased             - erased
>     u being upgraded           U upgraded
>     v being verified           V verified 
>
>   Display:
>     <status> <address completed>+<bytes
transmitted but not completed>
>   Status:
>     * timeout occured          + sequence error
detected
>
> *      0+0005bf
...u--------------------------------------------------------
----
> broadcast: flash programming error
[N12NSLU2Upgrade10FlashErrorE]
>  The NSLU2 reported an error reprogramming the flash,
this is
>  potentially a serious hardware problem, however it is
probably
>  worth while retrying the upgrade to see if the problem
is
>  temporary.


Next I telneted into RedBoot and attempted to do a manual
reflash:

> RedBoot> fis write -f 0x50060000 -b 0x01060000 -l
0x7a0000
> * CAUTION * about to program FLASH
>             at 0x50060000..0x507fffff from 0x01060000 -
continue
(y/n)? y
> ... Erase from 0x50060000-0x50800000: ...........Err =
a0
> 
> Can't erase region at 0x501c0000: Error trying to erase

I used "fis erase" to erase manually.  Each time
it errored out at a
higher address, until eventually it succeeded.  Then I tried
to "fis
write" again:

> RedBoot> fis write -f 0x50060000 -b 0x01060000 -l
8192
> * CAUTION * about to program FLASH
>             at 0x50060000..0x5007ffff from 0x01060000 -
continue
(y/n)? y
> ... Erase from 0x50060000-0x50080000: .
> Err = 90
> Can't program region at 0x50060000: Error trying to
program

I couldn't find any way to make this error go away.

Even worse, when experimenting with "fis write"
later I accidentally
erased the RedBoot partition, and now RedBoot doesn't even
start up. 
(This was a stupid mistake, which I won't make again.)

Is there any way to recover from this without JTAG?  And for
future
reference, is there anything useful to be about the flash
programming
errors above?





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://g
roups.yahoo.com/group/nslu2-general/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http
://groups.yahoo.com/group/nslu2-general/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:nslu2-general-digest@yahoogroups.com 
    mailto:nslu2-general-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
    nslu2-general-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.c
om/info/terms/
 

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )