Wireless Debugger 1

DAQ — daqIDEA 2

New Web Page 2

Cortex-M Tools 3

XCP Plug-in integrates

NI Tools

3

Markets and Trends 4

iSYSTEM Tools from

1993—Today

4

CORTEX Market 5

iSYSTEM for 3rd Party

Cortex-M Debugger

5

iSYSTEM for

Renesas E1 Debugger

5

testIDEA Standard/

Professional

6

ZIM Projects @iSYSTEM 6

fitIDEA—How iSYSTEM

does perform testing?

7

Q&A Testautomation 7

Systematic Test Case

Generation

8

Function and Task Profi-

ling via Standard IO

8

DAQ and XCP for Vector

CANoe / CANape

9

iC6000 and AURORA 9

iSYSTEM Blog 10

iSYSTEM @Twitter 11

Zelos3 11

The Last Page 12

I N D U S T R Y ‘ S F I R S T W I R E L E S S D E B U G G E R

T H E E M B E D D E D S O F T W A R E T O O L S C O M P A N Y Debug — Trace — Coverage — Performance — Visualization — Test — Report

B l u e P r i n t News and Innovations

iSYSTEM announced the

introduction of the industry's

first truly wireless debugger

at the ARM TechCon end of

October 2013 in Santa Clara.

The iONE-BT allows the wire-

less communication between

a target application and a PC

running iSYSTEM's winIDEA/

testIDEA debugging and test

software, via Bluetooth.

iONE-BT is the wireless De-

bug & Trace adaptor. On one

end, it establishes a debug

and trace communication

with the target processor, on

the other end it links to

winIDEA/testIDEA, running

on the host PC, via a wireless

communication.

The iONE-BT module can be

supplied directly by the tar-

get system (3.3V) or by a

SuperCap or battery power

module.

The SuperCap or battery mo-

dule receive its input power

from the target system. While

power from the target is

available, it directly supplies

the iONE-BT module and

charges the integrated back-

up energy storage element.

While the target is un-

powered, the iONE-BT is

supplied by the back-up

energy storage.

On the PC-side a USB-

Bluetooth dongle establishes

the bridge between Blue-

tooth and winIDEA/testIDEA.

Besides allowing wireless

access from the PC running

winIDEA/testIDEA across a

lab to a target connected to

the iONE-BT, this new wire-

less debugging capability

opens doors for embedding

debuggers in harsh environ-

ments.

An example: A company em-

beds some controller inside

a device which in turn is de-

ployed in a field or a mine.

Once placed and sealed in

the container, it is extremely

difficult and expensive to

open the container and re-

trieve the controller for the

purpose of debugging the

application or re-flashing the

device. Wireless access (up

to 10 meters) allows this to

be accomplished in the field

with minimal cost and time.

The Bluetooth communica-

tion is compliant to Bluetooth

standard 3.0. The transmit

power is Class 2 (typ. 0dBm)

with a range of approximately

10m. The bandwidth is ap-

proximately 2.1 Mbit/second.

Operating voltage is 3.3V.

The iONE-BT will be first

available as a debugger for

the ARM Cortex-M family of

microcontrollers. Other cores

will be supported in the fu-

ture. The debugging and

trace analysis interface,

winIDEA/testIDEA, are identi-

cal for the iONE-BT as for all

of the other iSYSTEM hard-

ware debug modules, such

as the iC5000. The iONE-BT

will be available for the ARM

Cortex-M at Embedded World

in Nuremberg, end of Febru-

ary 2014.

Page2 B L U E P R I N T

N E W W E B P A G E O N L I N E

What's in it for you? What

will it do for you?

More detailed information

about iSYSTEM tools and

their application

winIDEA Online Help to

give you an in-depth view of

iSYSTEM's tool functionality.

The online help is also part

of a winIDEA installation.

Please use Build 128 (full

installation necessary)

Which industries do al-

ready use iSYSTEM tools?

This sections gives you an

overview about markets,

their requirements and

applications.

3rd party tool solutions

that integrate iSYSTEM

tools and vise versa. In

addition to that the new

winIDEA Online Help lists

more details about those

integrations. Read also the

