Home |
RTTarget-32 Programming Manual Running Win32 Programs without Win32 The .LOC File Running a Program on the Target Compiling and Linking with On Time RTOS-32 |
The .LOC FileApart from the .RTB and/or .HEX and .BIN files, RTLoc generates a file with extension .LOC. The .LOC file has a purpose similar to that of a MAP file produced by a linker. It contains detailed information about how the program is mapped to the target hardware. The .LOC file is divided into several reports. Each report can be enabled or disabled with the -Rx options (see section RTLoc Options). The Configuration Report contains a copy of all configuration files lines processed with blank, comment, and inactive lines removed. The EXE File Report contains information about the application's PE file(s). In particular, parts of the PE file header and a list of all sections found is included. If the Dynamic Link Report is enabled, this report also lists all exported and imported functions. RTLoc produces a separate EXE File Report for the main program and each DLL of the application. The Fixup Table Report lists all fixups processed by RTLoc. For each fixup, its location in the PE file's address space and in the target image's address space, the original value, and the new value are given. This report is disabled by default, because it can become rather long. It is usually required for trouble-shooting only. The Dynamic Link Report shows how RTLoc has matched DLL imports to DLL exports. For each DLL import, the importing module, the import's module and function name, the matched exporting module and function name, and the address of the exported function are given. In addition, this report lists all exported functions which are never referenced. However, these unreferenced functions could still be required at run-time if they are called locally or are accessed through functions LoadLibrary/GetProcAddress. This report is disabled by default. However, whenever any Link commands are changed or added, it is strongly recommended to enable the Dynamic Link Report at least temporarily to verify that the linkage is correct. The Compression Report lists all program entities which have been compressed. This includes the entities' names, full size, compressed size, ratio of compressed to full size in percent, and the time required to compress and decompress the data. The times are given in milliseconds. The times for decompressing the data are measured on the host when RTLoc verifies that the compressed data indeed decompresses to its original. The time required on the target will depend on the processing speed of the target. The numbers in the Compression Report are supplied to allow estimates of how long the target will need to initialize. The Relocation Report is probably the most interesting report. It contains a list of all regions and program entities with their addresses, sizes, images' sizes, and effective access privilege levels. In this report, you can see how your program has been mapped onto the target. For regions, the Image column contains the size of the region which is actually being used. Discardable entities are marked with an asterisk ('*') character in front of their respective names. The Page Table Detailed Report lists all pages of memory with their respective linear and physical addresses and access rights. Since this report can be rather long, it is disabled by default. The Page Table Summary Report shows the number of pages with identical properties (e.g., pages with the same access rights, etc.). If boot code has been included, the Boot Code Configuration Report lists all configuration options and parameters available for the boot code. The Application Image File Report includes information about the binary file produced by RTLoc. The application header is shown followed by a list of program entities and modules with their respective attributes. If RTLoc produces any error, warning, or information messages, they are listed in order of their occurrence in the Message Report. Please be sure to read this section carefully and understand all warnings (if any). A list of all possible messages is given in RTLoc Error Messages. If any errors or fatal errors are encountered, no .RTB, .HEX, or .BIN file is created.
|