13 device, saving the profiler data file, and transferring the file to your PC, |
13 device, saving the profiler data file, and transferring the file to your PC, |
14 you must then import the profiler data (.dat) file. Importing the data file |
14 you must then import the profiler data (.dat) file. Importing the data file |
15 converts the file into a format that can be displayed by the analyzer (a .NPI |
15 converts the file into a format that can be displayed by the analyzer (a .NPI |
16 file).</p> |
16 file).</p> |
17 |
17 |
18 <p class="note"><strong>NOTE</strong> If a large .dat file is imported, the |
18 <p class="note"><strong>NOTE</strong> You do not necessarily need to collect |
19 graph and table response time will slow down until the large NPI file is saved. |
19 the performance data by using PI Profiler on the device, but you can also do |
20 Saving the NPI file will be performed in the background and cannot be |
20 profiling remotely, directly from the PI Wizard in Carbide.c++. For more |
21 canceled.</p> |
21 information, see <a href="collect_prof_data_remotely.htm">Collecting Profiler |
|
22 Data Remotely</a>.</p> |
22 |
23 |
23 <p>Importing a profiler data file will vary depending on if your application |
24 <p>Importing a profiler data file will vary depending on if your application |
24 was built by Carbide.c++ or is a standalone application. To find the binaries |
25 was built by Carbide.c++ or is a standalone application. To find the binaries |
25 in your application, the importer will need the *.pkg file created when your |
26 in your application, the importer will need the *.pkg file created when your |
26 application was built, or you will need to list all application binaries. If |
27 application was built, or you will need to list all application binaries. If |
32 <p>Unless your application executes from a fixed address in phone memory (e.g., |
33 <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 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 Profiler application when capturing your application data in a profiler data |
35 file.</p> |
36 file.</p> |
36 |
37 |
|
38 <p class="note"><strong>NOTE</strong> If a large .dat file is imported, the |
|
39 graph and table response time will slow down until the large NPI file is saved. |
|
40 Saving the NPI file will be performed in the background and cannot be |
|
41 canceled.</p> |
|
42 |
37 <p>To import your profiler data file, perform the following steps.</p> |
43 <p>To import your profiler data file, perform the following steps.</p> |
38 |
44 |
39 <div class="step"> |
45 <div class="step"> |
40 <h4>Importing a Profiler Data File</h4> |
46 <h4>Importing a Profiler Data File</h4> |
41 <ol> |
47 <ol> |
42 <li><a name="Select_Performance_Investigator_Data"></a>Select Performance |
48 <li><a name="Select_Performance_Investigator_Data"></a>Start the import |
43 Investigator Data</li> |
49 wizard form the Carbice.c++ toolbat by selecting <strong>Carbide</strong> |
44 |
50 > <strong>Performance Investigator</strong></li> |
45 <p>Select <strong>File > Import...</strong> from Carbide.c++ to display |
|
46 Import dialog box (Figure 1), and select Performance Investigator Data and |
|
47 click <strong>Next</strong>.</p> |
|
48 |
|
49 <p align="center"><img src="images/importdatfile_step1.png"></p> |
|
50 |
|
51 <p align="center" class="figure">Figure 1. Carbide.c++ Import window </p> |
|
52 <li><a name="Select_Profiler_Data_File" |
51 <li><a name="Select_Profiler_Data_File" |
53 id="Select_Profiler_Data_File"></a>Select Profiler Data File(s) |
52 id="Select_Profiler_Data_File"></a>Select Profiler Data File(s) |
|
53 <p>First use the radio buttons and select to get profiler data <strong>From |
|
54 File System</strong>. </p> |
|
55 <p class="note"><strong>NOTE</strong> Use the <strong>From Device via |
|
56 TraceViewer</strong> option if you want to collect new profiler data |
|
57 remotely from the device. For more information, see <a |
|
58 href="collect_prof_data_remotely.htm">Collecting Profiler Data |
|
59 Remotely</a>.</p> |
54 <p>Select .dat file(s) to the <strong>From File System</strong> list by |
60 <p>Select .dat file(s) to the <strong>From File System</strong> list by |
55 selecting either</p> |
61 selecting either</p> |
56 <ul> |
62 <ul> |
57 <li><strong>Add File</strong> and browsing to the file, or</li> |
63 <li><strong>Add File</strong> and browsing to the file, or</li> |
58 <li><strong>Add Directory</strong> and browsing to the directory you want |
64 <li><strong>Add Directory</strong> and browsing to the directory you want |
59 to import files from.</li> |
65 to import files from.</li> |
60 <li>The .dat file(s) will be converted to a format displayable by the |
66 <li>Use the <strong>Remove</strong> button to remove one file from the |
61 Carbide.c++ analyzer and assigned the .npi extension. </li> |
67 list, or</li> |
|
68 <li>Use the <strong>Remove All</strong> button to clear all files from |
|
69 the list.</li> |
62 </ul> |
70 </ul> |
|
71 <p>The .dat file(s) will be converted to a format displayable by the |
|
72 Carbide.c++ analyzer and assigned the .npi extension. </p> |
63 <p>After selecting the file, the <strong>PI views included in the |
73 <p>After selecting the file, the <strong>PI views included in the |
64 analysis</strong><strong>for <em>filename</em>.dat</strong> table will |
74 analysis</strong><strong>for <em>filename</em>.dat</strong> table will |
65 display a list of available views, according to the trace types available |
75 display a list of available views, according to the trace types available |
66 in the selected .dat file. </p> |
76 in the selected .dat file. </p> |
67 <ul> |
77 <ul> |
68 <li>By default, all available trace types in the table are selected, so |
78 <li>By default, all available trace types in the table are selected, so |
69 you can de-select the types you do not wish to include in the analysis. |
79 you can de-select the types you do not wish to include in the analysis. |
70 The CPU load view is a mandatory analysis and cannot be |
80 The CPU load view is a mandatory analysis and cannot be |
71 de-selected.</li> |
81 de-selected.</li> |
|
82 <li>The trace types/views are selected separately for each .dat file.</li> |
72 </ul> |
83 </ul> |
73 <p>Click Next to continue. </p> |
84 <p>After selecting the files and views, click <strong>Next</strong> to |
74 <p align="center"><img src="images/CB_import_step2.PNG" alt=""></p> |
85 continue. </p> |
|
86 <p align="center"><img src="images/CB_import_step2.png"></p> |
75 <p align="center" class="figure">Figure 2. Select Profiler Data File</p> |
87 <p align="center" class="figure">Figure 2. Select Profiler Data File</p> |
76 </li> |
88 </li> |
77 <li><a name="Select_Known_Available_Information"></a>Select Known Available |
89 <li><a name="Select_Known_Available_Information"></a>Select Known Available |
78 information |
90 information |
79 <p align="left">Use the <strong>Available Information</strong> page to |
91 <p align="left">Use the <strong>Available Information</strong> page to |
96 persisted values from the last .dat file import. In a new workspace or |
108 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 |
109 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 |
110 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 |
111 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> |
112 generated based on this input file name (+ (digit) + .npi).</p> |
101 <p align="center"><img src="images/import_dat_file_step3.png"></p> |
113 <p align="center"><img src="images/importdatfile_step3.png"> </p> |
102 <p align="center" class="figure">Figure 3. Enter known Available |
114 <p class="figure">Figure 3. Enter known Available Information</p> |
103 Information</p> |
|
104 </li> |
115 </li> |
105 <li><a name="ROM_files"></a>If <strong>Both</strong> or <strong>the ROM image |
116 <li><a name="ROM_files"></a>If <strong>Both</strong> or <strong>the ROM image |
106 symbol file</strong> option is selected, the <strong>Select build files |
117 symbol file</strong> option is selected, the <strong>Select build files |
107 from ROM</strong> dialog appears. (optional) </li> |
118 from ROM</strong> dialog appears. (optional) </li> |
108 |
119 |
146 <p align="center" class="figure">Figure 6. Select Key Press Mapping Profile |
157 <p align="center" class="figure">Figure 6. Select Key Press Mapping Profile |
147 </p> |
158 </p> |
148 <li><a name="Select_Output_File_and_Project"></a>Select Output File and |
159 <li><a name="Select_Output_File_and_Project"></a>Select Output File and |
149 Project </li> |
160 Project </li> |
150 |
161 |
151 <p>Use the Output File and Project page to import the .dat file into an |
162 <p>Use the Output File and Project page to import the *.npi file into an |
152 existing project or create a new empty project. </p> |
163 existing project or create a new empty project. </p> |
|
164 |
|
165 <p class="note">NOTE If you used remote profiling for collecting profiler |
|
166 data from the device, the original *.dat file will also be included in the |
|
167 selected project.</p> |
153 |
168 |
154 <p align="center"><img src="images/import_dat_file_step5.png"></p> |
169 <p align="center"><img src="images/import_dat_file_step5.png"></p> |
155 |
170 |
156 <p align="center" class="figure">Figure 7. Enter Output File and Project |
171 <p align="center" class="figure">Figure 7. Enter Output File and Project |
157 Information</p> |
172 Information</p> |
158 <li>Click Finish to create the *.npi file.</li> |
173 <li>Click Finish to create the *.npi file. |
|
174 <p class="note">NOTE Carbide.c++ reserves a large block of memory for the |
|
175 Java Virtual Machine (JVM) to run the whole IDE. However, in some cases, |
|
176 where Profiler trace log is too long in time and/or CPU load has been |
|
177 extensively high over the use case, the trace import process may fail due |
|
178 to out-of-memory situation. The out-of-menory may also lead to instability |
|
179 issues with Carbide itself, but an error message will be always be shown: |
|
180 <strong>Multiple problems have occurred</strong>. Jave heap space.<br> |
|
181 This problem can be avoided by keeping the profiled use cases shorter (the |
|
182 recommendation is maximum 5 minutes), and by selecting only those Profiler |
|
183 plug-ins that are needed for analysing the use case. Shorter use cases (in |
|
184 time) and smaller amount of selected profiler plug-ins also ease up the |
|
185 analysis phase, since it is easier to a browse shorter set of data and to |
|
186 pinpoint the possible performance issues within the trace.<br> |
|
187 If you need to analyse longer use cases, there are also other tools |
|
188 available for long-period-testing (LPT). For example, you can run the Nokia |
|
189 Energy Profiler (NEP) directly on target and it can be used for LPT type of |
|
190 use cases.</p> |
|
191 </li> |
159 <li>If <b>Instructions executed</b> has been selected as one of the trace, a |
192 <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 |
193 the dialog below is displayed during PIAnalyser file import (once for each |
161 file f several are imported): |
194 file f several are imported): |
162 <p align="center"><img |
195 <p align="center"><img |
163 src="../../reference/analyzer/images/MIPS_speed_dialog.png"></p> |
196 src="../../reference/analyzer/images/MIPS_speed_dialog.png" alt=""></p> |
164 </li> |
197 </li> |
165 <li>If you imported only one file, PIAnalyser will open showing the views |
198 <li><strong>Performance Investigator</strong> view will open with the |
166 selected for that file. |
199 imported files listed in it. A project will also be opened to the |
167 <p>If you imported several files, a project will be opened to the |
200 <strong>Carbide Project Explorer</strong> including the imported files. |
168 <strong>Carbide Project Explorer</strong> where you can choose the file to |
201 <p>If you imported only one file, PIAnalyser will also open showing the |
169 be viewed with PIAnalyser.</p> |
202 views selected for that file. If you imported several files, you can open |
|
203 any one of them by double-clicking the file name in the Performance |
|
204 Investigator view or in the Project Explorer.</p> |
170 </li> |
205 </li> |
171 </ol> |
206 </ol> |
172 </div> |
207 </div> |
173 |
208 |
174 <p align="left"><strong>Related references</strong></p> |
209 <p align="left"><strong>Related references</strong></p> |
175 <ul> |
210 <ul> |
|
211 <li><a href="collect_prof_data_remotely.htm"></a><a |
|
212 href="../../reference/analyzer/import_rom_build_files.htm">Select build |
|
213 files from ROM</a></li> |
|
214 <li><a href="collect_prof_data_remotely.htm">Collecting Profiler Data |
|
215 Remotely</a></li> |
176 <li><a href="../../reference/analyzer/main_view.htm">Analyzer View</a></li> |
216 <li><a href="../../reference/analyzer/main_view.htm">Analyzer View</a></li> |
177 <li><a href="key_profile_pref.htm">Key Press Profile</a> </li> |
217 <li><a href="key_profile_pref.htm">Key Press Profile</a> </li> |
178 </ul> |
218 </ul> |
179 |
219 |
180 <div id="footer"> |
220 <div id="footer"> |