Technical Note part!

Download Area with

downloads for

- winIDEA/testIDEA

- isystem.connect Software

Development Kits (SDKs)

- iSYSTEM's free Cortex-M

IDE winIDEA OPEN

- ...

iSYSTEM's Eclipse Plug-

ins and more

Why embedded compa-

nies love to work with iSYS-

TEM and iSYSTEM tools?

This page lists benefits of

iSYSTEM and iSYSTEM

tools to help you and your

boss to make the right deci-

sion.

iSYSTEM's past and cur-

rent research projects

about testing and multicore

e m b e d d e d s y s t e m s .

eMOTE is finished, MoTTeM

is ongoing and we just

started a 3rd one covering

multi-core and fault injec-

tion aspects of embedded

systems.

daqIDEA is a tool for the

graphical presentation of

large data sets. It displays

values for different varia-

bles as a 2D chart and as a

table of numeric values.

The data acquired can be

exported to a file and the

variable configuration can

be saved into a configura-

tion file. Charts can be

closely inspected by zoom-

ing and stretching and if

left alone, the maximum

amount of latest data will

be displayed.

The iSYSTEM Blue Box can

perform a high-frequency

data acquisition using real-

time access of the connec-

ted CPU. Up to 256 DAQ

items can be configured on

a blue box. Each DAQ item

can monitor a location of 1-

8 bytes.

Processing time of one DAQ

item (reading it from me-

mory) varies on the CPU

architecture and debug

port speed, but ranges

from 50us-500us.

DAQ sampling periods can

be configured (per individu-

al DAQ item) for maximum,

1ms, 10ms, 100ms and 1s.

Access to the iSYSTEM DAQ

functionality is provided via

isystem.connect. In addi-

tion to that a user may con-

figure a DAQ configuration

using the GUI daqIDEA. It is

a script in Python and can

be modified/extended by

users. Other benefits:

High speed, polling on

Blue Box

Uses debugging interface,

trace is not necessary

Can export data to excel,

csv, text

Included in winIDEA for

free as a Python script

D A Q I D E A - G R A P H I C A L D I S P L A Y O F D A T A

See page 6 — ZIM Projects

More

Information:

isystem.com/

downloads/

winIDEA/help/

See also page 9 — DAQ and

XCP for Vector CANoe/

CANape

See page 11 — Multi-core,

timing behavior, efficiency,

robustness, simulation, on-

target verification = Zelos3

iSYSTEM offers several

dedicated ARM/Cortex de-

bug and test tool packages.

All combine a hardware

debugger connecting to the

target microcontroller

through the debug inter-

face and winIDEA/testIDEA,

iSYSTEM‘s integrated deve-

lopment and test environ-

ment:

iTAG.ZERO—DIY (do it yours-

elf with build instructions

on the web)

iTAG.FIFTY– Complete De-

velopment Platform under

50€ with no code size rest-

rictions and GNU compiler

included (get it via amazon)

The iTAG debug hardware

is driven by winIDEA Open,

iSYSTEM‘s free Cortex IDE

& Compiler software packa-

ge.

iTAG.1K– iTAG.FIFTY soft-

ware upgrade including full

technical support

iTAG.2K– Cortex-M debug

and trace platform

Beside iTAG type of Cortex

debug hardware iSYSTEM

does provide

A wireless Cortex-M de-

bugger iONE-BT as well as

A multi-architecture debug

and analyzer platform

called iC5000, iC6000.

I S Y S T E M I T A G F A M I L Y O F T O O L S

Page 3 B L U E P R I N T

N I A N D I S Y S T E M T O O L S I N T E G R A T E V I A X C P

NI VIP2013, Munich, Oc-

tober 23: iSYSTEM and NI

presented how their tools,

such as LabVIEW and Veri-

Stand, integrate with

winIDEA via XCP. iSYSTEM

had already proven such an

integration using the XCP

master software CANoe

and CANape from Vector

Informatik. It is a plug and

play solution for both wor-

lds using iSYSTEM‘s XCP

plug-in integrated in

winIDEA/testIDEA.

Some background infomra-

tion about XCP: XCP stands

for Universal Measurement

