|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-CC04A14B-A839-5613-820D-F1E65EB2DF7F" xml:lang="en"><title>MAKSYM/MAKSYMROFS</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
13 <p>MAKSYM/MAKSYMROFS tool is used to create a symbol file, which lists |
|
14 the addresses of every global and exported function in the ROM. It |
|
15 reads a log file to generate the symbol file. The log file contains |
|
16 information about the contents of the ROM or ROFS image. </p> |
|
17 <p>MAKSYM reads the log file which is created by ROMBUILD when building |
|
18 a ROM image. MAKSYMROFS reads the log file which is created by ROFSBUILD |
|
19 when building a ROFS image. The command syntax for MAKSYM and MAKSYMROFS |
|
20 is the same. </p> |
|
21 <section id="GUID-4ABD6DC7-7B5F-5E81-81F6-408F02FB8EA2"><title>MAKSYM |
|
22 command syntax</title> <codeblock id="GUID-80510A94-15C8-55C3-99D9-5C82DEBF9269" xml:space="preserve">MAKSYM <logfile> [<outfile>]</codeblock> <table id="GUID-977669AC-2133-5573-9287-6B3741A86C8C"> |
|
23 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/> |
|
24 <tbody> |
|
25 <row> |
|
26 <entry><p> <codeph><logfile></codeph> </p> </entry> |
|
27 <entry><p>This is the name of the log file generated by the <xref href="GUID-003D2C5B-09DC-5BD1-AF45-A0FCB56F567B.dita">ROMBUILD</xref> tool. </p> </entry> |
|
28 </row> |
|
29 <row> |
|
30 <entry><p> <codeph><outfile></codeph> </p> </entry> |
|
31 <entry><p>This is the name for the MAKSYM output file. If not specified, |
|
32 it defaults to <filepath><ROMimagename>.symbol</filepath>. </p> </entry> |
|
33 </row> |
|
34 </tbody> |
|
35 </tgroup> |
|
36 </table> <p>By default, ROMBUILD produces a log file called <filepath>ROMBUILD.LOG</filepath>, which is passed to MAKSYM tool in the following |
|
37 way: </p> <p><userinput>MAKSYM rombuild.log</userinput> </p> <p>This |
|
38 will generate an output text file (Symbolic information file) called <filepath><romimagename>.symbol</filepath>. </p> <p>The file contains all |
|
39 the global variables along with their address and length. For example, |
|
40 the start of <filepath>EKERN.EXE</filepath> looks like this: </p> <codeblock id="GUID-74AEE387-D6D3-51C6-8658-78B2A2DA0FF4" xml:space="preserve">From \Epoc32\Release\Misa\UREL\ekern.exe |
|
41 |
|
42 50003040 0094 _E32Startup |
|
43 500030d4 002c ImpDma::Init1(void) |
|
44 50003100 0004 ImpDma::Init3(void) |
|
45 50003104 0008 ImpDma::MaxBlockSize(void) |
|
46 </codeblock> <p>In this example, the function <codeph>ImpDma::Init1()</codeph> starts at address <codeph>0x500030d4</codeph> and is <codeph>0x2c</codeph> bytes long. </p> <p> <b>Notes</b>: </p> <ul> |
|
47 <li id="GUID-BD48C930-4051-5276-AB78-8CC5BADD65ED"><p>If you are distributing |
|
48 ROM images for testing, it is also useful to supply the symbolic information |
|
49 file for that image. </p> </li> |
|
50 <li id="GUID-2B694850-0513-52B8-B477-78A08F4B83AE"><p>If you re-build |
|
51 the ROM image you must also rebuild the symbolic information file |
|
52 using MAKSYM. </p> </li> |
|
53 </ul> </section> |
|
54 </conbody></concept> |