Subject: 34. What can I do if my new software upload gets screwed up?
Sometimes the documented method of upgrading software on an Ascend unit
(Xmodem upload over the console port) can get hosed up, either by a
power loss, user error, bad cable, crappy workstation communications,
or other acts of god and building maintenance. For those occasions,
we have some advice from an undisclosed source inside Ascend:
> Usually, when you load a bad binary into a Pipeline, it will
> recover by booting into the downloader, which displays "CKCK" on
> the console port. Occasionally, however, that doesn't happen.
> To resuscitate a Pipeline that has been loaded with the wrong code
> and can't recover, you'll need to short a jumper that causes the
> box to power up into the boot rom debug monitor, type the 'DF'
> command, then download good code through the console port.
>
> Platform location (console speed)
>
> SOS BRI P20 (38400)
> SOS T1 P8 (38400)
> MAX-HP P3 (57600)
> P50-4WS56 C43 (57600)
> P50-BRI (revB) P9 (57600)
>
> Platform-specific notes:
>
> PIPE50
>
> On the original Pipe 50, there are no jumpers.
>
> MAX
>
> On the MAX E1 and T1, the Boot ROM doesn't talk to the console port.
> If your Max requires resuscitation like this, you'll need to contact
> Ascend Customer Service.
Go to Previous Question
Go to Next Question
Go to Table of Contents