and Calibration Protocol. It

allows the measurement

and calibration of internal

signals and data of an

electronic control unit

(ECU). XCP has been stan-

d a r d i z e d b y A S A M

(Association for Standar-

dization of Automation &

Measurement Systems).

Any compliant XCP master

(software) can connect to

iSYSTEM‘s winIDEA via this

protocol.

Major benefit is that em-

bedded systems develo-

pers and testers may use a

debugger instead of a bus

channel to connect to an

ECU to perform testing and

measurement. The applica-

tion code must not be in-

strumented as it is the case

using bus access. Normally

to measure via a bus an

XCP stack runs in the target

and some extra code has to

be added to the application

in order to perform the

measurement. During deve-

lopment such an XCP stack

normally doesn‘t exist on

the target. Some compa-

nies even avoid to extend

their application software

at all.

More

Information:

isystem.com/itag

More

Information:

isystem.com/

download/

winideaopen

See also page 9 — DAQ and XCP for Vector CANoe/CANape

See also page 1 —

Wireless Debugger and

page 5 — 3rd Party De-

bugger Support

In 1971 a first microcon-

troller (MCU) was intro-

duced. At that time Embed-

ded Software development

was done with very limited

tool support, mostly in As-

sembler, no PC. The first in-

circuit emulator connected

to a PC was brought to the

market in the early 80ties,

iSYSTEM did so in 1988.

Developing and manufac-

turing a software develop-

ment and test tool for em-

bedded microcontroller

application development, a

tool manufacturer has to

have a close relationship

w i t h s e m i c o n d u c t o r

vendors to be able to come

up with the right tools in

time and with the highest

possible integration. The

world of microcontrollers

has changed a lot since the

very beginning in terms of

complexity, number of

cores, speed, power con-

sumption, and variety. So

did the software develop-

ment tools. Emulation is

replaced by on-chip debug-

ging, a tool must be reu-

sable over several projects

and microcontroller archi-

tectures, more and more

test and measurement

functionality is built in, a

flexible integration of such

tools within the software

development and test pro-

cess is mandatory. Today

iSYSTEM development and

test tools do support more

than 50+ MCU families,

3000+ derivatives, from 8-

and 16- to 32-Bit. The

Windows and/or Eclipse

based development and

test environment (winIDEA/

testIDEA) is easy to learn

and use. The flexible in-

tegration and application of

iSYSTEM solutions within

the entire development

process is enabled by open

and public interfaces

(APIs).

iSYSTEM's fully software

configurable iC5000 and

iC6000 platform adapts to

a multi-functional analyzer,

development and test tool

for many different proces-

sors and controllers. An

optional I/O module adds

the capability to generate,

monitor and trace digital as

well as analog signals.

Since the very beginning

iSYSTEM Blue Box Techno-

logy was driven by a single

software called winIDEA

(before that it was called

dosIDEA). In the early times

of in-circuit-emulation most

of the development and

test functionality was done

in hardware. Today a vast

part is software.

M A R K E T S A N D T R E N D S

I S Y S T E M T O O L S F R O M 1 9 9 3 — T O D A Y

Page 4 B L U E P R I N T

„The world of microcontroller has changed a lot since the very beginning in terms of complexity, number of cores, speed, power consumption, and variety.“

„Since 1986 iSYSTEM provides Embedded Development Software Tools and Blue Box hardware technology to different markets“

This is the most growing

market since a while now.

Lots of embedded applica-

tions are already based on

this microcontroller archi-

tecture, more will follow.

Cyber-Physical Systems, a

new buzzword for embed-

ded systems, but an indica-

tion that shows already

today that lots of small and

mid-size embedded sys-

tems will be present on the

market in the future. Most

of them will be based on

Cortex.

A R M / C O R T E X M A R K E T

Page 5 B L U E P R I N T

Th e in t eg ra t i on o f

3rd party debuggers in

winIDEA is part of the iSYS-

TEM GOES SOFTWARE

strategy. As a result, we

expect iSYSTEM’s develop-

ment and test environment

winIDEA/testIDEA, which is

particularly popular in the

automotive industry at this

time, to become even more

