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

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

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

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

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

file).</p>

<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>

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

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

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

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

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

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

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

to describe and list binaries.</p>

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

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

Profiler application when capturing your application data in a profiler data

file.</p>

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

    Investigator Data</li>

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

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

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

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

  <li><a name="Select_Profiler_Data_File"

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

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

    selecting either</p>

    <ul>

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

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

        to import files from.</li>

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

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

    </ul>

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

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

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

    in the selected .dat file. </p>

    <ul>

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

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

        The CPU load view is a mandatory analysis and cannot be

      de-selected.</li>

    </ul>

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

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

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

  </li>

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

    information 

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

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

    <ul>

      <li>Project importer &mdash; 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>

      <li>Project and ROM importer &mdash; 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>

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

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

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

        project or a ROM image </li>

    </ul>

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

    <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 based on this input file name (+ (digit) + .npi).</p>

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

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

  </li>

  <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>

  <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, click Next. </p>

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

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

    Project and Package (.pkg) File 

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

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

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

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

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

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

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

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

    Package (.pkg) File Information</p>

  </li>

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

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

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

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

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

  suggested default. </p>

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

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

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

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

  alt="keymap profile"></p>

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

  </p>

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

    Project </li>

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

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

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

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

  Information</p>

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

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

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

    file f several are imported): 

    <p align="center"><img

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

  </li>

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

    selected for that file. 

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

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

    be viewed with PIAnalyser.</p>

  </li>

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

<div id="footer">

Copyright © 2010 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>