PortServer CM 32 firmware upgrade failure

Digi CM & Passport
1

anyone know how to recover from an upgrade failure.

I have tried booting the latest image from a tftp server, but the bootup fails during the recognition of the serial ports. here is the bootup process including the failure and reboot.

Thanks for any help.

Booting from Original Boot 1.9.7a (Jan/02/02)

Testing RAM … FULL TEST
This test takes a few seconds.
Press if you want to cancel it.
Memory detected: 65536 Kbytes
Test in progress: 65536 Kbytes OK
Testing Flash [Configuration] … OK
Testing Flash [Op Code] … NOK
Interface Cards Detected … OK
32-UART ports detected
Testing Ethernet … OK
Testing Real Time Clock … OK
Testing Router Serial Number… OK
Router ID is 118176010000C1

Watchdog timer ((A)ctive or (I)nactive) [I] : a
Firmware boot from ((F)lash or (N)etwork) [F] : n
Boot type ((B)ootp,(T)ftp or Bot(H)) [T] : t
Boot File Name [zvmppcdg.bin] : zImage
IP address assigned to Ethernet interface [192.168.1.178] : 192.168.1.60
Server’s IP address [192.168.160.1] : 192.168.1.51
MAC address assigned to Ethernet [00:40:9D:22:74:37] :
Network boot.

Sending a tftp request.
Trying file : zImage
Booting from 192.168.1.51 … 3600 kb

Network boot completed.
Received 3693200 bytes.
CRC is … OK

Entry Point = 0x00210020
loaded at: 00210020 0021C398
relocated to: 00200020 0020C398
board data at: 002062C8 002064A8
relocated to: 001FF120 001FF300
zimage at: 00217000 0027F957
relocated to: 03C7F000 03CE7957
initrd at: 0027F957 00594793
relocated to: 03CEA000 03FFEE3C
avail ram: 00280000 03CEA000

Linux/PPC load: root=/dev/ram ramdisk=0x00007000
Uncompressing Linux…done.
Now booting the kernel
Linux version 2.2.14 (root@cm.digi.com) (gcc version 2.95.2 19991030 (2.95.3 pr2
Boot arguments: root=/dev/ram ramdisk=0x00007000
CPM interrupt vector 0 handler c00b1a54
time_init: decrementer frequency = 180000000/60
Calibrating delay loop… 47.82 BogoMIPS
Memory: 60560k available (736k kernel code, 1056k data, 28k init) [c0000000,c40]
Flash addr: c8004000, CPLD addr: c8002000, UART Addr: c8000000
CPLD-10 init: r1=0 ck1=ff sc1=0 i1=ff i2=ff i3=ff i4=ff s1=0 s2=0 s3=0 s4=0
FLASH disk driver initialized: VMA c8004000 size 4096kb blocks 64
Dentry hash table entries: 8192 (order 4, 64k)
Buffer cache hash table entries: 65536 (order 6, 256k)
Page cache hash table entries: 16384 (order 4, 64k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 65536 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.2
Serial driver version 4.27 with SHARE_IRQ enabled
ttyS01 at 0xc8000000 (irq = 2) is a ST16C654
ttyS02 at 0xc8000008 (irq = 2) is a ST16C654
ttyS03 at 0xc8000010 (irq = 2) is a ST16C654
ttyS04 at 0xc8000018 (irq = 2) is a ST16C654
ttyS05 at 0xc8000020 (irq = 2) is a ST16C654
ttyS06 at 0xc8000028 (irq = 2) is a ST16C654
ttyS07 at 0xc8000030 (irq = 2) is a ST16C654
ttyS08 at 0xc8000038 (irq = 2) is a ST16C654
ttyS09 at 0xc8000040 (irq = 2) is a ST16C654
ttyS10 at 0xc8000048 (irq = 2) is a ST16C654
ttyS11 at 0xc8000050 (irq = 2) is a ST16C654
ttyS12 at 0xc8000058 (irq = 2) is a ST16C654
ttyS13 at 0xc8000060 (irq = 2) is a ST16C654
ttyS14 at 0xc8000068 (irq = 2) is a ST16C654
ttyS15 at 0xc8000070 (irq = 2) is a ST16C654
ttyS16 at 0xc8000078 (irq = 2) is a ST16C654
ttyS17 at 0xc8000080 (irq = 2) is a ST16C654
ttyS18 at 0xc8000088 (irq = 2) is a ST16C654
ttyS19 at 0xc8000090 (irq = 2) is a ST16C654
ttyS20 at 0xc8000098 (irq = 2) is a ST16C654
ttyS21 at 0xc80000a0 (irq = 2) is a ST16C654
ttyS22 at 0xc80000a8 (irq = 2) is a?

Booting from Original Boot 1.9.7a (Jan/02/02)

Testing RAM … FULL TEST
This test takes a few seconds.
Press if you want to cancel it.
Memory detected: 65536 Kbytes
Test in progress: 65536 Kbytes OK
Testing Flash [Configuration] … OK
Testing Flash [Op Code] … NOK
Interface Cards Detected … OK
32-UART ports detected
Testing Ethernet … NOK
Testing Real Time Clock … OK
Testing Router Serial Number… NOK
Hardware Op Code invalid. Trying network boot.

Sending a tftp request.
Trying file : zvmppcdg.bin

WARNING! Network boot failure. System halted.

2

Recommend trying the steps outlined in the following article:

http://www.digi.com/support/kbaseresultdetl.jsp?id=20

If this fails, you should contact Digi Technical Support to make repair arrangements for this unit.

3

Are the Portserver CM 32 and CM 32 the same beasts?

I’m under the impression they’re seperate products, and the Portserver CM 32’s firmware capped out at version 1.3.4g. Someone correct me if I’m wrong?

4

Lo and behold, now I have the same problem as the original poster. I’d just like to confirm that the URL below is the correct zimage file for me to have been downloading:

http://ftp1.digi.com/support/firmware/zimage

And the fact that it reboots part of the way through the port recognition process… does that indicate hardware damage, or just something screwed up in the firmware?

Are there older firmwares available to try running?

Are there any boot parameters that can be passed to it, to cause the kernel to skip the serial port check (just to see if the rest of it is working)?

5

Yes, the PortServer CM and Digi CM are different products.

You are correct, the last firmware version for the PortServer CM (obsolete product) is 1.3.4g.

6

Ok, I just solved my own problem and that of the original poster.

The problem is that Digi’s instructions tell us to leave the watchdog timer active. Watchdog timers exist to reboot the device if it seems to be hung.

It’s likely that the tftp boot process takes long enough that the watchdog timer kicks in, reboots the portserver, and then puts us back to square one.

So… leave your watchdog timer Inactive, as opposed to Active, and try the tftp boot procedure again.