popular around the world.

SEGGER J-LINK and

ST-LINK from STMicroelec-

tronics:

This is accomplished by

a free version of winIDEA

called winIDEA Open for

Cortex-M with integrated J-

Link and ST-Link support.

winIDEA Open has no code

size limitation, supports

only the GNU tool chain,

and is provided with no

support. Therefore it is

recommended to use

winIDEA Open for evaluati-

on and non-critical projects

only. Extensive technical

support as well as the use

of additional compilers is

available through an up-

grade to a regular winIDEA

version.

I S Y S T E M F O R 3 R D P A R T Y C O R T E X - M D E B U G G E R

iSYSTEM winIDEA/testIDEA

standard software distribu-

tion supports Renesas E1

Debugger for the RH850

family of MCUs. This inclu-

des standard debug functi-

onality, flash programming,

communication over JTAG

or LPD and compiler sup-

port for Greenhills and IAR.

If trace (recording of pro-

gram execution etc.) is

required, we recommend

an upgrade to the iC5000

blue box supporting On-

chip trace buffer as well as

SofTrace, Profiling and

Code Coverage analysis.

I S Y S T E M F O R R E N E S A S E 1 D E B U G G E R

More

Information:

isystem.com/

download/

winideaopen

iSYSTEM iC5000

supporting

RH850 on-chip

trace, SofTrace,

Profiling and

Code Coverage

(see also page 9

— Function and

Task Profiling via

Standard IO)

See page 3 — iSYSTEM Cortex-M

tools

Follow us on ARM Connected Community:

community.arm.com/community/arm-partner-

directory/partner-isystem

iSYSTEM testIDEA is an

application for embedded

software tests. It expands

iSYSTEM's debug and trace

tools for software develop-

ment with unit, integration

and system testing functio-

nality on object code level.

testIDEA is an interactive

editor for creating and run-

ning tests. It creates re-

ports with detailed informa-

tion about test execution

and results. An integration

with winIDEA is provided.

Test cases and test vectors

are executed on the real

customer hardware without

code instrumentation. The

major advantage of non-

instrumented tests is the

fast turn-around-times,

because the tests can run

without compilation, linking

and download. No test dri-

vers are needed and there-

fore no additional re-

sources are used on the

target system. Functions

like tracing, profiling and

code coverage analysis can

be integrated into the test

cases. Test cases can be

created without knowing

the isystem.test API.

testIDEA stores the test

cases in YAML format.

YAML is human friendly

data serialization standard.

Human friendliness is its

main advantage over XML.

The test specification files

can be easily edited with

any text editor and later

used either by scripts or

testIDEA. Tests created

with testIDEA can be

reused in scripts via isys-

tem.test API. Integration

with isystem.connect API

expands the operation area

of iSYSTEM test technology

from unit testing to integra-

tion and system testing.

API Information:

isystem.com/download/

winidea_testidea_apis/

eMOTE – "*E*mbedded

*Mo*del-based *Te*sting"

PNumber: KF2076903SS9

iSYSTEM AG, sepp.med

GmbH and the FZI

(Research Center for Infor-

mation Technology in Karls-

ruhe) cooperated to define

and enhance methods and

tools for testing embedded

software. The project titled

eMOTE was funded by the

BMWi (Federal Ministry of

Economics and Technology

in Germany) and lasted

October 2009 - October

2011. Main goal was to

adopt sepp.med’s model

based test procedures and

their test generation me-

thods to the specifics and

constraints of real-time

embedded sof twa re .

iSYSTEM’s debug solutions

were extended and

customized to optimally

support test execution in

real time. In particular follo-

wing aspects were covered

and/or solutions develo-

ped:

Coverage of existing and

currently evolving stan-

dards for embedded soft-

ware development and

test in different industry

sectors

Non-intrusive testing, in

particular without code

instrumentation

Test of real-time conditi-

ons and their description

in the model

Combination of test me-

thods with code coverage

analysis

Inclusion of data sources

(for external stimulation

of an embedded system)

in the test pattern and the

test itself

Integration in a model

based development pro-

cess

MoTTeM—Model-based non

-invasive Test and Trace-

