Application Notes

These documents give you an insight view in the power of BlueBox technology.

 

General

isystem.connect SDK enables you to use BlueBox tools over different programming languages. This Application Note describes how to create, edit and save winIDEA workspace using isystem.connect with Python.

 
Network Analyzers

Having a dedicated mini-HIL controller, with the ability to correlate external signals (analog, digital or SPI messages) with the execution of embedded applications, is becoming increasingly useful in modern embedded systems. Aside from being able to generate analog and digital signals, ADIO can also capture and display them in parallel to the microcontroller code execution, i.e. synchronously to the program trace.

This Application Note describes a few examples of how an ADIO can be used during development and testing of embedded systems.

 

Having a dedicated Network Analyzer synchronized with the program trace can be very useful, especially when trying to debug a large number of interconnected devices (like ECUs in a car).

This Application Note describes a few different examples of how an CAN/LIN can be used to ease the development and the debugging of connected devices that are using either a CAN or a LIN network: Network traffic sniffing, Timing Analysis, Message injection, CAN/LIN message as trigger for trace recording, isystem.connect SDKs.

 

 
AUTOSAR

AUTOSAR Classic profiling means profiling the runtime behavior of an AUTOSAR Classic based application, specifically the application itself, the Run-Time Environment (RTE), the Operating System (OS), and other parts of the Basic Software (BSW). Results cover use-cases such as CPU load analysis, event-chain analysis, timing requirements validation, timing constraint validation, OS metric calculation etc.

This Application Note gives an overview of the AUTOSAR Classic Profiling use-case.

 

 
Renesas R-Car

The boot-up process of complex SoCs can be quite elaborate and may involve a mixture of SoC-specific bootloaders for the real-time core, often used as the master boot core, and various bootloaders for the application cores.

This Application Note describes how to utilize the ARM System Trace Macrocell (STM) for timing measurement of the boot-up process of complex SoCs, such as the Renesas R-Car family.

 
Infineon AURIX

This Application Note provides an overview of the on-chip trace architecture and capabilities of the Infineon TriCore AURIX microcontroller family, and introduces two use cases (Multi-Core OS Profiling via DAP interface and Multi-Core OS and Program Trace via AGBT interface) of the AURIX trace infrastructure in combination with the iSYSTEM On-Chip Analyzers BlueBox iC5000, iC5700 or iC6000.

 

This Application Note describes how to setup the iSYSTEM winIDEA IDE and BlueBox On-Chip Analyzers to synchronously debug and trace two Infineon TriCore AURIX devices. Additionally it provides configuration instructions of setting up the CAN/LIN module to view the communication between both devices.

 

 
Vector MICROSAR

This Application Note describes how to use the winIDEA Analyzer for the timing analysis of the Vector MICROSAR operating system. Timing analysis records and examines the runtime behavior of operating system objects such as tasks and ISRs, as well as RTE objects like Runnables and communication interfaces.

 

 
ETAS RTA-OS Profiling

This Application Note describes how to use winIDEA IDE for Multi-OS timing analysis (profiling) using the ETAS Lightwight Hypervisor, RTA-HVR. The description is based on a demo application provided by ETAS. The demo application executes on a dual-core SPC58EC Chorus4M device.

The master core, which is operational after reset, executes a standards AUTOSAR OS (RTA-OS) and starts the slave core. The slave core executes the hypervisor which provides two virtual machines (VM0 and VM1). Within each of these VMs an (adapted) AUTOSAR OS (RTA-OS) is running.

 

This Application Note explains how to profile and analyze the timing-behavior of ETAS RTA-OS based AUTOSAR applications, and configure the different Profiling use-cases(Running Task/ISR2 via Data Trace, Task State/Running ISR via Data Trace, Runnables via Program Flow Trace) in detail.

 

 
Elektrobit EB tresos

This Application Note describes three approaches for OS scheduling analysis on EB tresos Safety OS. EB tresos Safety OS is a micro-kernel based OS and thus does not follow the approaches known from classic AUTOSAR OS (i.e. OSEK) implementations.

 

This Application Note describes how to use the winIDEA Analyzer for the timing analysis of the Elektrobit EB tresos AutoCore operating system. Timing analysis records and examines the runtime behavior of operating system objects such as tasks and ISRs.

 

This Application Note describes how to use the iSYSTEM winIDEA IDE Analyzer for the timing analysis of AUTOSAR Runnables of the two Elektrobit AUTOSAR solutions “EB tresos AutoCore” and “EB tresos Safety”.