4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">

     4   <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">

     5 <title>Symbol files,  Map files, and Image files</title>

     5   <title>Symbol files, Map files, OST dictionary files, and Image files</title>

     6 <link href="../../book.css" type="text/css" rel="stylesheet">

     6   <link href="../../book.css" type="text/css" rel="stylesheet">

    10 <h2>Symbol files, Map files, and Image files</h2>

    12 <p>In the Crash Analyser Import Wizard, you have to define either the symbol

    11 <p>In the Crash Analyser Import Wizard, you have to define either the symbol files or map files or both of them. Defining image files is optional.</p>

    13 files or map files or both of them. Defining image files is optional.</p>

    14 <p>When you create an image, symbol files are generated automatically. Symbol files contain the binary structure of an image, which is needed for producing an analysis file. You can find a symbol file for example from <i>\epoc32\rombuild\&lt;device>\core.</i></p>

    16 

    15 <p>If you have defined symbol files, you can define also map files and image files.</p><h4>Map files</h4><p>If you need to define map files, you can select the <b>Map files folder</b> option to define the location of map files, or you can select <b>MapFiles.zip</b> option if you want to provide a ZIP file containing the map files. If you choose the <b>SDK Map files folder</b> option, the Crash Analyser Import Wizard checks which SDKs you have installed in Carbide.c++, and lists the directories of each SDK which contain map files. Choose the directory you want. If you do not want to define any map files, then select the <b>No map files</b> option.</p>

    17 <p>When you create an image, symbol files are generated automatically. Symbol

    18 files contain the binary structure of an image, which is needed for producing

    19 an analysis file. You can find a symbol file for example from

    20 <i>\epoc32\rombuild\&lt;device&gt;\core.</i></p>

    21 

    22 <p>If you have defined symbol files, you can define also map files and image

    23 files.</p>

    24 

    25 <h4>Map files</h4>

    26 

    27 <p>If you need to define map files, you can select the <b>Map files folder</b>

    28 option to define the location of map files, or you can select

    29 <b>MapFiles.zip</b> option if you want to provide a ZIP file containing the map

    30 files. If you choose the <b>SDK Map files folder</b> option, the Crash Analyser

    31 Import Wizard checks which SDKs you have installed in Carbide.c++, and lists

    32 the directories of each SDK which contain map files. Choose the directory you

    33 want. If you do not want to define any map files, then select the <b>No map

    34 files</b> option.</p>

    18 <p>The following image file types can be selected in the Import Wizard. You can also select more that one type at the time.</p>

    37 

    38 <p>The following image file types can be selected in the Import Wizard. You can

    39 also select more that one type at the time.</p>

    20 <li><b>R&amp;D image file</b> (.fpsx,), is a flashable Nokia proprietary image file containing the software for the phone.</li>

    41   <li><b>R&amp;D image file</b> (.fpsx,), is a flashable Nokia proprietary

    21 <li><b>Core image file</b> (.Cxx), is a language independent flashable phone software file.</li>

    42     image file containing the software for the phone.</li>

    22 <li><b>Variant image file</b> (.Vxx.), is an image file which contains the language, country or operator variant specific phone software.</li>

    43   <li><b>Core image file</b> (.Cxx), is a language independent flashable phone

    23 <li><b>(.img) image file</b> is a Symbian OS flashable image file.</li>

    44     software file.</li>

    45   <li><b>Variant image file</b> (.Vxx.), is an image file which contains the

    46     language, country or operator variant specific phone software.</li>

    47   <li><b>(.img) image file</b> is a Symbian OS flashable image file.</li>

    25 <p>All the files (.fpsx, .Cxx, .Vxx, .img) refer to flash image files. Usually only one / few of them are needed, the extension just differs in different environments. The files are the ones that are flashed to phone e.g. with Phoenix tool. The image files are not absolutely neccessary but they enable the analyser to do more precise decoding than just symbol files.</p>

    49 

    26 <p>Different environments put these files to different locations, common locations under SDK root are for example \epoc32\rombuild and \Rom_images_2009. If you have not flashed your development phone yourself, it may be difficult to find the original flash images anywhere. Most of flash files available can be found from Notes DCT5 database, but the decoding files must match the flash image in phone exactly. Only reliable way is to flash a certain image first and use flash image for decoding only for crashes from that image.</p>

    50 <p>All the files (.fpsx, .Cxx, .Vxx, .img) refer to flash image files. Usually

    51 only one / few of them are needed, the extension just differs in different

    52 environments. The files are the ones that are flashed to phone e.g. with

    53 Phoenix tool. The image files are not absolutely necessary but they enable the

    54 analyser to do more precise decoding than just symbol files.</p>

    55 

    56 <p>Different environments put these files to different locations, common

    57 locations under SDK root are for example \epoc32\rombuild and \Rom_images_2009.

    58 If you have not flashed your development phone yourself, it may be difficult to

    59 find the original flash images anywhere. Most of flash files available can be

    60 found from Notes DCT5 database, but the decoding files must match the flash

    61 image in phone exactly. Only reliable way is to flash a certain image first and

    62 use flash image for decoding only for crashes from that image.</p>

    63 

    64 <h4>OST dictionary files</h4>

    65 

    66 <p>OST dictionaries are XML files generated by TraceCompiler. The files are

    67 used to translate the binary trace to human-readable format. The files are

    68 located in your environment under <em>\epoc32\ost_dictionaries</em>.</p>

    69 

    29 <li><a href="../concepts/how_to_analyse_crash.htm">How to analyse a crash </a></li>

    72   <li><a href="../concepts/how_to_analyse_crash.htm">How to analyse a crash

    73   </a></li>

    34 <li><a href="../tasks/import_crash_files.htm">Importing crash files</a></li>

    78   <li><a href="../tasks/import_crash_files.htm">Importing crash files</a></li>

    37 <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 

    81 <div id="footer">

    38 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div>

    82 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights

    83 reserved. License: <a

    84 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div>