analysis of Embedded Mul-

ticore software

Duration: January 2013 -

December 2014, PNumber:

KF2326902BZ2

MoTTeM evaluates specific

requirements regarding

test-methodology, develop-

ment-tools and tools for

testing of embedded soft-

ware running on multicore

microcontroller based hard-

ware. Together with the FZI

(Research Center for Infor-

mation Technology in Karls-

ruhe) and HighTec EDV

Systeme GmbH, iSYSTEM

focuses on todays and fu-

ture challenges specific for

multicore embedded appli-

cations development and

testing.

T E S T I D E A S T A N D A R D / P R O F E S S I O N A L

Z I M P R O J E C T S @ I S Y S T E M

Page 6 B L U E P R I N T

More

Information:

isystem.com/

download/

brochures

See page 7 — fitDEA and

page 8 — Systematic Test

Case Generation with CTE

XL Professional

See page 11 — Multi-core,

timing behavior, efficiency,

robustness, simulation, on-

target verification ...

For safety-relevant applica-

tions, tool manufacturers

have to subject their soft-

ware tools to rigorous test-

ing. Chapter 8-11 of the

ISO 26262 standard, a

version of IEC 61508 spe-

cifically “adapted” to auto-

motive, is dedicated to con-

fidence in the use of soft-

ware tools. This standard

has a specific impact not

only on vehicle manufactur-

ers and their suppliers but

also on the development

and test processes of tool

manufacturers and thus

the development process

of the actual software tool.

iSYSTEM internalizes test

automation with fitIDEA, a

test tool suite that facili-

tates fully automatic execu-

tion of defined tests in em-

bedded systems. fitIDEA is

an automated test tool that

was initially developed for

iSYSTEM internal purposes.

It uses a generic API

(application programming

interface, isystem.connect)

of the iSYSTEM develop-

ment environment named

winIDEA/testIDEA and the

public scripting language

Python. As a tool manufac-

turer iSYSTEM faces almost

the same challenges as

their customers: Lots of

different hardware variants,

historically grown code

base plus legacy code, and

extended functionality ac-

cording to higher require-

ments of customers, in-

crease the complexity of

development and test tools

as well and makes it evi-

dent to introduce test auto-

mation. Interestingly, func-

tional safety standards

more and more incorporate

the qualifica-

tion of soft-

ware tools.

This is of

p a r t i c u l a r

interest be-

cause the

risk of using

s o f t w a r e

tools in re-

spect to specific require-

ments and “use cases” has

to be considered in prepa-

ration of a development.

Software tool manufactur-

ers are not excluded either,

i.e. these manufacturers

are expected to implement

suitable improvements and

extensions in their own

development and test pro-

cesses. iSYSTEM has al-

ready aligned their process-

es to this trend and inter-

nalizes an agile software

development process with

test automation transpar-

ency.

What challenges to devel-

opment and test engineers

does the tool suite fitIDEA

overcome?

As a start, fitIDEA is the

internal implementation of

iSYSTEM’s software devel-

opment and test process.

Our focus is mainly on agile

development and an inter-

nalized process of continu-

ous integration. We have

therefore approached the

issue test automation sys-

tematically. fitIDEA is more-

over an environment to

prove the correctness of

the iSYSTEM tool function-

ality according to certain

use cases, mainly customer

-specific ones. This is a

requirement of several

functional safety stand-

ards.

How can a test technique

master the complexity of

modern software applica-

tions and the variety of

devices?

The answer is fitIDEA and

internalized test automa-

tion in an agile software

development environment

– in other words, automa-

tion and sophisticated tech-

niques. And an occasional

glimpse at the aviation

sector with its extensive

experience in model/

requirements based test-

ing.

There are diverse ap-

proaches and philosophies

regarding software testing.

Which one do you think is

most interesting?

In a way, they are all inter-

esting. However, the meth-

odology and the company

have to match up. Agile

software development and

the related testing philoso-

phy are quite fascinating.

Especially because many

habitual processes and

patterns are breaking up,

and any type of software

challenge is overcome with

both determination and

professionalism.

FITIDEA — HOW iSYSTEM DOES PERFORM TESTING

