01
Find actual errors at runtime
C-RUN performs runtime analysis by checking application execution directly within the development environment. It checks for arithmetic issues, bounds issues and heap integrity and will tell you what went wrong and where.
02
Intuitive and easy-to-use
C-RUN offers a convenient and flexible rule selection in the settings and error filter management. The runtime analysis tool can be used for C and C++ source code and adds efficient instrumentation of diagnosis routines inside your code when enabled. The tool can check your code during execution on the target or in the simulator and you get a direct code correlation and graphical feedback in editor.
03
Integrated with IAR Embedded Workbench
C-RUN is an add-on to IAR Embedded Workbench for Arm and for Renesas RX. C-RUN is designed to be a natural part of your development workflow, when working in a traditional edit/build/debug cycle, running unit tests or doing integration tests. C-RUN provides you with extremely valuable feedback already as soon as the first iteration of code is about to be taken for a test drive.
04
Stand-alone mode
C-RUN can be used standalone to find ”hard to detect” problems in the field. It only requires to build and deploy a test firmware for a unit with the necessary C-RUN tests enabled in IAR Embedded Workbench. The C-RUN output messages will then be redirected to a serial interface and log the messages. The recorded cryptic messages can then be parsed offline to plaintext with the C-SPY command line utility (cspybat) for diagnosis and bug fixing.
Evaluation guide for IAR C-RUN
This guide is an extensive walk-through for evaluating the runtime error-checking capabilities offered by IAR C-RUN. Accompanying projects are available as easy-to-follow demonstrations when going forward with a more thorough evaluation.
FAQ for IAR C-RUN
What is Runtime Analysis?
- By inserting test code into an application, a runtime analysis tool can find real and potential errors in the code while executing the program in a software debugger.
What is a typical error that can be detected with runtime analysis?
- Out of bounds, arithmetical errors and memory inconsistency errors.
Why do I need Runtime Analysis?
- By using runtime analysis, you can find potential and real errors at an early stage, as opposed to finding errors at a later stage which makes product development more expensive and time consuming. It improves cost efficiency and development time, allowing for a speedier time to market.
Does C-RUN support both C and C++?
- Yes.
Can I use C-RUN in C-SPY simulator? And in my actual target hardware?
- Yes and Yes.
How can I evaluate C-RUN?
- A size-limited version of C-RUN is activated for evaluation when you download an evaluation version of IAR Embedded Workbench for Arm or IAR Embedded Workbench for RX.
Which Arm cores does C-RUN support?
- All supported cores in IAR Embedded Workbench for Arm.
Is there any feature limitation of C-RUN evaluation?
- No.
Does my IAR Embedded Workbench version support C-RUN?
- Supported versions:
- - IAR Embedded Workbench for Arm, version 7.20 and forward
- - IAR Embedded Workbench for RX, version 3.10 and forward
- - 12KB code size limited C-RUN is available for evaluation within the 14-days EWARM free evaluation license
Get quote
Want to use this product in your development projects? Our sales team is here to guide you to the right solution. Complete this form, and we will get back to you with a price quote tailored to your needs.