TRAVEO™ T2G is Infineon's Arm® Cortex®-M automotive MCU family for body control and instrument clusters. Every part is programmed over SWD; what needs most care in production is the eFuse and the life cycle, because those steps cannot be undone.

TRAVEO™ T2G is Infineon’s family of 32-bit automotive microcontrollers. According to Infineon, the CYT2B series targets body control, with an Arm® Cortex®-M4F as the main core and a separate Cortex®-M0+ for peripheral and security processing; CYT3BB and CYT4BB use one or two Cortex®-M7 cores; CYT4BF uses two Cortex®-M7 cores. In every series the Cortex®-M0+ runs a secure, uninterruptible boot.

TRAVEO™ T2G in the device list

As of November 2026 the device list has 385 TRAVEO™ T2G entries in 12 families: CYT2B6x (24), CYT2B7x (62), CYT2B9x (64), CYT2BLx (40), CYT3BBx (21), CYT4BBx (21), CYT4BFx (44), CYT6BJx (4), CYT2CL (6), CYT3DL (51), CYT4DN (32) and CYT4EN (16).

Programmer Entries supported Protocol
FlashRunner 2.0 / 2.0 HS / 2.0 NXG 385 (332 full ordering codes available now; 53 base part numbers with the algorithm delivered within 20 days of order) SWD
WriteNow! 53 (base part numbers, such as CYT2B75C) SWD

The two manufacturers list the parts differently: SMH by full ordering code (CYT2B74BAE, for example), Algocraft by base part number. To look a part up, type the first characters of its ordering code, for example search for CYT4BF.

Memory regions to program

FlashRunner’s data lists these regions for TRAVEO™ T2G:

  • FLASH (code flash): about 1 MB on CYT2B7x, about 8 MB on CYT4BFx and about 16 MB on CYT6BJx.
  • WFLASH (work flash): 96 KB to 512 KB. Infineon notes that work flash withstands far more erase cycles than code flash, so it suits data that is updated often.
  • SFLASH (supervisory flash): 32 KB.
  • FUSES (eFuse): 1 KB.
  • METADATA and CHECKSUM: additional regions listed in the data.

Where production goes wrong

eFuse and life cycle. According to Infineon, every device has 1,024 bits of OTP eFuse that hold a unique identifier and control the device’s life-cycle stage and security state; 192 of the bits are left for the user. A blown eFuse cannot be restored, so the life cycle can only move forward. At start-up the boot ROM applies access restrictions to the debug access port (DAP) from the eFuse and supervisory flash content, and in the SECURE stage it also authenticates FlashBoot. In practice:

  • Write eFuses or change the life cycle on the line only when the project really requires it, and validate the whole sequence on samples first.
  • Before writing protection settings into SFLASH, check whether later steps (test, rework) still need debug access.
  • To write a serial number or key per board, use the programmer’s dynamic data feature.

Treat code flash and work flash separately. The two regions have different sector structures, so set the erase and programming ranges for each in the project to avoid erasing data already held in work flash.

Line integration

SWD needs only a few signals, which suits multi-channel parallel programming. FlashRunner 2.0 (4 to 16 channels, extendable to 32), 2.0 HS (up to 32 channels), 2.0 NXG (1 to 4 channels) and WriteNow! (1 to 8 sites) all fit in the fixture, connect to ATE or ICT through a control interface or LAN, and report a result per channel. FlashRunner can encrypt firmware and dynamic data and limit the number of boards that may be programmed, which helps where the firmware itself needs protecting.

Questions and answers

Why do some entries in a family show “20 days”? Those are the base part numbers Algocraft lists. Except for CYT6BJ8D and CYT6BJCD, the matching full ordering codes (CYT2B75CAE for CYT2B75C, for example) are available now on FlashRunner, so look up the full ordering code on your board.

Is TRAVEO™ T1G (S6J3) supported too? The device list has about 500 further Traveo T1G (S6J3) entries; search for S6J3 to see them.

Can the unique ID in the eFuse be read for traceability? Where the device allows it, FlashRunner can read the unique ID and return it to the host. For your specific TRAVEO™ T2G part, check the implementation with gree-tech.