Q & A A B O U T T E S T A U T O M A T I O N

Page 7 B L U E P R I N T

“In a way, all test

methods are

interesting. However,

the methodology and

the company have to

match up.”

Tool test bench for

automated regression tests

executed on different

hardware platforms and

target systems. The

iSYSTEM test benches also

include customer-specific

systems

More Information:

isystem.com/

download/brochures

iSYSTEM and Berner &

Mattner respond to the

demand for consistent de-

velopment tools and auto-

mated test tools required

especially by the automo-

tive industry. Nowadays,

many companies use a

“line-up of tools” in the

various development stag-

es of an “embedded sys-

tem”. There are no smooth

transitions and automa-

tisms between the individu-

al stages and the respec-

tive tools. Consequently,

the know-how achieved at

the beginning of the pro-

cess often goes missing,

and numerous steps have

to be repeated over and

over again. There is a high-

er demand for software

testing particularly at the

early stages of the develop-

ment process, calling for

techniques and automa-

tisms for the systematic

generation of test cases

and their execution in a

real environment, in other

words, on the target hard-

ware. Up to now, the two

partners have covered dif-

ferent stages of the devel-

opment and test process.

iSYSTEM focuses on soft-

ware development for the

implementation/integration

of software and hardware,

especially software testing

at the development engi-

neer’s workplace; Berner &

Mattner specializes in sys-

tems engineering, develop-

ment and testing of high-

performance electronic and

mechanical systems and,

in this context, especially

consulting, conceptual de-

sign, software and system

development, setup and

operation of entire test and

integration systems.

S Y S T E M A T I C S O F T W A R E T E S T C A S E G E N E R A T I O N

Page 8

CTE XL Professional –

Graphical Editor for

Classification Trees

from Berner & Mattner

integrates with iSYSTEM

winIDEA/testIDEA.

The classification tree

method was developed

in the 1990s, followed

by the classification

tree editor. The editor is

context-sensitive and a

powerful tool for the

systematic specification

and implementation of

test cases.

Trace is a functionality of

an on-chip debugger to

record program execution

during runtime giving each

recorded event a time-

stamp. This is how a devel-

oper and tester may ana-

lyze software and its inter-

action with the real world

as well as to reproduce

error scenarios. Trace is a

prerequisite of additional

analysis on the final hard-

ware such as performance

measurements (function

profiling) and code cover-

age. The latter ensures that

their is no dead code (no

non-tested code) left in the

final and shipped applica-

tion. Tool manufacturers

like iSYSTEM implement

trace using dedicated pins

and on-chip trigger logic

provided on the silicon, and

implemented by the semi-

conductor vendor. However,

pins and on-chip trigger

logic costs money, so more

and more silicon doesn't

implement trace capabili-

ties. iSYSTEM did imple-

ment a technical and ge-

neric solution to rebuild

trace pins where no such

trace ports are available.

As said before, some CPUs

do not provide OCT ports

and so no trace is possible

there. To alleviate this limi-

tation, a free port on the

emulated CPU can be used

to rebuild the trace port. If

the CPU has no free ports,

a bigger package device

can be used either in a

redesigned target system

or on an emulation adapter.

The port must be manipu-

lated by the target applica-

tion – the code must be

instrumented on appropri-

ate positions. iSYSTEM

provides instrumentation

macros for this purpose.

Currently the following

MCUs are supported:

Renesas V850/FX4L

Renesas RH850/F1L.

It is possible to build such

trace port adaptors for

Cortex-M0,

Cortex-M0+

Freescale Qorivva 560xP

Or others

F U N C T I O N / T A S K P R O F I L I N G V I A S T A N D A R D I O

B L U E P R I N T

Target Device replaced by

Adaptor with high pin-count

Device.

=> adds an I/O Port not

used by Application

=> used as “User Trace

Port”

User Trace Port Signals

routed to Debug Connector

iC5000 records User Trace

Messages

iC5000 adds Time-Stamp to

each Message

More

Information:

isystem.com/

downloads/

winIDEA/help/

Contents/Analyzer/

Trace concepts/User

trace ports

The iC6000 Blue Box is

