troubles after FW upgrade Digi CM 32 ver 1.5 to 1.7

Realport
1

After upgrade using http, fwupgrade we are have follow:

Rebooting in 180 seconds…
Bootloader 1.1.3 (Jul 18 2003 - 19:22:45)
CPU : XPC855xxZPnnD4 (50 MHz)
DRAM : 64 MB
FLASH : 8 MB
PC CARD : No card
EEPROM : A Type exist
Ethernet : AUTO-NEGOTIATION
Autoboot Start: 0
[Kernel Image]
Image Address : f0020000
Data Size : 652787 Bytes
Verifying Checksum … OK
[Ram Disk Image]
Image Address : f06d0000
Data Size : 60990 Bytes
Verifying Checksum … OK
Linux version 2.4.2_hhl20 (root@localhost.localdomain) (gcc version 2.95.3 2001031
5 (release/MontaVista)) #760 Mon Apr 18 19:58:55 KST 2005
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2
RTC Time(mm/dd/yy-hh:mm:ss) : 7/28/2005-4:9:50
Decrementer Frequency = 187500000/60
Calibrating delay loop… Oops: kernel access of bad area, sig: 11
NIP: C017F384 XER: A000007F LR: C017F350 SP: C016BFB0 REGS: c016bf00 TRAP: 0300
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: B847D1B7, DSISR: 00000009
TASK = c016a010[0] ‘swapper’ Last syscall: 0
last math 00000000 last altivec 00000000
GPR00: 00000049 C016BFB0 C016A010 0003CE00 00001032 00000001 00000001 00000000
GPR08: C018DB9D B8480000 0000001A FFFFFFFF 35409033 E00A2000 03FF1000 007FFF13
GPR16: 00000000 00000001 007FFF00 FFFFFFFF 03FEC17C 00000000 03FAFEE0 00000003
GPR24: 00000000 03FF1B9C C0180000 C0180000 FFFFFFFF C0190000 00000200 00000049
Call backtrace:
C017F2B4 C017F714 C00021E4
Kernel panic: Attempted to kill the idle task!
In idle task - not syncing
Rebooting in 180 seconds…

New FW uploads have not results :frowning:

-Andrew-

2

I’m not sure why this problem occurred, possibly a corrupt firmware file or the process was interrupted? Seems like the firmware upload didn’t work though, this is not a known problem in other words.

My suggestion would be to run the Disaster Recovery procedure found on page 162 of the manual at this link:
http://ftp1.digi.com/support/documentation/90000301_F.pdf

If that doesn’t get you back up and running, you’ll need to call Technical Support for an RMA of the unit. Serial number would be needed at that time.