Run custom software for simulation with Arm IP Explorer
Introduction
Run a pre-installed example and compare performance
Create a custom example
Upload and run your custom example
Next Steps
Run custom software for simulation with Arm IP Explorer
Who is this for?
This is an introductory topic for IP Explorer users using the software simulation platforms available.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Run a pre-installed example on IP Explorer simulation platform
- Create your own example benchmark
- Upload and run your benchmark
Prerequisites
Before starting, you will need the following:
- An Arm account that can access IP Explorer
- (Optional) A Linux machine with the desired compilers installed
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll use Arm IP Explorer to run built-in and custom software on cloud-hosted simulation platforms for Arm Cortex-M processors. You’ll launch an example to collect cycle-accurate results, edit a marked C source region to create a benchmark, and build a
.tgz archive on Linux. Then, you’ll upload the archive, choose the project and compiler, and compare cycle counts across Cortex-M instances.Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Confirm that you’re logged in to IP Explorer and that you created the instances in the earlier step. Refresh Simulate Processors so recently created instances appear at the top.
Wait for processing to finish, then reopen the Select/Upload Software menu. Confirm that you uploaded the
.tgz archive produced by the provided software package.Select Arm Compiler for Embedded (AC6). Use the same compiler when you run your custom benchmark.
Edit the marked sections in the provided C source file to add or modify the code you want to measure. Keep the project structure unchanged so the package uploads correctly.
A successful run produces cycle-accurate benchmark results and confirms execution on a Fast Models system. Run the same software on My Cortex-M0 and My Cortex-M7, then compare the reported cycle counts.