iSYSTEM’s new generation

of embedded on-chip de-

bug/analyzer, real-time test

and measurement tool

platform. It is a combina-

tion of hardware and soft-

ware accessing all kind of

debug interfaces including

new high-speed interfaces

such as AURORA and oth-

ers. iC6000 ensures that a

big amount of data can be

collected, analyzed and

visualized in real-time. To

capture serial streams

whose speeds exceed

6Gbps, the latest genera-

tion of Xilinx FPGAs is used.

In addition to that the hard-

ware platform does sup-

port:

Trace port 8Rx and 4Tx

Aurora Channels up to

6.25 Gbps

Trace port speed up to

500MHz (parallel Nex-

us5001 MDO or ETM)

Trace memory 8GB

Connectivity USB 3.0

I/O Module: Digital and

analog inputs/outputs for

measurement and stimu-

lation/triggering

I C 6 0 0 0 W I T H A U R O R A S U P P O R T

Page 9 B L U E P R I N T

The XCP protocol provides

for two different memory

access modes. The so-

called polling mode facili-

tates access to any ECU

memory address, fully

asynchronous with the ap-

plication logic. To this end,

an XCP master like

CANoe.XCP or CANape

transmits the specific ad-

dress to the XCP slave on

the ECU and, in return,

receives the data at this

address. DAQ (Data AcQui-

sition) is the second access

mode. Here, the XCP slave

streams configured data

packages with the current

values to the XCP master,

based on the timing de-

fined by the XCP slave. This

way, access can run syn-

chronously with the appli-

cation on the ECU. In con-

trast to polling, DAQ events

can also transmit the inter-

nal timestamp of the XCP

slave. The iSYSTEM XCP

protocol slave and espe-

cially DAQ are now directly

implemented in the blue

box and are independent of

the PC used. Multiple

memory areas can be read

and written simultaneously,

and different sampling

rates can be configured,

e.g. at every change of a

memory area or at intervals

of 1 ms, 10 ms, 100 ms

and 1 s. So far, the polling

mechanism was only imple-

mented in the host soft-

ware winIDEA by iSYSTEM.

With the implementation in

the FPGA of the debugger,

it has now been virtually

realized at real-time. More-

over, the debugger assigns

an explicit timestamp to

the DAQ event and passes

it on to the XCP master for

analysis. Thus, the XCP

master can correlate the

data with other measure-

ment data.

D A Q A N D X C P I M P L E M E N T A T I O N

More

Information:

isystem.com/

downloads/

winIDEA/help/

Contents/

Integration with 3rd

party tools/Vector

CANoe

Besides the bus

interface, paral le l

access via h igh-

performance debug

i n t e r f a c e s i s

a v a i l a b l e d u r i n g

development

E C U a c c e s s i s

p o s s i b l e w i t h o u t

additional software

(XCP dr iver) . No

additional resources

are required, and the

real-time behavior is

not affected.

T h e d e b u g g e r

t i m e s t a m p i s

synchronous with the

bus t raf f ic . This

allows for an analysis

o f i n te r n a l EC U

values that is time-

synchronous with bus

communication.

See also page 3 — DAQ

and XCP for NI Tools

iSYSTEM News and Tech-

nical Blog — Register today

to get regular updates au-

tomatically.

In 2009 iSYSTEM did lau-

nch into blogging, setting

up the first dedicated soci-

al media press office

(SMPO) for the embedded

community. The blog provi-

des an interactive platform

for the international em-

bedded community to get

the most out of develop-

ment and testing. Next to

showcasing high quality,

modular and easy to use

products and services, iSY-

STEM is committed to talk

about technological chal-

lenges and involve partners,

customers and developers

in a lively discussion about

issues and themes that

drive the embedded indust-

ry.

The blog is a testament of

iSYSTEM's vision to easily

enable developers and

testers to use embedded

development and test tools

within the complete develo-

pment process. It is also

evidence of iSYSTEM’s

mission to develop and

produce development and

test tools for real-time em-

bedded applications.

I S Y S T E M B L O G E M B E D D E D . T Y P E P A D . C O M

Page 10 B L U E P R I N T

