Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
This example walks you through the two different methods that can be used to profile your Nios II system in terms of resource usage.
Users are adviced to go through this page before starting the tutorials in Profiling Nios II Systems.pdf. The Nios II Embedded Evaluation Kit (NEEK) , Cyclone III Edition is used in this tutorial but the tutorial can be applied for other Development Kits as well.
This example contains tutorials for users to measure the performance of their Nios II systems using the: a) GNU Profiler b) Performance_counter
The contents in the attached zip file is required to run through the tutorial. The source files can be found in the following directories :
..\profiler_software_examples\source\SBT_flow:
Contains the source files for Software Build Tools flow for use with Nios II Software Build Tools for Eclipse.
-- The steps to use the SBT_flow source files are mentioned in Profiling Nios II Systems.pdf.
..\profiler_software_examples\source\CLI_flow:
Contains the ./create-this-app source files for the CLI flow to be used with the Nios II Command Line Interface.
-- The steps to use the CLI_flow source files Profiling Nios II Systems.pdf.
a) GNU Profiler - The GNU Profiler provides an overview of the resource usage for the entire system. It adds overhead evenly through the system and users can track processor utilization based on the system clock timer.
b) Performance Counter - The performance counters and timestamp interval timers are utilized in this program to measure the overall performance of a Nios II system, more precisely compared to the GNU profiler. It allows users to identify the code sections that use the most processor time.
This design requires the following:
For more information about how profiling works in Profiling Nios II Systems and ways to troubleshoot several problems that might occur during profiling, please refer to Application Note 391 which is available at http://www.altera.com/literature/an/an391.pdf.
This design is provided as-is and is not supported by Altera.
Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.