4   <meta http-equiv="Content-Type"

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

     5  content="text/html; charset=iso-8859-1">

    11 <p>After capturing run-time information from your application on the

    11 

    12 target device, saving the profiler data file, and transfering the file

    12 <p>After capturing run-time information from your application on the target

    13 to your PC, you must then import the profiler data (.dat) file.

    13 device, saving the profiler data file, and transferring the file to your PC,

    14 Importing the data file converts the file into a format that can be

    14 you must then import the profiler data (.dat) file. Importing the data file

    15 displayed by the analyzer (a .NPI file).</p>

    15 converts the file into a format that can be displayed by the analyzer (a .NPI

    16 <p class="note"><strong>NOTE</strong> If a large .dat file is imported, the graph and table response time will slow down   until the  large NPI file is saved. Saving the NPI file will be performed in the background and  cannot be canceled.</p>

    16 file).</p>

    17 <p>Importing a profiler data file will vary depending on if your

    17 

    18 application was built by Carbide.c++ or is a standalone application. To

    18 <p class="note"><strong>NOTE</strong> If a large .dat file is imported, the

    19 find the binaries in your application, the importer will need the *.pkg

    19 graph and table response time will slow down until the large NPI file is saved.

    20 file created when your application was built, or you will need to list

    20 Saving the NPI file will be performed in the background and cannot be

    21 all application binaries. If you wish to analyze applications that

    21 canceled.</p>

    22 execute at a static address, you will need the ROM image .symbol file

    22 

    23 that represents your phone. For dynamically loaded binaries stored in a

    23 <p>Importing a profiler data file will vary depending on if your application

    24 phone’s ROFS or ROM, a .oby file can be used to describe and list

    24 was built by Carbide.c++ or is a standalone application. To find the binaries

    25 binaries.</p>

    25 in your application, the importer will need the *.pkg file created when your

    26 <p>Unless your application executes from a fixed address in phone

    26 application was built, or you will need to list all application binaries. If

    27 memory (e.g., is part of the flashed phone image), enable dynamic

    27 you wish to analyze applications that execute at a static address, you will

    28 binary support in the Profiler application when capturing your

    28 need the ROM image .symbol file that represents your phone. For dynamically

    29 application data in a profiler data file.</p>

    29 loaded binaries stored in a phone’s ROFS or ROM, a .oby file can be used

    30 to describe and list binaries.</p>

    31 

    32 <p>Unless your application executes from a fixed address in phone memory (e.g.,

    33 is part of the flashed phone image), enable dynamic binary support in the

    34 Profiler application when capturing your application data in a profiler data

    35 file.</p>

    36 

    34   <li><a name="Select_Performance_Investigator_Data"></a>Select

    42   <li><a name="Select_Performance_Investigator_Data"></a>Select Performance

    35 Performance Investigator Data</li>

    43     Investigator Data</li>

    36   <p>Select <strong>File &gt; Import...</strong> from Carbide.c++ to

    44 

    37 display Import dialog box (Figure 1), and select Performance

    45   <p>Select <strong>File &gt; Import...</strong> from Carbide.c++ to display

    38 Investigator Data and click <strong>Next</strong>.</p>

    46   Import dialog box (Figure 1), and select Performance Investigator Data and

    39   <p align="center"><img src="images/importdatfile_step1.png"

    47   click <strong>Next</strong>.</p>

    40  width="470" height="550"></p>

    48 

    49   <p align="center"><img src="images/importdatfile_step1.png"></p>

    50 

    42   <li><a name="Select_Profiler_Data_File"></a>Select Profiler Data File</li>

    52   <li><a name="Select_Profiler_Data_File"

    43   <p>Click <strong>Profiler Sample File...</strong>   and select the .dat file you transferred to your PC. The

    53     id="Select_Profiler_Data_File"></a>Select Profiler Data File(s) 

    44 .dat file will be converted to a format displayable by the Carbide.c++

    54     <p>Select .dat file(s) to the <strong>From File System</strong> list by

    45 analyzer and assigned the .npi extension (Figure 2). Click <strong>Next</strong>

    55     selecting either</p>

    46 to continue.</p>

    56     <ul>

    47   <p align="center"><img src="images/CB_import_step2.PNG" width="541"

    57       <li><strong>Add File</strong> and browsing to the file, or</li>

    48  height="385"></p>

    58       <li><strong>Add Directory</strong> and browsing to the directory you want

    49   <p align="center" class="figure">Figure 2. Select Profiler Data File</p>

    59         to import files from.</li>

    50   <li><a name="Select_Known_Available_Information"></a>Select Known Available information </li>

    60       <li>The .dat file(s) will be converted to a format displayable by the

    51   <p align="left">Use the <strong>Available Information</strong> page to choose how the

    61         Carbide.c++ analyzer and assigned the .npi extension. </li>

    52     profiler session is imported. The options include:</p>

    62     </ul>

    53   <ul>

    63     <p>After selecting the file, the <strong>PI views included in the

    54     <li>Project importer &#8212; select this option if you have a Carbide project that has a PKG file or if you have a standalone PKG file (a PKG file that has absolute paths)</li>

    64     analysis</strong><strong>for <em>filename</em>.dat</strong> table will

    55     <li>Project and ROM importer &#8212; select this option if you have both a Carbide project / package file for the profiled application as well as the ROM image symbol file and OBY file for the profiled device </li>

    65     display a list of available views, according to the trace types available

    56     <li>ROM importer &#8212; select this option if you have  the ROM image symbol file and the OBY file for the profiled device</li>

    66     in the selected .dat file. </p>

    57     <li>Unknown importer &#8212; select this option when you have neither a project or a ROM image </li>

    67     <ul>

    58   </ul>

    68       <li>By default, all available trace types in the table are selected, so

    59   <p align="left">Click <strong>Next</strong> to continue.</p>

    69         you can de-select the types you do not wish to include in the analysis.

    60   <p align="left" class="note"><strong>NOTE</strong> You can also click the Finish button (if enabled) to fill in the remaining wizard pages  with persisted values from the last .dat file import. In a new workspace or first time a workspace is used, you will need to define related information in remaining pages, since there is no previous import related to the new workspace. For a new imported .dat file, a new output file name will be generated base on this input file name (+ _digit + .npi).</p>

    70         The CPU load view is a mandatory analysis and cannot be

    61   <p align="center"><img src="images/import_dat_file_step3.png"

    71       de-selected.</li>

    62  width="629" height="705"></p>

    72     </ul>

    63   <p align="center" class="figure">Figure 3. Enter known Available

    73     <p>Click Next to continue. </p>

    74     <p align="center"><img src="images/CB_import_step2.PNG" alt=""></p>

    75     <p align="center" class="figure">Figure 2. Select Profiler Data File</p>

    76   </li>

    77   <li><a name="Select_Known_Available_Information"></a>Select Known Available

    78     information 

    79     <p align="left">Use the <strong>Available Information</strong> page to

    80     choose how the profiler session is imported. The options include:</p>

    81     <ul>

    82       <li>Project importer &mdash; select this option if you have a Carbide

    83         project that has a PKG file or if you have a standalone PKG file (a PKG

    84         file that has absolute paths)</li>

    85       <li>Project and ROM importer &mdash; select this option if you have both

    86         a Carbide project / package file for the profiled application as well

    87         as the ROM image symbol file and OBY file for the profiled device </li>

    88       <li>ROM importer &mdash; select this option if you have the ROM image

    89         symbol file and the OBY file for the profiled device</li>

    90       <li>Unknown importer &mdash; select this option when you have neither a

    91         project or a ROM image </li>

    92     </ul>

    93     <p align="left">Click <strong>Next</strong> to continue.</p>

    94     <p align="left" class="note"><strong>NOTE</strong> You can also click the

    95     Finish button (if enabled) to fill in the remaining wizard pages with

    96     persisted values from the last .dat file import. In a new workspace or

    97     first time a workspace is used, you will need to define related information

    98     in remaining pages, since there is no previous import related to the new

    99     workspace. For a new imported .dat file, a new output file name will be

   100     generated based on this input file name (+ (digit) + .npi).</p>

   101     <p align="center"><img src="images/import_dat_file_step3.png"></p>

   102     <p align="center" class="figure">Figure 3. Enter known Available

    65   <li><a name="ROM_files"></a>If  <strong>Both</strong> or <strong>the ROM image symbol file</strong> option is selected, the <strong>Select build files from ROM</strong> dialog appears. (optional) </li>

   104   </li>

    66   <p>Use the <strong><a href="../../reference/analyzer/import_rom_build_files.htm">Select build files from ROM</a></strong> dialog to select the build files that correspond to the ROM on the device. Start by selecting the SDK, then the ROM OBY file as well as the ROM symbol file. When done, clickc Next. </p>

   105   <li><a name="ROM_files"></a>If <strong>Both</strong> or <strong>the ROM image

    67   <p align="center"><img src="../../images/wnd_import_rom_build_files.png" width="629" height="705"></p>

   106     symbol file</strong> option is selected, the <strong>Select build files

   107     from ROM</strong> dialog appears. (optional) </li>

   108 

   109   <p>Use the <strong><a

   110   href="../../reference/analyzer/import_rom_build_files.htm">Select build files

   111   from ROM</a></strong> dialog to select the build files that correspond to the

   112   ROM on the device. Start by selecting the SDK, then the ROM OBY file as well

   113   as the ROM symbol file. When done, click Next. </p>

   114 

   115   <p align="center"><img src="../../images/wnd_import_rom_build_files.png"></p>

   116 

    69   <li><a name="Select_Associated_Project_and_Package"></a>Select

   118   <li><a name="Select_Associated_Project_and_Package"></a>Select Associated

    70     Associated Project and Package (.pkg) File</li>

   119     Project and Package (.pkg) File 

    71   <p align="left">Use the Associated Project and Package (.pkg) File

   120     <p align="left">Use the Associated Project and Package (.pkg) File page to

    72     page to select one or more projects to associate with the imported .dat

   121     select one or more projects to associate with the imported .dat file as

    73     file as well as choosing its project configuration. Use the Add PKG

   122     well as choosing its project configuration. Use the Add PKG File control to

    74     File control to add a .pkg file during the import operation or the

   123     add a .pkg file during the import operation or the Remove PKG Files control

    75     Remove PKG Files control to remove a PKG file from the imported

   124     to remove a PKG file from the imported profiler session. Click

    76     profiler session. Click <strong>Next</strong> to continue.</p>

   125     <strong>Next</strong> to continue.</p>

    77   <p align="center"><img src="images/import_dat_file_step4.png"

   126     <p align="center"><img src="images/import_dat_file_step4.png"></p>

    78  width="517" height="496"></p>

   127     <p align="center" class="figure">Figure 5. Enter Associated Project and

    79   <p align="center" class="figure">Figure 5. Enter Associated Project

   128     Package (.pkg) File Information</p>

    80     and Pakage (.pkg) File Information</p>

   129   </li>

    89   <p>Use the Output File and Project page to import the .dat file into

   132   <p>If the DAT file has button trace enable, the <b>Select Key Press Mapping

    90 an existing project or create a new empty project. In addition, use the

   133   Profile</b> page appears. Select either a Carbide builtin Key Map Profile or

    91 Output file name field to specify the name output file name for the

   134   user defined profile (if available) for the target device key map. The key

    92 imported .dat file.</p>

   135   map profile selected in the <strong>Window &gt; Preferences &gt; Carbide.c++

   136   &gt; Performance Investigator</strong> preference panel is highlighted as the

   137   suggested default. </p>

    94   <p align="center"><img src="images/import_dat_file_step5.png"

   139   <p>A suggested key profile will also be selected if only one ROM kit/SDK is

    95  width="517" height="496"></p>

   140   selected previously in this import wizard or the profile XML file in the ROM

    96   <p align="center" class="figure">Figure 7. Enter Output File and

   141   kit/SDK contains only one key map profile.</p>

    97 Project Information</p>

   142 

    98   <li>Click Finish to create the *.npi file and open it with the

   143   <p align="center"><img src="images/importdatfile_keyprofile.png"

    99 Analyzer (Figure 8).</li>

   144   alt="keymap profile"></p>

   100   <p align="center"><img src="images/importdatfile_step7.png"

   145 

   101  width="708" height="653"></p>

   146   <p align="center" class="figure">Figure 6. Select Key Press Mapping Profile

   102   <p align="center" class="figure">Figure 8. Performance Investigator

   147   </p>

   103 Analyzer</p>

   148   <li><a name="Select_Output_File_and_Project"></a>Select Output File and

   149     Project </li>

   150 

   151   <p>Use the Output File and Project page to import the .dat file into an

   152   existing project or create a new empty project. </p>

   153 

   154   <p align="center"><img src="images/import_dat_file_step5.png"></p>

   155 

   156   <p align="center" class="figure">Figure 7. Enter Output File and Project

   157   Information</p>

   158   <li>Click Finish to create the *.npi file.</li>

   159   <li>If <b>Instructions executed</b> has been selected as one of the trace, a

   160     the dialog below is displayed during PIAnalyser file import (once for each

   161     file f several are imported): 

   162     <p align="center"><img

   163     src="../../reference/analyzer/images/MIPS_speed_dialog.png"></p>

   164   </li>

   165   <li>If you imported only one file, PIAnalyser will open showing the views

   166     selected for that file. 

   167     <p>If you imported several files, a project will be opened to the

   168     <strong>Carbide Project Explorer</strong> where you can choose the file to

   169     be viewed with PIAnalyser.</p>

   170   </li>

   108   <li><a href="../../reference/analyzer/main_view.htm" align="left">Analyzer

   176   <li><a href="../../reference/analyzer/main_view.htm">Analyzer View</a></li>

   109 View</a></li>

   112 <div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>

   179 

   180 <div id="footer">

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

   182 reserved. <br>

   183 License: <a

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