Failed to load .axf

Hi again GB

In general, to measure the runtime performance of your code, you can count cycles using the Cortex-M's memory-mapped DWT performance counters such as DWT_CYCCNT, or count instructions as shown in the FVP model's simulated LCD display, or use the SysTick Timer, or use Streamline bare-metal.

See also Knowledge Base Article "Measuring the cycle count of the Cortex-M3 and Cortex-M4 processor's own activity" at developer.arm.com/.../latest

Unfortunately Cortex-M4 FVP does _not_ model the DWT, but cycle-accurate models are available separately.
 
You can run your program on a cycle-accurate model or real hardware, and read/view the number of cycles executed, either from within your code itself, or from the model's simulated LCD display, or from a connected debugger, for example, the Arm Development Studio Debugger.  

To measure the cycles per function, you will need to read the cycle count on entry into the function, then read the cycle count again on exit from the function, and calculate the difference.  You can do this either under your program control, or from the debugger (e.g. by setting breakpoints on function entry/exit).

If you need more information on this, I recommend you raise an official support case from the support menu above.

Hope this helps,

Stephen

Hi again GB

In general, to measure the runtime performance of your code, you can count cycles using the Cortex-M's memory-mapped DWT performance counters such as DWT_CYCCNT, or count instructions as shown in the FVP model's simulated LCD display, or use the SysTick Timer, or use Streamline bare-metal.

See also Knowledge Base Article "Measuring the cycle count of the Cortex-M3 and Cortex-M4 processor's own activity" at developer.arm.com/.../latest

Unfortunately Cortex-M4 FVP does _not_ model the DWT, but cycle-accurate models are available separately.
 
You can run your program on a cycle-accurate model or real hardware, and read/view the number of cycles executed, either from within your code itself, or from the model's simulated LCD display, or from a connected debugger, for example, the Arm Development Studio Debugger.  

To measure the cycles per function, you will need to read the cycle count on entry into the function, then read the cycle count again on exit from the function, and calculate the difference.  You can do this either under your program control, or from the debugger (e.g. by setting breakpoints on function entry/exit).

If you need more information on this, I recommend you raise an official support case from the support menu above.

Hope this helps,

Stephen