ACT - AURIX™ Configuration Tool ATV MC July 2015

Слайд 1 ACT – AURIX™ Configuration Tool
ATV MC
July 2015

Слайд 2ACT – Intention
The ACT was developed to:
Simplify pin mapping
Provides an overview

over used/configured pins
Shows possible module connections and signal paths to the single pins/balls
Support PCB-design
Provide an interface to easily configure the iLLD
Have a single core OS

Page

for internal use only

Слайд 3AURIX™ Configuration Tool – ACT
ACT will be provided as a plugin

for Tasking VX Toolset for Tricore from Altium

Free of charge!

Page

for internal use only

Слайд 4Pin-Mapper

Слайд 5New Pin-Mapper project

Page
for internal use only
Copyright ©

Слайд 6Select TASKING Pin Mapper Project

Page
for internal use

only

Слайд 7Give the project a name

Page
for internal use

only

Слайд 8Select the derivate and the package
Page
for internal

use only

Слайд 9Open the pin-mapper
Select the project in the project explorer on the

left side
Right click on the project

Page

for internal use only

Слайд 10Overview
Ports Configuraiton

Package and Overview

Page

for internal use only

Слайд 11If package is not shown
Open the right perspective

Page

for internal use only

Слайд 12Package Overview – Different States
Can display:
Module names
Symbolic names
Connection status
Pad classes
Power domains
Reset

state

Page

for internal use only

Слайд 13Configuration
Easily assign symbolic names to pins
Easily mark connections between modules and

pins as Use-tags

Page

for internal use only

Слайд 14Configuration

Select the pin you want to use for the signal
If two

pins are selected for an uniqe signal, a warning is displayed

Page

for internal use only

Слайд 15After configuration
Generate .c and .h files if needed

And select the folder

in the project where the files should be

Page

for internal use only

Слайд 16Config-file itself
The configuration is stored in xml-like-format

Can be used for further

processing

Next time open the file with Pin Configuration Editor again

Page

for internal use only

Слайд 17ACT – Pin Mapper
Shows all configured pins
with possible errors

and
warnings
Can display:
Module names
Symbolic names
Connection status
Pad classes
Power domains
Reset state

Page

for internal use only

Слайд 18ACT – Pin Mapper
Connection Status
Pad Class
Power Domain
Reset State
Page

for internal use only

Слайд 19ACT – Pin Mapper
After the configuration the target project for the

setting has to be chosen
The configuration is stored in
xml-like-format

Page

for internal use only

Слайд 20ACT – Driver Configuration

Слайд 21ACT – Driver Configuration
iLLD come from tests and application used by

several teams at infineon ATV
iLLD are basic function low level drivers for use and demonstration for almost every module
All drivers have the same code styling -> common look and feel
Already tested in pre-silicone with a virtual prototype or in RTL-simulations
Each derivate (TC2YX) has its own set of drivers
No dependency between the peripheral drivers
The strict iLLD coding guidelines allow layering of drivers for multi-dimensional system scenarios
Available in the beta ACT-release (estimated Q2/15)

Page

for internal use only

Слайд 22ACT – Driver Configuration
The iLLD consists of unifunctional and multifunctional drivers

Page

for internal use only

Слайд 23ACT – Driver Configuration
Multifunctional drivers: Add a new peripheral and choose

the iLLD for this module
Right click in the
window and add a
new service or
driver
Then you can choose
the iLLD for the
module

Page

for internal use only

Слайд 24Select the iLLD from a module and configure your parameters
ACT –

Driver Configuration

Page

for internal use only

Слайд 25ACT – Generated Struct
E. g., for QSPI Master, the generated init-struct

is

Page

for internal use only

Слайд 26ACT – OS

Слайд 27OS – With Respect To The TASKING OS
3 stage implementation:
Configurator
Generates an

oil-file

OIL compiler
Generates c- and h-files

Normal compiler+linker
Generates the hex-/elf-file

LLD

Page

for internal use only

Слайд 28OS – Create the Config
Select File ? New

And create the oil-file
Page

for internal use only

Слайд 29OS – OIL-Configurator

Task-config

Alarm-config

OS-routines

Event-config

Resource-config

Message-config
Page
for internal use only
Copyright ©

Слайд 30OS – Basic Configuration

Task-config

Used hook-routines

OS-timer setup
Page
for internal

