2.10.2. Running the Boot Monitor

To run Boot Monitor and have it display a prompt to a terminal connected to UART0, set switch S6-1 to OFF and reset the system. Standard input and output functions use UART0 by default. The default setting for UART0 is 38400 baud, 8 data bits, no parity, 1 stop bit. There is no hardware or software flow control. Use these values to configure a terminal application on your PC to communicate with the Boot Monitor.

Note

If the Boot Monitor has been accidently deleted from flash memory or a different version of the monitor is required for a different Core Tile, see Rebuilding the Boot Monitor or platform library for information on loading the monitor.

Boot Monitor commands

The command interpreter accepts user commands from the debugger console window or an attached terminal and carries out actions to complete the commands.

Note

Commands are accepted in uppercase or lowercase. The Boot Monitor accepts abbreviations of commands if the meaning is not ambiguous. For example, for QUIT, you can type QUIT, QUI, QU, Q, quit, qui, qu, or q.

Optional parameters for commands are indicated by []. For example HELP [command] indicates that the HELP command can take an optional parameter to specify that the help text for command is displayed instead of general help text.

Note

The commands available depend on the Core Tile fitted. For example, the ARM7TDMI Core Tile does not contain a cache and the ENABLE CACHES and DISABLE CACHES commands are not present.

Additional Boot Monitor commands might be available depending on the Core Tile fitted. Type HELP at the Boot Monitor prompt to display a full list of commands that are available for the specific baseboard and Core Tile configuration.

Table 2.7 lists the commands for the Boot Monitor.

Table 2.7. Boot Monitor commands

CommandAction
@ script_fileRuns a script file.
ALIAS alias commandsCreate an alias command alias for the string of commands contained in commands.
CLEAR BOOTSCRIPTClear the current boot script. The Boot Monitor will prompt for input on reset even if the S6-1 is set to ON to indicate that a boot script should be run.
CONFIGUREEnter Configure subsystem. Commands listed in Table 2.8 can now be executed.
CONVERT BINARY binary_file LOAD_ADDRESS address [ENTRY_POINT address]Provides information to the system that is required by the RUN command in order to execute a binary file. A new file with name binary_file is produced, but with an .exe file extension.
DEBUGEnter the debug subsystem. Commands listed in Table 2.9 can now be executed.
DISABLE CACHESDisable both the I and D caches.
DISPLAY BOOTSCRIPTDisplay the current boot script.
ECHO textEcho text to the current output device.
ENABLE CACHESEnable both the I and D caches.
EXITExit the Boot Monitor. The processor is held in a tight loop until it is interrupted by a JTAG debugger.
FLASHEnter the flash file system for the NOR flash on the baseboard. See Table 2.10 for flash commands.
HELPList the Boot Monitor commands.
QUITAlias for EXIT. Exit the Boot Monitor.

Table 2.8 lists the commands for the Configure subsystem.

Table 2.8. Boot Monitor Configure commands

CommandAction
DISPLAY CLOCKSDisplay system clocks.
DISPLAY DATEDisplay date.
DISPLAY HARDWAREDisplay hardware information (for example, the FPGA revisions).
DISPLAY TIMEDisplay time.
EXITExit the configure commands and return to executing standard Boot Monitor commands.
HELP [command]List the configure commands. If a command is specified, help for that command is output.
QUITAlias for EXIT. Exit the Configure commands and return to standard Boot Monitor commands.
SET CLOCK 0 frequency

Set frequency for clock 0.

Caution

Clock 0 is the reference for the test chip present on the attached Core Tile. Clock 0 can only be directly modified if the PLL on the test chip is bypassed. See the application note for your Core Tile for more information on setting the system clock.

SET CLOCK 1 frequency

Set frequency for clock 1.

Note

The Boot Monitor does not set any of the clocks on startup. The clock values are determined by the default values in the FPGA image and the settings of switch S8 (see Setting the configuration switches).

