Catalyst 4224 Console Error

[eah18]

I went to upgrade the IOS on a Catalyst 4224 using xmodem. I commonly use this procedure instead of a tftp (mostly due to limitations on flash size) and in fact did so earlier today on a 2621 with no trouble whatsoever. My procedure is to power on the box, drop to ROM Monitor, change the console baud rate to 115200, and then type reset. Then I disconnect from Hyperterminal and change my own baud rate to 115200.

Normally when I then hit <ENTER> all is well - the box is booting. I do a hard reset, break into ROMMON again, and start the xmodem transfer.

On the 4224, I just get garbage on the screen after changing the baud rate. My Hyperterm setting are 115200, I have verified again again in the backscroll that I did indeed change ther CAT4224's baud rate to 115200, and yet here I am, with pure garbage on my console. Just for grins I did try all the other baud rates, and none of them worked.

FYI I saw this issue posted on another Cisco forum on another site, but there was no response. Does anyone here have any suggestions? I'd be happy to open up the box if there are any reset jumpers in there. I don't care about the configuration (in fact I want to wipe it clean) so if there is any way I can wipe out the box completely to factory defaults, that would be fabulous.

Thank you so much!

--EMILY

 

[RookThis]

Sounds like there is still a mis-match in speed, but try write erase, then reload without saving the config.

 

[eah18]

I appreciate the input, but since I can't get to the box at all, I can't do any configuration clearing. The box is already "wiped" to factory defaults, so there's no IP for me to telnet to if I hooked it into the network; console is my only option.

Seriously, I tried every speed through Hyperterm. I get a few lines of "CCCC" when it is loading the image - it's as if the SOME of the info is getting through at the 115200 speed.

Anyway, what I really need is to know if there's a hardware jumper inside the box to reset the config register to default (or to 0x2142). If anyone can help, I appreciate it!