cancel
Showing results for 
Search instead for 
Did you mean: 

Failed Software Upgrade SPS08030h to SPR08095g

kvon12
New Contributor III

Hello, I tried to update the software on a ICX 7250-48 from sps08030h to spr08095g. The upgrade failed and now I'm getting the messages below. What can i do to recover the switch with a working image? Thanks 

NAND read: device 0 offset 0x4000000, size 0x2000000
................................................................ 33554432 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
could not boot from secondary, no valid image; trying to boot from primary
BOOTING image from Primary

NAND read: device 0 offset 0x0, size 0x2000000
................................ 33554432 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!

ICX7250-Boot> show_image
===========================
Primary :
NAND read: device 0 offset 0x0, size 0x200
512 bytes read: OK
SPR08095g(60787539)
Secondary:
NAND read: device 0 offset 0x4000000, size 0x200
512 bytes read: OK
SPR08095g(60787539)
===========================

ICX7250-Boot> printenv
baudrate=9600
ipaddr=10.14.234.96
serverip=10.14.202.36
netmask=255.255.255.0
gatewayip=10.14.234.1
uboot=spz10106.bin
image_name=SPS08030h.bin
ver=10.1.06T215 (Dec 14 2015 - 13:11:19)

 

1 ACCEPTED SOLUTION

BenBeck
Moderator
Moderator

You need to go through 8080f if you are upgrading from that old of code. Try recovering to 8080f and then upgrading to 8080f and then to 8095:

setenv ipaddr <device IP address> - set ip address
setenv netmask <255.255.255.0> - set subnet mask
setenv serverip <xxx.xxx.xxx.xxx> - set tftp server address
setenv gatewayip <xxx.xxx.xxx.xxx> - set gateway address
printenv
- Try to ping your TFTP server.  If you cannot ping, check your connections. Once ping is successful, enter these commands:
setenv uboot spz10106.bin (change boot code image as needed)
setenv image_name sps08080f.bin (change OS image as needed)
saveenv
tftpboot

*load 8080f to flash via normal method and reboot

*then load 8095 via normal method and reboot one final time

 

Ben Beck, RCNA, RCNI, Principal Technical Support Engineer
support.ruckuswireless.com/contact-us

View solution in original post

5 REPLIES 5

kvon12
New Contributor III

spoke to soon. I was able to figure out how to resolve this.