SET CLOCK 2 frequencySet frequency for clock 2.
SET CLOCK 3 frequencySet frequency for clock 3.
SET CLOCK 4 frequencySet frequency for clock 4.
SET DATE dd/mm/yySet date. The date can also be entered as dd-mm-yy
SET TIME hh:mm:ssSet time. The time can also be entered as hh-mm-ss

Table 2.9 lists the commands for the Debug subsystem.

Table 2.9. Boot Monitor Debug commands

CommandAction
DEPOSIT address value [size]Load memory specified by address with value. The size parameter is optional. If used, it can be BYTE, HALFWORD, or WORD. The default is WORD.
DISABLE MESSAGESDisable debug messages
ENABLE MESSAGESEnable debug messages
EXAMINE addressExamine memory at address
EXITExit the debug commands and return to executing standard Boot Monitor commands.
GO addressRun the code starting at address.
HELP [command]

List the debug commands.

Entering HELP followed by a command displays help for that command.

QUITAlias for EXIT. Exit the Debug commands and return to standard Boot Monitor commands.
MODIFY address value mask [size]Performs read-modify-write at memory specified by address. The current value at the location is ORed with the result of ANDing value and mask. The size parameter is optional. If used, it can be BYTE, HALFWORD, or WORD. The default is WORD.
START TIMERStart a timer.
STOP TIMERStop the timer started with the START TIMER command and display the elapsed time.

Table 2.10 lists the commands for the NOR Flash subsystem.

Table 2.10. Boot Monitor NOR flash commands

CommandAction

DISPLAY IMAGE name

Displays details of image name.

ERASE IMAGE name

Erase an image or binary file from flash.

ERASE RANGE start [end]

Erase an area of NOR flash from the start address to the end address.

Note

It is only possible to erase entire blocks of flash. Therefore the entire block of flash that contains start, the block that contains end and all intervening blocks are erased. This might mean that data before start or after end will be erased if they are not on block boundaries. If the optional end parameter is not specified, only the single block of flash that contains start is erased.

Caution

This command can erase the Boot Monitor image if it is stored in NOR flash. See Loading Boot Monitor into NOR flash.

EXITExit the flash commands and return to executing standard Boot Monitor commands.
HELP

List the flash commands.

Entering HELP followed by a command displays help for that command.

LIST AREASList areas in flash. An area is one or more contiguous blocks that have the same size and use the same programming algorithm.
LIST IMAGESList images in flash.
LOAD nameLoad the image image_name into memory.
QUITAlias for EXIT. Exit the NOR flash commands and return to standard Boot Monitor commands.
RESERVE SPACE address sizeReserve space in NOR flash. This space will not be used by the Boot Monitor. address is the start of the area and size is the size of the reserved area.
RUN nameLoad the image name from flash and run it.
UNRESERVE SPACE addressFree the space starting at address in NOR flash. This space can be used by the Boot Monitor.
WRITE BINARY file [NAME new_name] [FLASH_ADDRESS address] [LOAD_ADDRESS address] [ENTRY_POINT address]

Write a binary file to flash. By default, the image is identified by its file name. Use NAME new_name to specify a name instead of using the default name.

Use FLASH_ADDRESS address to specify where in flash the image is to be located. The optional LOAD_ADDRESS and ENTRY_POINT arguments enable you to specify the load address and the entry point.

If an entry point is not specified, the load address is used as the entry point.

Note

Remote file access requires semihosting. Use a debugger connection to provide semihosting.

WRITE IMAGE file [NAME new_name] [FLASH_ADDRESS address]

Write an ELF image file to flash. By default, the image is identified by its file name. For example, t:\images\Boot_Monitor_EB.axf is identified as boot_monitor. Use NAME new_name to specify a name instead of using the default name.

Use FLASH_ADDRESS address to specify where in flash the image is to be located. If the image is linked to run from flash, the link address is used and address is ignored.

Note

Remote file access requires semihosting. Use a debugger connection to provide semihosting.


Copyright © 2005-2011 ARM Limited. All rights reserved.ARM DUI 0411D
Non-Confidential