LOAD

The LOAD command instructs the µVision debugger to load an object file. You can load the object file of the current project when starting the µVision debugger by enabling Options for Target – Debug - Load Application at Startup.

µVision analyzes the contents of the file to determine the file type (if the file type cannot be determined, then an error message is displayed). The following file types are supported:

• Absolute Object File or ELF/DWARF File: is produced by the linker/locator, and contains complete symbolic debug information, type information, and line numbers when translated with debug information. When no further options are specified, the debugger performs a target reset and provides memory map settings.
• Intel HEX File: is produced by Object-to-Hex-Converter programs, and contains no symbolic debug information, no type information, and no line number information. Program testing is supported only at CPU instruction level. Source-level and symbolic debugging are not supported. No target reset is performed when HEX files are loaded. Therefore, it might be required to issue an explicit RESET command.

The LOAD command has several options that depend on the target in use:

• INCREMENTAL - adds the debugging information to the existing symbol table. This allows multi-application debugging.
• NOCODE - loads only the symbolic information and ignores code records. NOCODE prevents the existing program code from being overwritten. This option requires to previously load a CPU driver for a monitor (MON51, MON251, or MON166).
• NORESET (only available on some targets) prevents the generation of a RESET signal after loading the program. For targets where this option does not exist, use the INCREMENTAL option instead, which effectively performs the same operation.

Examples

LOAD C:\PROJECTS\C51\EXAMPLES\MEASURE\MEASURE

This command line loads measure from the directory c:\projects\c51\examples\measure. This directory is also searched by µVision for source files.

LOAD MYPROG.HEX

This command line loads myprog.hex.

Support for Key Sequences

Key sequences can be used in the LOAD command. This enhancement allows using a generic Debugger initialization file across multiple projects, for example: in a Multi-Project Workspace, the name of the linker output file can be specified with %L.

Examples

LOAD %L INCREMENTAL

This command line loads the linker output file of the current project for debugging.

Note

• When a file name contains spaces, it must be enclosed in quotes ("). In this case, the parser applies the rules for C string literals. Then, it is required to use a double backslash (\\) instead of a single backslash (\) character.

  Example:

  LOAD "C:\\path with blanks\\filename.hex"