7.7.8.95. GEL_SymbolAddOffset()ΒΆ
Loads additional symbol information with offset relocation information.
Syntax
GEL_SymbolAddOffset( "fileName", code_offset, data_offset, ["cpuName"], ["boardName"] );
Parameters
fileName: names the symbol file containing the symbol information. The fileName must be enclosed in quotation marks. The symbol file can be a standard COFF or ELF output file (*.out) or a specific symbol file obtained during the build process.
code_offset: specifies the offset by which the code sections are relocated in memory, relative to their original addresses.
data_offset: specifies the offset by which the data sections are relocated in memory, relative to their original addresses.
cpuName (optional): names the CPU on which to load the symbolic information (useful in a multiprocessor environment). The cpuName must be enclosed in quotation marks.
boardName (optional): names the board on which to load the symbolic information. If not specified, uses the board name of the processor on which this GEL function is executed. The boardName must be enclosed in quotation marks.
Description
Symbol information can be appended to the existing symbol table. This function loads the symbol information from the specified symbol file. It does not modify target memory or set the program entry point.
The relocation information is specified using an address offset that identifies an offset relative to locations the symbol file specifies the sections are to be loaded in memory.
GEL_SymbolAddOffset differs from GEL_SymbolAddRel in that the relocation information is specified using an address offset relative to the usual locations at which the sections would be loaded, instead of an absolute address.
GEL_SymbolAddOffset differs from GEL_SymbolLoadOffset in that it does not clear the contents of the existing symbol table before loading the new symbols. Symbols are loaded with the code and data address offsets specified by the relocation information.
If the file is not in the current directory, provide a full path name within the string. A double backslash escape sequence is required to ensure that you get a backslash into the filename entry.
The cpuName and boardName must match the Processor Name and Board Name as configured in the multiprocessor setup. In a single processor system, you do not need to fill these fields.
Synchronous
Synchronous from GEL: Yes
Completely synchronous: No
Example
GEL_SymbolAddOffset("c:\\mydir\\myfile.out", 16, 64, "Cortex_M4_0",
"Texas Instruments XDS110 USB Debug Probe_0");
Related Topics