cc/td/doc/product/access/acs_serv/as5400
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

ROM Monitor

ROM Monitor

This appendix describes the Cisco AS5400 ROM monitor, the first software to run when the access server is powered-up or reset. The ROM monitor can help you isolate or rule out hardware problems encountered when installing your access server.

This appendix describes:

Entering the ROM Monitor Program

The ROM monitor diagnostics help initialize the processor hardware and boot the main operating system software. If you set the software configuration register (bits 3, 2, 1, and 0) to zero, you can start the access server in the standalone ROM monitor. An example of the ROM monitor prompt follows:

rommon 1 >
 

To enable the Break key, and to default to booting at the ROM monitor while running the system software, reset the configuration register to 0x0 by entering configuration mode, and enter the following configuration command:

confreg 0x0
 

The new configuration register value, 0x0, takes effect after the access server is rebooted with the reload command. If you set the configuration to 0x0, you will have to manually boot the system from the console each time you reload the access server.


TimeSaver Break (system interrupt) is always enabled for 60 seconds after rebooting the system, regardless of whether break is configured to be off by setting the configuration register. During the 60-second window, you can break to the ROM monitor prompt.

ROM Monitor Command Conventions

Following are ROM monitor command conventions:

Command Aliasing

The ROM monitor supports command aliasing modeled on the aliasing function built into the Korn shell. The alias command is used to set and view aliased names. This allows the user to alias command names to a letter or word. Aliasing is often used to shorten command names or automatically invoke command options.

Aliases are stored in NVRAM and remain intact across periods of no power. These are some of the set aliases:

b=boot
h=history
i=reset
r=repeat
k=stack
?=help

ROM Monitor Commands

At the ROM monitor prompt, enter ? or help at the rommon n > prompt to display a list of available commands and options, as follows:

rommon 12 > help
alias               set and display aliases command
boot                boot up an external process
break               set/show/clear the breakpoint
confreg             configuration register utility
cont                continue executing a downloaded image
context             display the context of a loaded image
cookie              display contents of cookie PROM in hex
dev                 list the device table
dir                 list files in file system
dis                 disassemble instruction stream
dnld                serial download a program module
dram                verify DRAM
frame               print out a selected stack frame
hardware_info       display hardware information
help                monitor builtin command help
history             monitor command history
meminfo             memory information (-spd dumps SDRAM cookie)
repeat              repeat a monitor command
reset               system reset
set                 show all monitor variables
show_spd            show all SPD data
sleep               millisecond sleep command
stack               produce a stack trace
sync                write monitor environment to NVRAM
sysret              print out info from last system return
unalias             unset an alias
unset               unset a monitor variable

Note   You can display additional details for a command by entering the command name with a -? option, which prints the command usage message.

The commands are listed and described in alphabetical order. Note that the ROM monitor commands are case sensitive.

For example:
    rommon 1 > alias
    r=repeat
    h=history
    ?=help
    b=boot
    ls=dir
     
    
boot [-xv] [devid] [imagename]

b--Boots the default system software from ROM.

b filename [host]--Boots using a network TFTP server. When a host is specified, either by name or IP address, the boot command will boot from that source.

b flash:--Boots the first file in Flash memory.

b device:--Boots the first file found in the Flash memory device. The Flash memory device specified can be either flash:, to boot the Cisco IOS software, or bootflash:, to boot the boot image in Flash memory.
b device:name--An extension of the above command, allows you to specify a particular filename in the Flash memory bank.
The configuration register resides in NVRAM. The configuration register is identical in operation to other Cisco access servers. Enter confreg for the menu-driven system, or enter the new value of the register in hexadecimal.
For example:
    rommon 2 > confreg
     
     
               Configuration Summary
       (Virtual Configuration Register:0x0)
    enabled are:
    break/abort has effect
    console baud:9600
    boot:the ROM Monitor
     
    do you wish to change the configuration? y/n  [n]: y
    enable  "diagnostic mode"? y/n  [n]: 
    enable  "use net in IP bcast address"? y/n  [n]: 
    enable  "load rom after netboot fails"? y/n  [n]: 
    enable  "use all zero broadcast"? y/n  [n]: 
    disable "break/abort has effect"? y/n  [n]: 
    enable  "ignore system config info"? y/n  [n]: 
    change console baud rate? y/n  [n]: y
    enter rate:0 = 9600,  1 = 4800,  2 = 1200,  3 = 2400
    4 = 19200, 5 = 38400, 6 = 57600, 7 = 115200  [0]: 
    change the boot characteristics? y/n  [n]: 
     
     
               Configuration Summary
       (Virtual Configuration Register:0x0)
    enabled are:
    break/abort has effect
    console baud:9600
    boot:the ROM Monitor
     
    do you wish to change the configuration? y/n  [n]: 
     
    
