INTRODUCTION TO iSYSTEM TOOLS

V 21.1

Introduction to iSYSTEM tools

Contents

01 Working with iSYSTEM tools 3

02 What is winIDEATM IDE ? 5

03 iSYSTEM environment setup 5

04 Development process with winIDEA 6

05 Download and installation 7

06 Licensing 8

07 BlueBox Activation keys 9

Get to know the development process with iSYSTEM tools and install winIDEA.

01

• Program the FLASH memory

• Get detailed insight into the microcontroller application

• Debug and test single-core, multi-core or SoC based embedded targets

• Synchronously start/stop two or more cores/SoCs

• Measure execution time and performance

• Collect code coverage metrics

• Track time correlation of signals outside the microcontroller during the application execution. Signals can be analog or digital electrical signals, or interface signals to other parts of the electronic circuit board (CAN, LIN, SPI…)

• Perform On-Target Unit, System and Hardware-in-the-loop (HIL) testing without instrumenting the code

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 01 / Working with iSYSTEM tools 3

With iSYSTEM tools you can:

Working with iSYSTEM tools

What is winIDEATM IDE ?02

winIDEATM IDE (Integrated Development Environment) in conjunction with iSYSTEM BlueBox is a tool for debugging, testing and analyzing embedded systems. It enables access to single and multi-core microcontrollers/SoCs and offers different forms of debug interfaces to work with your microcontroller and debug hardware. This gives you insight into your application and its function on your target device.

winIDEA is used for:

• Flashing software on the Target

• Finding bugs in code

• Analyzing which parts of the code were executed and which were not on the target microcontroller (code coverage)

• Measuring the actual time taken to execute portions of the code on the target microcontroller (profiler)

• Getting insight into the embedded operating system (OS awareness)

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 02 / What is winIDEATM IDE? 4

Flash Programming & Debugging

Tracing

Code CoverageAnalysis

Timing & Perfomance Analysis

winIDEA

iSYSTEM environment setup03

A typical setup for debugging embedded software with winIDEA consists of:

• winIDEAwinIDEA Integrated DevelopmentEnvironment runs on the development PC.

• BlueBoxBlueBox On-Chip Analyzer tool provides a hardware interface between the development PC running winIDEA and the target microcontroller.

• Microcontroller unitThe target microcontroller, on which the embedded software is executed, is fitted either to a semiconductor vendor’s development board or the final circuit board of the product being developed.

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 03 / iSYSTEM environment setup 5

PC with winIDEA™

Integrated Development Environment

iSYSTEM BlueBox

On-Chip Analyzer Tool

Your hardware

Evaluation Board or User Target Board

Development process with winIDEA04

When you finish coding your application, build the source code.

winIDEA offers a complete build environment, including

• Editor, to build the C/C++ embedded software

• 3rd party build environment and import the output into winIDEA.

The code is then programmed through the BlueBox into the program flash on the Target microcontroller.

Output of the build process is typically an ELF file, which is compliant with the DWARF debugging data format. It contains executable code with debug information, such as address and size of global variables, functions entry/exit points and local variables, addresses of interrupt vectors and routines, etc.

Use winIDEA for debugging and testing to meet application requirements and quality objectives. Introduction to BlueBox and winIDEA / Unit 00 / Chapter 04 / Development process with winIDEA 6

Debug the application

winIDEA BlueBox CPU

Build the application

*.ELF file

Found bugs?

Application Unit/System

testing

Software release

NOYESFix source code

Download and installation05

winIDEA is a standard Windows application and is installed as any other Windows program.

To perform debugging with winIDEA and the BlueBox, it is recommended that your development PC meets the following requirements:

• OS Windows 10 (64-bit), Windows 7 and higher, OS Linux

• CPU: 4-8 cores

• RAM: 12GB or more

• HDD: 100GB or more (SSD)

To install winIDEA, download the installation file from iSYSTEM website, run it and follow the installation wizard.

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 05 / Download and installation 7

Install winIDEAThe default folder is <DRIVE>:\iSYSTEM\winIDEA

Start winIDEA

1

2

3

Download winIDEA

Licensing06

Every new iSYSTEM BlueBox in conjunction with winIDEA operates in an evaluation period without any restrictions for 10 days from the first time of use.

Within the 10-days evaluation period BlueBox must be licensed for operation with winIDEA.

A valid winIDEA license includes:

• one year of technical support

• one year of upgrades and new versions

Specific product functionalities require Activation keys. During winIDEA evaluation period it operates with all its functionalitytemporarily enabled.

Activation Keys purchased with the BlueBoxare already pre-programmed by iSYSTEM.Later additional Activation Keys can be purchased to expand the BlueBox functionality.

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 06 / Licensing 8

winIDEA license

Activation Key – Trace

Activation Key – Multi-core

Activation Key – Debug

BlueBox Activation Keys07

Three major types of BlueBox Activation Keysare provided:

• DebugCovers debugging functionality on a microcontroller.

• TraceCovers timing and performance analysis, code coverage analysis, or similar activities based upon trace information on a microcontroller.

• Multi-coreCovers use with multi-core microcontrollers.

The table shows which activation keys are required for different purposes.

Introduction to BlueBox and winIDEA / Unit 00 / Chapter 07 / BlueBox Activation Keys 9

✓

✓

✓

✓

✓

✓

✓

✓

✓

Debug Trace Multi-core

I want to find bugs in code

I want to do a timing analysis

I want to do code coverage

I want to find bugs in code and my MCU has two or more cores

I want to do a timing analysis and my CPU has two or more cores ✓

For more information on licensing options contact your iSYSTEM on license@isystem.com.

Further Reading

On this topic:

• iSYSTEM Software and Hardware tools

• How to download winIDEA IDE

• How iSYSTEM licensing works

• More Tutorials…

More resources:

• winIDEA Online Help

• Knowledge Base

• Webinars

• Video Tutorials

• Application Notes

• Technical Notes

• User Manuals