iSYSTEM YouTube

Channel

Page 11 B L U E P R I N T

Follow iSYSTEM to get and comment news on a regular basis.

T W I T T E R : T W I T T E R . C O M / I S Y S T E M A G

ZELOS3 - Multi-Core Proces-

sors with Technologies for

Safe Scheduling Simulation

iSYSTEM AG and the Uni-

versity Of Applied Sciences

Regensburg with its Labor-

atory for Safe and Secure

Systems (LaS3) cooperate

to define and enhance

methods and tools that aim

to realize safe and reliable

multi-core based cyber-

physical systems according

to functional safety stand-

ards such as ISO 26262.

The use of multi-core pro-

cessors comes with a lot of

challenges to master tim-

ing behavior, resource effi-

ciency and reliability of a

cyber-physical system. This

requires the use of appro-

priate scheduling algo-

rithms. Within ZELOS3 the

University and LaS3 will

analyze these multi-core

scheduling algorithms in

terms of robustness by

extending those with fault

tolerance mechanisms. In

order to analyze the timing

behavior of a cyber-physical

system, simulation of such

systems is becoming an

important factor. Such a

simulation is based on ab-

stract system modelling.

The manually creation of a

model is very time consum-

ing and error-prone. Zelos3

will develop methods and

tooling to automatically

reconstruct such models

based on the recorded pro-

gram execution in real-time

(trace record via iSYSTEM’s

debugger software and

hardware). In addition to

that as well as to prove the

robustness of multi-core

scheduling algorithms

ZELOS3 will implement fault

injection via simulation. In

a second step the simula-

tion results will be verified

and optimized by fault in-

jection on a real target

hardware without instru-

menting the software run-

ning on the target hard-

ware using iSYSTEM's IDE

and debugger. On a tool

and sc ienti f ic level

iSYSTEM, LaS3 and the

University of Applied Sci-

ences Regensburg will work

closely together with the

company Timing-Architects

(timing-architects.com). TA

offers comprehensive solu-

tions for the evaluation and

optimization of the timing,

performance, and reliability

properties of embedded

multi-core and many-core

systems based on simula-

tion.

More Info: October 2013 -

September 2015, Project

Number: KF2326903BZ3

Industry Tool Partner:

Z I M P R O J E C T Z E L O S 3

“In order to

analyze the

timing behavior

of a cyber-

physical system,

simulation of

such systems is

becoming an

important factor”

“We are continually

impressed with how

much energy and

passion our teams

tackle the

challenges of the

iSYSTEM prospects

and customers

world-wide”

iSYSTEM AG für

Informatiksysteme

Carl-Zeiss-Str. 1

85247 Schwabhausen

Germany

Phone: +49(8138)6971-0

Fax: +49(8138)6971-46

E-mail: info@isystem.com

Web: www.isystem.com

Commercial register of the

local courts (Amtsgericht)

München HRB 148751

VAT identification number:

DE128231221

Board of Management:

Erol Simsek, Werner Fischer,

Martin Gröstenberger

Responsible for the content

§ 10 Absatz 3 MDStV:

Erol Simsek

B L U E P R I N T

iSYSTEM Germany:

Support, Systems

Engineering, Logistics,

Sales, Marketing

R&D and Manufacturing Slovenia

T H E L A S T P A G E — A B O U T I S Y S T E M

iSYSTEM is a privately held company headquartered in Germany, close to Munich. Since its

foundation in 1986, iSYSTEM is an independent manufacturer and provider of embedded

software debugging and test tools. Beside standard products iSYSTEM offers development

and production services for custom designs, projects and OEM products.

iSYSTEM’s Blue Box Technology stands for fast and easy microcontroller access via any

kind of microcontroller debug interface. No matter whether one is developing, debugging or

testing embedded software on a real target system. iSYSTEM’s open and integrated Debug

and Test Software enables engineers to drive a Blue Box and the corresponding develop-

ment.

iSYSTEM maintains long standing and close relationships with all major semiconductor,

operating system and compiler companies worldwide. This guarantees quick tool availabili-

ty and the highest level of integration.

iSYSTEM is a ISO9001:2008 certified company.