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).
NOTE 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.
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.
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.
To import your profiler data file, perform the following steps.
Select File > Import... from Carbide.c++ to display Import dialog box (Figure 1), and select Performance Investigator Data and click Next.
Figure 1. Carbide.c++ Import window
Select .dat file(s) to the From File System list by selecting either
After selecting the file, the PI views included in the analysisfor filename.dat table will display a list of available views, according to the trace types available in the selected .dat file.
Click Next to continue.
Figure 2. Select Profiler Data File
Use the Available Information page to choose how the profiler session is imported. The options include:
Click Next to continue.
NOTE 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).
Figure 3. Enter known Available Information
Use the Select build files from ROM 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.
Figure 4. Select build files from ROM dialog
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 Next to continue.
Figure 5. Enter Associated Project and Package (.pkg) File Information
If the DAT file has button trace enable, the Select Key Press Mapping Profile 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 Window > Preferences > Carbide.c++ > Performance Investigator preference panel is highlighted as the suggested default.
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.
Figure 6. Select Key Press Mapping Profile
Use the Output File and Project page to import the .dat file into an existing project or create a new empty project.
Figure 7. Enter Output File and Project Information
If you imported several files, a project will be opened to the Carbide Project Explorer where you can choose the file to be viewed with PIAnalyser.
Related references