Skip to main content

Infineon TRAVEO™ T2G AUTOSAR software

The TRAVEO™ AUTOSAR software was introduced to the market in 2014 and has since undergone numerous improvements and upgrades. For the TRAVEO™ T2G, a mature, feature-rich driver layer is now available, which is developed, maintained, and supported by in-house TRAVEO™ experts. The TRAVEO™ T2G AUTOSAR software was developed in compliance with Automotive SPICE and ISO26262 standards, making it suitable for applications with safety targets up to ASIL-B. Additionally, the delivery package includes the EB tresos configuration tool, which comes with a node-locked license.

The AUTOSAR software portfolio includes:

AUTOSAR MCAL (ASR 4.2.2)​

TRAVEO™ T2G AUTOSAR drivers enable a wealth of smart hardware features, making the TRAVEO™ T2G series highly attractive within the AUTOSAR workflow. The microcontroller abstraction layer (MCAL) is the lowest software layer of the Basic software. It contains drivers that are software modules with direct access to the µC internal peripherals and memory-mapped µC external devices. In addition to the features defined by AUTOSAR, the TRAVEO™ T2G MCAL supports safety functions, trigger connections between internal peripherals, "Smart I/O" functions, and many more TRAVEO™-specific design ideas.

Software partners with experience in integrating the TRAVEO™ T2G MCAL include Elektrobit, Etas, and Vector Informatik.

For details about the TRAVEO™ T2G AUTOSAR MCAL, see the following TRAVEO™ T2G user guides:

AUTOSAR self-test libraries​

Available separately to the MCAL, the self-test libraries help to fulfill safety goals by giving a high diagnostic coverage over large parts of the chip area. Self-Test Libraries are defined for CORE, FLASH and RAM.

"foreground mode" and "background mode" are available

  • In "Foreground Mode" the complete test is executed at once, for example at start up.
  • In "Background Mode" execution is distributed over several times slots intermittently with other task

For details about the TRAVEO™ T2G AUTOSAR Self-Test libraries, please refer to the following TRAVEOTM T2G user guides:

AUTOSAR flash EEPROM emulation (FEE)​

Included in the FEE delivery, the FEE Interfaces to TRAVEO™ T2G MCAL FLS abstracts from the physical Flash's segmentation and addressing scheme and provides a virtual addressing and segmentation scheme. It utilizes virtual page sizes of 4 bytes, which allows for a virtually unlimited number of erase cycles (calculation tool included). The algorithm is robust against power down and has a compact memory footprint.

For details on the TRAVEO™ T2G AUTOSAR FLASH EEPROM Emulation (FEE), see the following user guide:

AUTOSAR MCAL multi-core extension​

This extension adds "Type II" multi-core support (as defined in ASR 4.4) to defined MCAL drivers, where each CPU core can run an instance of the driver.

Peripheral channels and their data are individually allocable to cores but cannot be shared among cores.

The following drivers in the MCAL Multi-Core Extension feature Type II multi-core support:

The MCAL Multi-Core Extension in addition offers some Type III multi-core support:

For this multicore type, the driver has core-independent instances with globally available hardware. This type is referred as “Multicore Type III”. Multicore Type III has the following characteristics:

  • The code of the driver is shared among all cores
    • A common binary is used for all cores
    • A configuration is common for all cores
  • Each core runs an instance of the driver
  • Peripheral channels are globally available for all cores

This Type III multi-core support is available for:

  • DIO 3.0 driver - all pins are accessible from all cores without synchronization.

On most above listed "Type II" modules, some APIs can be globally accessed by any M7 core, offering limited Type III multi-core support.

If multicore Type III is required, the section including the data related to the read-only API or atomic write API must be allocated to the memory, and can be read from any M7 core

AUTOSAR complex device drivers for code flash (main flash)​

  • Code Flash Driver supports write and erase of main flash
  • Operation can be requested from all CPU Cores (CM4, CM7, CM0+)
  • "Dual Bank" support allows to execute the driver form Flash Configuration by EB tresos

For details on the TRAVEO T2G AUTOSAR Complex Device Driver for Code Flash please refer to the following User Guide.

  • Code Flash Driver

TRAVEO™ T2G AUTOSAR complex device driver for I2C​

The I2C driver is a complex driver, which enables you to support I2C communication on special output pins of the MCU. It supports the T2G serial communication block (SCB)

  • Supports master- and slave mode
  • Mode Change at run-time supported
  • Configurable with EB-Tresos Studio as AUTOSAR Complex Device Driver
  • A single I2C driver supports multiple channels
  • Simultaneous communication using multiple channels is possible
  • Each channel can be configured to run in poll or interrupt mode
  • No interrupt between Address field and Data field
  • User can select the I2C transaction to "Normal sequence" or "Repeated Start"
  • FIFO mode is supported (by using interrupts, by polling and by using DMA and interrupts)

For details on the TRAVEO™ T2G AUTOSAR Complex Device Driver for I2C, please refer to the following user guide:

TRAVEO™ T2G AUTOSAR complex device driver for UART​

It supports the TRAVEOTM T2G serial communication block (SCB)

  • Full Duplex Support
  • Frame Size 4 bit-9 bit
  • Operation Modes: Synchronous transmit, Asynchronous transmit, Automatic receive, Synchronous receive, Asynchronous receive

For details on the TRAVEO™ T2G AUTOSAR Complex Device Driver for UART , please refer to the following user guide

© 2024 Infineon Technologies AGOpenDocsPlease read the sections "Important notice" and "Warnings" at the end of this document

Last updated on