use only

Слайд 31OS – Alarm Configuration

Period

Base counter
Page
for internal use

only

Слайд 32OS – Task Configuration

Resource assignment

Event assignment

Preemptiv/non preemptive scheduling

Message assignment
Page

for internal use only

ACT - AURIX™ Configuration Tool ATV MC July 2015 презентация

Содержание

Слайд 1 ACT – AURIX™ Configuration Tool
ATV MC
July 2015

Слайд 2ACT – Intention
The ACT was developed to:
Simplify pin mapping
Provides an overview

Слайд 3AURIX™ Configuration Tool – ACT
ACT will be provided as a plugin

Слайд 4Pin-Mapper

Слайд 5New Pin-Mapper project

Page
for internal use only
Copyright ©

Слайд 6Select TASKING Pin Mapper Project

Page
for internal use

Слайд 7Give the project a name

Page
for internal use

Слайд 8Select the derivate and the package
Page
for internal

Слайд 9Open the pin-mapper
Select the project in the project explorer on the

Слайд 10Overview
Ports Configuraiton

Слайд 11If package is not shown
Open the right perspective

Page

Слайд 12Package Overview – Different States
Can display:
Module names
Symbolic names
Connection status
Pad classes
Power domains
Reset

Слайд 13Configuration
Easily assign symbolic names to pins
Easily mark connections between modules and

Слайд 14Configuration

Select the pin you want to use for the signal
If two

Слайд 15After configuration
Generate .c and .h files if needed

And select the folder

Слайд 16Config-file itself
The configuration is stored in xml-like-format

Can be used for further

Слайд 17ACT – Pin Mapper
Shows all configured pins
with possible errors

Слайд 18ACT – Pin Mapper
Connection Status
Pad Class
Power Domain
Reset State
Page

Слайд 19ACT – Pin Mapper
After the configuration the target project for the

Слайд 20ACT – Driver Configuration

Слайд 21ACT – Driver Configuration
iLLD come from tests and application used by

Слайд 22ACT – Driver Configuration
The iLLD consists of unifunctional and multifunctional drivers

Page

Слайд 23ACT – Driver Configuration
Multifunctional drivers: Add a new peripheral and choose

Слайд 24Select the iLLD from a module and configure your parameters
ACT –

Слайд 25ACT – Generated Struct
E. g., for QSPI Master, the generated init-struct

Слайд 26ACT – OS

Слайд 27OS – With Respect To The TASKING OS
3 stage implementation:
Configurator
Generates an

Слайд 28OS – Create the Config
Select File ? New

And create the oil-file
Page

Слайд 29OS – OIL-Configurator

Task-config

Alarm-config

OS-routines

Event-config

Resource-config

Message-config
Page
for internal use only
Copyright ©

Слайд 30OS – Basic Configuration

Task-config

Used hook-routines

OS-timer setup
Page
for internal

Слайд 31OS – Alarm Configuration

Period

Base counter
Page
for internal use

Слайд 32OS – Task Configuration

Resource assignment

Event assignment

Preemptiv/non preemptive scheduling

Message assignment
Page

Слайд 33

Обратная связь

Что такое ThePresentation.ru?

ACT - AURIX™ Configuration Tool ATV MC July 2015 презентация

Содержание

Слайд 1 ACT – AURIX™ Configuration ToolATV MCJuly 2015

Слайд 2ACT – IntentionThe ACT was developed to:Simplify pin mappingProvides an overview

Слайд 3AURIX™ Configuration Tool – ACTACT will be provided as a plugin

Слайд 4Pin-Mapper

Слайд 5New Pin-Mapper projectPage for internal use onlyCopyright ©

Слайд 6Select TASKING Pin Mapper ProjectPage for internal use

Слайд 7Give the project a namePage for internal use

Слайд 8Select the derivate and the packagePage for internal

Слайд 9Open the pin-mapperSelect the project in the project explorer on the

Слайд 10OverviewPorts Configuraiton

Слайд 11If package is not shownOpen the right perspectivePage

Слайд 12Package Overview – Different StatesCan display:Module namesSymbolic namesConnection statusPad classesPower domainsReset

Слайд 13ConfigurationEasily assign symbolic names to pinsEasily mark connections between modules and

Слайд 14ConfigurationSelect the pin you want to use for the signalIf two

