ROMmon--> Can't send the Break Signal--> USB Adapter?

[Vasconcelos]

I'll rate every post that helps

So, I've tryed the methods below to send the Break Signal to the Router in order to enter ROMmon and they aren't working

Putty

    - CTRL+ Pause (Only the Pause key is available)

    - Right-Click> Special Command> Break

    - Virtual Keyboard--> CTRL+ Pause (Only the Pause key is available)

Tried with SecureCRT and Tera Term also

I'm using a USB Adapter on the Console Cable (DB9)

Does someone know what might be the problem? 

[Leo Laohoo]

What kind of router?

[Vasconcelos]

Cisco 2611xm

[Diana Karolina Rojas]

Hello!

Did you try this?

CTRL + SHIFT + 6 + X

Enter

Please do not forget to rate useful post.

Best Regards,

[Vasconcelos]

Does anyone know?

[Ben Walters]

This might be related to the configuration register of the device, some of them make the router ignore break.

I am guessing you aren't able to get into the router which is why you want to boot to ROMmon in the first place. If you are able to configure the router you may want to check the register and then change it.

Here is more info:

https://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/50421-config-register-use.html

[Makkakaz]

How to Simulate a Break Key Sequence

Break key sequence simulation is useful if your terminal emulator does not support the break key, or if a bug does not allow your terminal emulator to send the correct signal.

Note: The hyperterminal under Windows NT had this behavior in the past.

Complete these steps to simulate a break key sequence:

1. Connect to the router with these terminal settings:

   1200 baud rate

   No parity

   8 data bits

   1 stop bit

   No flow control

   You no longer see any output on your screen, and this is normal.

2. Power cycle (switch off and then on) the router and press the SPACEBAR for 10-15 seconds in order to generate a signal similar to the break sequence.

3. Disconnect your terminal, and reconnect with a 9600 baud rate. You enter the ROM Monitor mode.

If all these methods fail to properly send a break, retry the procedures from a different terminal or PC platform.

More detailed info you could find here

[i-luv]

It might be slightly outdated answer and most likely addresses the issue from different angle, but imho it's better late than not at all.

I have struggled with the similar issue of sending break command, till I got over Jeremy Cioara's  hint on usb to serial adapters.

There he described that the usb to serial converter Has to be constructed on a [Prolific] chipset(prolific usb-to-serial converter) as other chipsets(i.e. in my case CH340) most likely Do Not have break functionality.