For example:
    reboot >
    monitor: command "launch" aborted due to user interrupt
    diagmon 7 > cont
     
    reboot>
     
    
For example:
    rommon 6 > context
    CPU Context:
    d0 - 0x00000028      a0 - 0x0ff00420
    d1 - 0x00000007      a1 - 0x0ff00000
    d2 - 0x00000007      a2 - 0x02004088
    d3 - 0x00000000      a3 - 0x020039e6
    d4 - 0x00000000      a4 - 0x02002a70
    d5 - 0x02003e8a      a5 - 0x02003f17
    d6 - 0x00000000      a6 - 0x02003938
    d7 - 0x00000001      a7 - 0x0200392c
    pc - 0x02004adc     vbr - 0x02000000
     
    
For example:
    rommon 1 > cookie
     
    cookie:
    00 01 01 31 03 15 03 20 00 14 33 01 30 11 4a 41 
    42 30 33 35 31 30 37 38 32 00 00 00 00 00 13 63 
    0c 1d 00 00 00 00 11 11 22 22 33 33 44 44 55 55 
    66 66 77 77 88 88 99 99 00 00 11 11 22 22 33 33 
    ff 00 30 96 f8 00 7a ff ff ff ff ff ff ff ff ff 
    ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
    ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
    ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 
     
    
For example:
    rommon 10 > dev
    Devices in device table:
            id  name
        flash: flash                      
    bootflash: boot flash 
    
For example:
    rommon 11 > dir flash:
    File size           Checksum   File name
       9474676 bytes (0x909274)   0x54322421    c5400-js-mz.Jan6
    
For example:
    rommon 6 > frame 2
    Frame 02: FP = 0x02003960    RA = 0x020050ee
    at 0x02003968 (fp + 0x08) = 0x02004f8d
    at 0x0200396c (fp + 0x0c) = 0x0200f390
    at 0x02003970 (fp + 0x10) = 0x02006afc
    at 0x02003974 (fp + 0x14) = 0xc0a82983
    at 0x02003978 (fp + 0x18) = 0x02003a7e
    at 0x0200397c (fp + 0x1c) = 0x02002630
    at 0x02003980 (fp + 0x20) = 0x00000000
    at 0x02003984 (fp + 0x24) = 0x02000000
    at 0x02003988 (fp + 0x28) = 0x0200c4a4
    at 0x0200398c (fp + 0x2c) = 0x0200f448
     
    
For example:
    rommon 11 > help
    alias               set and display aliases command
    boot                boot up an external process
    break               set/show/clear the breakpoint
    confreg             configuration register utility
    cont                continue executing a downloaded image
    context             display the context of a loaded image
    cookie              display contents of cookie PROM in hex
    dev                 list the device table
    dir                 list files in file system
    dis                 disassemble instruction stream
    dnld                serial download a program module
    dram                verify DRAM
    frame               print out a selected stack frame
    hardware_info       display hardware information
    help                monitor builtin command help
    history             monitor command history
    meminfo             memory information (-spd dumps SDRAM cookie)
    repeat              repeat a monitor command
    reset               system reset
    set                 show all monitor variables
    show_spd            show all SPD data
    sleep               millisecond sleep command
    stack               produce a stack trace
    sync                write monitor environment to NVRAM
    sysret              print out info from last system return
    unalias             unset an alias
    unset               unset a monitor variable
     
    
For example:
    rommon 9 > meminfo
     
    Main memory size:128 MB. Packet memory size:64 MB
    Available main memory starts at 0xa000e000, size 0x7ff2000
    Packet memory starts at 0xa8000000
    NVRAM size:0x80000
    Main memory control register:0xbe9022f4
    Shared memory control register:0x00000202
    
For example:
    rommon 5 > stack 8
    Stack trace:
    PC = 0x02004adc
    Frame 00: FP = 0x02003938    RA = 0x02005f2a
    Frame 01: FP = 0x02003948    RA = 0x02005df0
    Frame 02: FP = 0x02003960    RA = 0x020050ee
    Frame 03: FP = 0x02003994    RA = 0x02004034
    Frame 04: FP = 0x02003b00    RA = 0x00012ca6
     
    
For example:
    rommon 8 > sysret
    System Return Info:
    count: 19,  reason: user break
    pc:0x60043754,  error address: 0x0
    Stack Trace:
    FP: 0x80007e78, PC: 0x60043754
    FP: 0x80007ed8, PC: 0x6001540c
    FP: 0x80007ef8, PC: 0x600087f0
    FP: 0x80007f18, PC: 0x80008734
     
    

hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 15 10:43:02 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.