Infineon TC3xx
The Infineon TC3xx family is the 2nd generation of scalable 32-bit automotive microcontrollers based on the TriCore™ architecture. Depending on the device variant, TC3xx MCUs integrate up to six CPU cores running at frequencies of up to 300 MHz, combined with large on-chip Flash and SRAM memories, advanced timer peripherals, and high-speed communication interfaces such as CAN FD, FlexRay, Ethernet, and LIN.
A key focus of the TC3xx family is functional safety and cybersecurity. The devices provide hardware safety mechanisms including lockstep cores, ECC-protected memories, watchdogs, clock and voltage monitoring, and a Safety Management Unit (SMU), enabling support for applications up to ISO 26262 ASIL-D. Many devices also integrate a Hardware Security Module (HSM) for secure boot, authentication, and cryptographic services.
The AURIX TC3xx family is widely used in automotive powertrain, chassis, domain controller, and industrial control applications. Its multicore architecture, real-time performance, and extensive peripheral set make it well suited for demanding embedded systems requiring deterministic behavior, high computational performance, and robust safety features.
Supported devices
Refer to the supported device list for a full list of all supported TC3xx family devices, their corresponding names and connection diagrams.
Target interfaces
| Interface | J-Link support | Flasher support |
|---|---|---|
| JTAG |  |
|
| DAP | |
|
Memory blocks
| Flash bank | Base address | J-Link support | Flasher support | Loader | |
|---|---|---|---|---|---|
| Name | Bank size | ||||
| Program Flash | 0x80000000 (cached) (0xA0000000 (uncached) [1]) | |
|
Default | up to 16 MB |
| Data Flash 0 - EEPROM | 0xAF000000 | |
|
Default | up to 1 MB |
| Data Flash 0 - UCBxx | 0xAF400000 | |
|
Default | 512 Byte per UCB |
| Data Flash 0 - CFS | 0xAF800000 | |
|
Default | 64 kB |
| Data Flash 1 - EEPROM | 0xAFC00000 | |
|
Default | up to 1 MB |
¹ The cached and uncached memory area contain the same data and may not overlap in the HEX file.
Limitations
#READ
The #READ command can only be used to read memory areas that have already been programmed.
Due to the memory's ECC correction, it is not possible to read deleted areas, which results in the error message: ReadBlock() failed.
Troubleshooting
Device ID does not match
At the start of the programming process, the Flasher attempts to connect to the device and read its device ID. Each Aurix device has a unique ID.
If a device ID error occurs, there may be several possible causes.
To obtain detailed information on the error, increase the "Verbosity level" in the U-Flash configuration to at least "Detailed" and transfer the project to the Flasher again.
Device ID = 0x00000000 or 0xFFFFFFFF
- There is a fault in the wiring
- The device is kept in reset by an external reset generator or watchdog
- The supply voltage is insufficient
Device ID is wrong
- The wrong device was selected in U-Flash
- There is another device on the board assembled
- The supply voltage is too low and/or the interface speed is too high