Слайд 15After configurationGenerate .c and .h files if neededAnd select the folder

Слайд 16Config-file itselfThe configuration is stored in xml-like-formatCan be used for further

Слайд 17ACT – Pin MapperShows all configured pins with possible errors

Слайд 18ACT – Pin MapperConnection StatusPad ClassPower DomainReset StatePage

Слайд 19ACT – Pin MapperAfter the configuration the target project for the

Слайд 20ACT – Driver Configuration

Слайд 21ACT – Driver ConfigurationiLLD come from tests and application used by

Слайд 22ACT – Driver ConfigurationThe iLLD consists of unifunctional and multifunctional drivers Page

Слайд 23ACT – Driver ConfigurationMultifunctional drivers: Add a new peripheral and choose

Слайд 24Select the iLLD from a module and configure your parametersACT –

Слайд 25ACT – Generated StructE. g., for QSPI Master, the generated init-struct

Слайд 26ACT – OS

Слайд 27OS – With Respect To The TASKING OS3 stage implementation:ConfiguratorGenerates an

Слайд 28OS – Create the ConfigSelect File ? NewAnd create the oil-filePage

Слайд 29OS – OIL-ConfiguratorTask-configAlarm-configOS-routinesEvent-configResource-configMessage-configPage for internal use onlyCopyright ©

Слайд 30OS – Basic ConfigurationTask-configUsed hook-routinesOS-timer setupPage for internal

Слайд 31OS – Alarm ConfigurationPeriodBase counterPage for internal use

Слайд 32OS – Task ConfigurationResource assignmentEvent assignmentPreemptiv/non preemptive schedulingMessage assignmentPage

Слайд 33

Похожие презентации

Обратная связь

Что такое ThePresentation.ru?

Слайд 1 ACT – AURIX™ Configuration Tool
ATV MC
July 2015

Слайд 2ACT – Intention
The ACT was developed to:
Simplify pin mapping
Provides an overview

Слайд 3AURIX™ Configuration Tool – ACT
ACT will be provided as a plugin

Слайд 5New Pin-Mapper project

Page
for internal use only
Copyright ©

Слайд 6Select TASKING Pin Mapper Project

Page
for internal use

Слайд 7Give the project a name

Page
for internal use

Слайд 8Select the derivate and the package
Page
for internal

Слайд 9Open the pin-mapper
Select the project in the project explorer on the

Слайд 10Overview
Ports Configuraiton

Слайд 11If package is not shown
Open the right perspective

Page

Слайд 12Package Overview – Different States
Can display:
Module names
Symbolic names
Connection status
Pad classes
Power domains
Reset

Слайд 13Configuration
Easily assign symbolic names to pins
Easily mark connections between modules and

Слайд 14Configuration

Select the pin you want to use for the signal
If two

Слайд 15After configuration
Generate .c and .h files if needed

And select the folder

Слайд 16Config-file itself
The configuration is stored in xml-like-format

Can be used for further

Слайд 17ACT – Pin Mapper
Shows all configured pins
with possible errors

Слайд 18ACT – Pin Mapper
Connection Status
Pad Class
Power Domain
Reset State
Page

Слайд 19ACT – Pin Mapper
After the configuration the target project for the

Слайд 21ACT – Driver Configuration
iLLD come from tests and application used by

Слайд 22ACT – Driver Configuration
The iLLD consists of unifunctional and multifunctional drivers

Page

Слайд 23ACT – Driver Configuration
Multifunctional drivers: Add a new peripheral and choose

Слайд 24Select the iLLD from a module and configure your parameters
ACT –

Слайд 25ACT – Generated Struct
E. g., for QSPI Master, the generated init-struct

Слайд 27OS – With Respect To The TASKING OS
3 stage implementation:
Configurator
Generates an

Слайд 28OS – Create the Config
Select File ? New

And create the oil-file
Page

Слайд 29OS – OIL-Configurator

Task-config

Alarm-config

OS-routines

Event-config

Resource-config

Message-config
Page
for internal use only
Copyright ©

Слайд 30OS – Basic Configuration

Task-config

Used hook-routines

OS-timer setup
Page
for internal

Слайд 31OS – Alarm Configuration

Period

Base counter
Page
for internal use

Слайд 32OS – Task Configuration

Resource assignment

Event assignment

Preemptiv/non preemptive scheduling

Message assignment
Page