AN218629 Comparison of TRAVEO™ T1G and TRAVEO™ T2G
About this document
Scope and purpose
AN218629 compares MCUs of the TRAVEO™ T1G family with MCUs of the TRAVEO™ T2G Family CYT2/CYT3/CYT4 series.
Associated Part Family
TRAVEO™ T1G Family, TRAVEO™ T2G Family
Introduction
This application note compares TRAVEO™ T1G Family MCUs with TRAVEO™ T2G Family MCUs. Both TRAVEO™ T1G and TRAVEO™ T2G families are manufactured in 40-nm CMOS technology with embedded flash.
Several global system configurations are different between these two product families. While several resources have been enhanced, downward compatibility is maintained.
This application note consists of two main sections: one for automotive body segment, and the other for automotive cluster segment. The Body Entry/High Products section compares body products, while the Cluster Products section compares cluster products. The product lineup is listed in Table 1.
Table 1. MCU List for Comparison
Products | TRAVEO™ T1G Family | TRAVEO™ T2G Family |
---|---|---|
S6J3428, S6J3429, and S6J342A Series | CYT2B7, CYT2B9, and CYT4BF Series | |
S6J3200 Series | CYT4DN and CYT2C9 Series |
Body Entry/High Products
TRAVEO™ T2G Family MCU Features
Table 2. Features of TRAVEO™ T2G Family MCUs
Function | CYT2B7 Series | CYT2B9 Series | CYT4BF Series |
---|---|---|---|
Flash Memory (Code Flash) | Up to 1088 KB | 2112 KB | 8256 KB |
Flash Memory (Work Flash) | Up to 96 KB | 128 KB | 512 KB |
SRAM0 | Up to 64 KB | 128 KB | 512 KB |
SRAM1 | Up to 64 KB | 128 KB | 512 KB |
CXPI | Not Supported | Supported | Not Supported |
FlexRay | Not Supported | Not Supported | Supported |
Secure Digital High Capacity (SDHC) Host Controller | Not Supported | Not Supported | Supported |
Serial Memory Interface | Not Supported | Not Supported | Supported |
Ethernet | Not Supported | Not Supported | Supported |
Product Overview
TRAVEO™ T2G Family is a family of 32-bit MCUs based on the high-performance Arm® Cortex®-M series of CPUs, as Figure 1 shows, intended for automotive body-control applications.
The Cortex-M4 processor is the main CPU designed for a short interrupt response time, high code density, and high 32-bit throughput while maintaining a strict cost and power consumption budget. A secondary Cortex-M0+ based CPU can implement security, safety, and protection features. Note that the CYT4BF series uses two Cortex-M7 processors for primary processing.
Figure 1 through Figure 3 show the major architecture components of the CYT2B7 series, CYT2B9 series, and CYT4BF series. There are four major subsystems: CPU subsystem, system resources, peripheral blocks, and I/O subsystem.
Figure 1. Block Diagram (CYT2B7 Series)
Figure 2. Block Diagram (CYT2B9 Series)
Figure 3. Block Diagram (CYT4BF Series)
On-chip System Features
CPU
Both TRAVEO™ T1G and TRAVEO™ T2G Family are based on 32-bit Arm Cortex processors.
TRAVEO™ T1G Family has a single Cortex-R5 processor, while TRAVEO™ T2G Family is a dual-CPU with Cortex-M4 and Cortex-M0+ processors. In TRAVEO™ T2G, two CPUs are configured as the CPU subsystem; Cortex-M4 or Cortex-M7 processor is the main CPU and Cortex-M0+ processor is the secondary CPU that can implement security, safety, and protection features. Note that as the CPU core changes, MCU features change according to the core specification.
Table 3: Differences in CPU
Item | TRAVEO™ T1G Family | TRAVEO™ T2G Family | Remarks | ||
---|---|---|---|---|---|
Main CPU | Secondary CPU | ||||
CYT2B7/B9 Series | CYT4BF Series | ||||
CPU Core | Cortex-R5F | Cortex-M4 | Cortex-M7 (x2) | Cortex-M0+ | |
Operation Frequency | Up to 132 MHz | Up to 160 MHz | Up to 350 MHz | Up to 100 MHz | Product specifications |
FPU | Single/Double precision | Single precision | Single/Double precision | None | |
MPU | 16 regions | 8 regions | 16 regions | 8 regions | 1 |
Cache Memory | I-cache 16 KB / D-cache 16 KB | None | I-cache 16 KB / D-cache 16 KB | None | |
TCM Interface | Supported Implemented TCRAM | Not supported | Supported (ITCM, DTCM) | Not supported | |
Support for Interrupt Controller | Vector Interrupt Controller (VIC) | Nested Vector Interrupt Controller (NVIC) |
Memory Design
Table 4 lists the Code Flash features. The main differences are in program size, Read-While-Write operation, and redundancy.
Table 4: Differences in Code Flash
Code Flash | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Sector Size | 32 KB, 8 KB | 32 KB, 8 KB |
Program Size | 32 bits, 64 bits, 256 bit | 64 bits, 256 bits, 4096 bits |
Program and Erase Cycles/Retention | 1000/20 years | 1000/20 years |
Read-While-Write Operation | Not supported | Supported |
Table 5 lists the Work Flash features. The main differences are in the sector size, program and erase cycles, Read-While-Write operation, and redundancy. When compared to TRAVEO, TRAVEO™ T2G families support smaller sector size and higher program and erase cycles.
Table 5. Differences in Work Flash
Work Flash | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Sector Size | 4 KB | 2 KB, 128 B |
Program Size | 32 bits | 32 bits |
Program and Erase Cycles/Retention | 1000/20 years, 10000/10 years, 100000/5 years | 125000/20 years, 250000/10 years |
Read-While-Write Operation | Not supported | Supported |
Table 6 lists the SRAM features. The main difference is the data retention in low power mode. TRAVEO™ T2G Family supports data retention in DeepSleep mode.
Table 6. Differences in SRAM
SRAM | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Data Retention in Low Power Mode | Not supported (TCRAM and SRAM are not retained in Shutdown mode. Backup RAM is retained in Shutdown mode) | Supported (SRAM is retained in DeepSleep mode) |
Debug
TRAVEO™ T1G and TRAVEO™ T2G families support JTAG and SWD Debug Interface. Table 7 shows the main differences in debugging.
Table 7. Differences in Debugging
Item | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
Debug interface | JTAG, SWD | JTAG, SWD |
Mode Setting
TRAVEO™ T2G Family does not support the serial programming mode; therefore, there is no mode pin in TRAVEO™ T2G Family. When the debugger is connected to JTAG, TRAVEO™ T2G Family transitions to Debug mode and enables programming to flash.
Table 8. Differences in Mode Setting
Item | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
Normal Mode | Setting by mode pin
| Debugger is not connected (SWD or JTAG)
|
Board mode | Setting by mode pin
| Debugger is connected (SWD or JTAG)
|
Power Supply and Monitoring
The power supply of TRAVEO™ T2G Family is the same as that of TRAVEO™ T1G Family, but signal names of power supply are different. Also, the type of power monitoring mode has been enhanced in TRAVEO™ T2G Family.
Power Supply
Table 9 lists the power supply and differences in functionality.
Table 9. Power Supply
Power Supply | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series | |||
---|---|---|---|---|---|
External | Digital | VCC | 2.7 to 5.5 V | VDDD | 2.7 to 5.5 V |
I/O | VDD IO_1/2 | 2.7 to 5.5 V | |||
VDD IO_3/4 | 2.7 to 3.6 V (only for CYT4BF series) | ||||
Analog | AVCC0/1 | 2.7 to 5.5 V | VDD A | 2.7 to 5.5 V | |
Internal | C | 1.2 V | VCCD | 1.1 V VCCD of CYT4BF can be also external power supply (typical 1.15 V when VCCD is external power supply) |
Monitoring
Table 10 lists the differences in voltage between TRAVEO™ T1G and TRAVEO™ T2G families.
Table 10. Voltage Monitoring
Monitoring | S6J3428/9/A Series | CYT2B7/B9, CYT4BF Series |
---|---|---|
Voltage Monitoring |
|
|
Reset Factor
Note that all resets in TRAVEO™ T2G Family are asynchronous resets. This difference is because the reset factor is optimized according to the TRAVEO™ T2G system. If you need the RAM retention Reset, see the Architecture Technical Reference Manual (TRM). Table 11 lists the main differences in Reset Factor.
Table 11. Differences in Reset Factors
Reset Sources | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | Remarks |
---|---|---|---|
POR | Yes | Yes | |
BOD Reset |
| ||
OVD Reset | No | ||
OCD Reset | No | Internal voltage OCD Reset4 | |
External Reset | RSTX pin | XRES_L pin | |
Clock Stop Wait Timeout Reset | Yes | No, does not support synchronous reset | |
Illegal Mode Detection Reset | Yes | No, does not have MD pin | |
Profile Error Reset | Yes | No, does not support Profile setting | |
Watchdog Timer (WDT) Reset |
|
| See Watchdog Timer |
Internal System (Software) Reset |
|
| |
Fault Detection Reset | No | Yes: via Fault report | |
Clock Supervision (CSV) Reset |
|
| |
Wakeup Reset | Yes (Power Domain Reset) | Yes (Hibernate Wake up Reset) | |
Debugger Reset |
|
|
Clock System
Compared to TRAVEO™ T1G Family clock system, TRAVEO™ T2G Family (only CYT4B Series) has Spread Spectrum Clock Generator functions. In TRAVEO™ T2G Family, frequency-locked loop (FLL) featuring fast startup and low power is implemented. Table 12 lists the main differences in clock system.
See the datasheet for the AC characteristics of each clock.
Table 12. Differences in Clock System
Clock System | TRAVEO™ T1G Family(S6J3428/9/A Series) | TRAVEO™ T2G Family(CYT2B Series) | TRAVEO™ T2G Family(CYT4B Series) | |
---|---|---|---|---|
Internal Clock Source | Fast CR: 4 MHz (Using source clock after reset) Slow CR: 100 kHz | IMO: 8 MHz (Using source clock after reset) ILO0/1: 32 kHz | ||
External Clock Source | Main clock: 3.6 to 16 MHz Sub clock: 32.768 kHz | ECO: 3.988 to 33.33 MHz WCO: 32.768 kHz EXT_CLK5 : 0.25 to 100 MHz | ||
High-Speed Clock Generation | PLL | PLL x1 Input: 3.6 to 17.6 MHz Output: 200 to 320 MHz SSCG PLL x1 Input: 3.6 to 32MHz Output:200 up to 320 MHz | PLL x1 Input: 3.988 to 33.34 MHz Output: 11 to 160 MHz SSCG not supported | PLL without SSCG x2 Input: 3.988 to 33.34 MHz Output: 11 to 200 MHz PLL with SSCG x2 Input: 3.988 to 33.34 MHz Output: 25 to 400 MHz |
FLL | Not implemented | FLL x1 Input: 0.25 to 80 MHz Output: 24 to 100 MHz | FLL x1 Input: 0.25 to 80 MHz Output: 24 to 100 MHz | |
Clock Gear | Supported | Not implemented | ||
Clock Supervision | Main clock Sub clock PLL clock SSCG clock Slow CR Fast CR | CLK_REF (IMO or ECO or EXT_CLK) CLK_HF (PLL and FLL) ILO0 CLK_LF (ILO1 or WCO) |
Watchdog Timer
Table 13 lists the watchdog timer (hardware) features. The main differences are counter clock, maximum timeout, and the behavior during low-power mode and debugging.
Table 13. Differences in Watchdog Timer (Hardware)
Watchdog Timer (Hardware) | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Trigger | Reset | Reset |
Counter Clock |
|
|
Counter | 32 bits | 32 bits |
Maximum Timeout | 12 hours | 38.33 hours |
Window Function | Supported | Supported |
Warning Interrupt | Supported | Supported |
Timeout Expiration Action | Reset or nonmaskable interrupt (NMI) | Reset |
Behavior During Low-Power Mode | Stop | Register can select stop or run |
Behavior During Debugging | Stop at debugging state | Register can select stop or run |
Table 14 lists the multi-counter watchdog timer (software) features. The main differences are counter clock, counter, maximum timeout, and the behavior during debugging.
Table 14. Differences in Multi-Counter Watchdog Timer (Software)
Multi-counter Watchdog Timer (Software) | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Trigger | User program | User program |
Counter Clock |
|
|
Counter | 32 bits | 2 * 16-bit, 32 bits only for interrupt |
Maximum Timeout | 36.4 hours | 2.11 seconds |
Window Function | Supported | Supported |
Warning Interrupt | Supported | Supported |
Timeout Expiration Action | Reset or NMI | Reset or Fault |
Behavior During Low-Power Mode | Register can select stop or run. | Register can select stop or run. |
Behavior During Debugging | Stop at debugging state | Register can select stop or run. |
Low-Power Mode
Table 15 lists the low-power modes. TRAVEO™ T2G Family supports almost all low-power modes with DeepSleep mode.
Table 15. Differences of Low-Power Modes
Low Power Mode | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Sleep
| Supported: Sleep
| Supported: Sleep
|
Timer
| Supported: Timer
| Supported: DeepSleep
|
Stop
| Supported: Stop
| Supported: DeepSleep
|
Partial wakeup (Shutdown)
| Supported: Partial wakeup
| Supported: DeepSleep
|
Timer (Shutdown)
| Supported: Timer (Shutdown)
| Supported: DeepSleep
|
Stop (Shutdown)
| Supported: Stop (Shutdown)
| Supported: DeepSleep
|
Interrupt Structure
The interrupt structure of TRAVEO™ T1G and TRAVEO™ T2G families differ based on the CPU. TRAVEO™ T1G Family (Cortex-R5) interrupt controller used vector interrupt controller (VIC), while TRAVEO™ T2G Family (Cortex-M4//M7/M0+) uses nested vector interrupt controller (NVIC). Table 16 lists the main differences in interrupt structure.
TRAVEO™ T1G Family controls system interrupts such as enable/disable, levels, and level masks with an external interrupt controller. Each CPU of TRAVEO™ T2G Family has eight interrupt inputs, and controls interrupts within the CPU, thereby performing high-speed interrupt processing.
TRAVEO™ T2G Family uses up to 1023 system interrupts assigned to eight groups. All interrupts within a group has the same priority. Four of the 1023 system interrupts can be assigned as NMI.
TRAVEO™ T2G Family implements wakeup interrupt controller (WIC), which enables interrupt detection for CPU wakeup in DeepSleep power mode.
Table 16. Differences of Interrupt Structure
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | Remarks | |
---|---|---|---|---|
CPU core | Cortex-R5F | Cortex-M4/M7 | Cortex-M0+ | |
Supported Interrupt Controller in CPU | VIC | NVIC | ||
Number of IRQ inputs of CPU | 1 | 8 | 8 | |
Number of NMI Inputs of CPU | 1 | 1 | 1 | |
Priority Level | Interrupt: 32 levels NMI: 16 levels | Interrupt: 8 levels NMI: None | Interrupt: 4 levels NMI: None | |
Number of System Interrupts | Up to 512 | Up to 1023 | 5 | |
Vector Address | Assigned for each system interrupt | Assigned for each IRQ input. Multiple system interrupts share a CPU interrupt handler as provided by the VTOR table. | ||
WIC | Not Supported | Supported |
System Interrupts are interrupts generated from peripheral functions and external inputs. For the list of system interrupts supported by the device variants, see the following documents:
- TRAVEO™ T1G Family: Hardware Manual by the device variants.
- TRAVEO™ T2G Family: Architecture Technical Reference Manual by the device variants.
Data Transfer
For data transfer, TRAVEO™ T2G Family has two types of DMA with different purposes: Peripheral DMA (P-DMA) and Memory DMA (M-DMA). Table 17 lists the main differences in data transfer.
P-DMA focuses on achieving low latency for a large number of channels. P-DMA has a single data transfer engine that is shared by all channels.
M-DMA focuses on achieving high memory bandwidth for a small number of channels. M-DMA has a dedicated data transfer engine for each channel.
The DMA transfer specification of TRAVEO™ T1G Family is set by the register. In TRAVEO™ T2G Family, transfer is specified by the descriptor in SRAM. P/M-DMA of TRAVEO™ T2G Family can perform transfer chaining with descriptor setting.
Table 17. Differences of Data Transfer
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | Remarks | |
---|---|---|---|---|
Function Name | DMAC | P-DMA | M-DMA | |
Data Transfer Specifics | Register | Descriptor in memory | ||
Data Size | 8-/16-/32-/64-bit | 8-/16-/32-bit | ||
Transfer Mode |
|
|
| |
Activation Trigger |
|
|
| |
Channel Arbitration Schemes |
|
| ||
Interrupt Generation |
|
| ||
Protection Schemes | Dedicated MPU
| SMPU and PPU
| See Protection. |
TPU
TRAVEO™ T1G Family has a dedicated timer for timing protection (TPU). However, TRAVEO™ T2G Family does not have a dedicated timer. TRAVEO™ T2G Family uses a TCPWM timer for timing protection.
The TCPWM timer is a general-purpose timer that can generate interrupts for overflow, underflow, and compare matches. This interrupt can be implemented as NMI, which can provide the TPU function. Figure 4 shows the configuration of the TPU and Figure 5 shows an example of the operation.
Figure 4. Timing Protection Implementation Example
- Configure the TCPWM initial values (for example, using DownCount mode), and set the upper limit of the measurement time as the initial time.
- Set the TCPWM interrupt to NMI.
- Software starts the timer at the start point of the measurement process.
- Software stops the timer at the end point of the measurement process.
- If the counter under-flowed before the software stops the timer, the Underflow interrupt of the TCPWM is notified as an NMI to the CPU via the interrupt controller.
Note: The interrupt controller can notify the system interrupt as NMI, including the TCPWM interrupt.
Figure 5. Timing Protection Example (Monitoring of the Interrupt Service
Routine Operation Time)
Fault Report
Fault report is a new feature of TRAVEO™ T2G Family. Figure 6 shows a block diagram of the Fault structure.
The centralization of faults by Fault report structures for a system-wide consistent handling of faults simplifies software development.
Fault report captures up to 967 failures such as MPU/SMPU/PPU protection violations, SRAM controller ECC errors, peripheral-specific errors, and so on. When Fault report captures a fault, it generates a notification signal such as fault interrupt, trigger output, external pin output, and fault reset request. Each of these output signals can be enabled or disabled.
The fault interrupt can be mapped to the CPU NMI as a system interrupt. In addition, Fault report provides the fault source and additional fault-specific information.
For more details, see the TRAVEO™ T2G Architecture Technical Reference Manual (TRM).
Figure 6. Fault Structure
7 For the list of system interrupts supported by the device variants, see the Technical Reference Manual.
Protection
The Protection function of TRAVEO™ T1G Family consists of the CPU’s Memory Protection Unit (MPU), DMA's MPU, and Peripheral Protection Unit (PPU). TRAVEO™ T2G Family consists of MPU, Shared Memory Protection Unit (SMPU), and PPU. Table 18 lists the main differences in Protection Units.
In TRAVEO™ T2G Family, memory protection is provided by MPU and SMPU. MPU is implemented as part of the CPU and bus infrastructure. P-DMA, M-DMA, and encrypted components do not have MPU. Instead, they inherit the access control attributes of programmed bus transfer.
SMPU is shared by all masters; PPU is a protection unit for peripheral registers.
TRAVEO™ T2G Family supports a new protection attribute (Secure/Non-secure), and protection contexts. Protection contexts can change the access restriction without changing the setting of the protection unit.
For more details, see the Technical Reference Manual.
Table 18. Differences in Protection Configuration and Access Attribute
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | Remarks |
---|---|---|---|
MPU implemented in the CPU | Cortex-R5: 16 Regions Access Attribute:
| ||
MPU implemented in the bus infrastructure | Not supported | 16 Regions Access Attribute:
| For external master such as debugger |
SMPU | Not supported | 16 Regions Access Attribute:
| |
PPU | Access Attribute:
| Access Attribute:
| |
MPU16-AHB | Access Attribute:
| Not supported. DMA access protection is provided by SMPU and PPU. |
Boot Process
The boot process of both TRAVEO™ T1G and TRAVEO™ T2G families is executed after reset and before the application program starts. The boot process is executed by the Cortex-R5 processor in TRAVEO™ T1G Family, and is executed by the secure master (Cortex-M0+ processor) in TRAVEO™ T2G Family.
The boot process in TRAVEO™ T1G Family mainly executes based on the operation mode and the security setting that the debugger connection authenticates, secure boot processing, and hardware watchdog timer according to the flash marker.
In TRAVEO™ T2G Family, the boot process consists of ROM boot and flash boot. The ROM boot process determines the Protection State and validates the flash boot process. The flash boot process configures the protection unit such as SMPU and PPU, and verify the application program code in the flash memory. In addition, activates the boot loader.
For more details, see the Technical Reference Manual.
Security
Table 19 lists the security features. TRAVEO™ T2G Family supports lifecycle stages, device protection states, and Hardware Security Module (HSM).
Table 19. Differences of Security
Security | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Lifecycle stages Device protection states | Not supported | Supported
|
Flash protection | Supported | Supported |
Debugger security | Supported | Supported |
Hardware-based encryption | Supported Secure Hardware Extension (SHE) | Supported Enhanced Secure Hardware Extension (eSHE) and HSM support are enabled by third-party firmware. |
Peripherals
Timer
The Timer function of TRAVEO™ T1G Family consists of a Base timer, Reload timer, Free-run timer, Input Capture, Output compare, and Quadrature Position/Revolution Counter (QPRC).
TRAVEO™ T2G Family implements TCPWM with integrated multiple timer functions. The TCPWM has seven operation modes. All TCPWM channels can be operated by selecting one of the seven modes. Table 20 lists the corresponding modes of each function.
Table 20. TCPWM Channel Modes
Function Name | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Mode | Base timer: Reload Timer mode Free-run Timer Reload Timer | TCPWM: Timer mode |
Capture Mode | Input Capture Base timer: PWC Timer mode | TCPWM: Capture mode |
Quadrature Decoder | QPRC | TCPWM: QUAD mode |
PWM Mode | Output compare Base timer: PWM Timer mode Base timer: PPG Timer mode | TCPWM: PWM mode |
PWM with Dead Time | Not supported | TCPWM: PWM_DT mode |
Pseudo-Random PWM | Not supported | TCPWM: PWM_PR mode |
Shift Register | Not supported | TCPWM: SR mode |
Base Timer: Reload Timer Mode
The Base Trimer Reload mode in TRAVEO™ T1G Family is a timer that counts down from a set value. When the timer value reaches ‘0’, the timer stops or starts counting down from the set value again. Also, an event can be generated if the timer value is ‘0’. In TRAVEO™ T2G Family, the same operation is possible using TCPWM Timer mode. Table 21 lists the main differences in Base Timer Reload Timer modes between TRAVEO™ T1G and TRAVEO™ T2G families.
Table 21. Differences in Base Timer: Reload Timer Mode
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Function | Base Timer: Reload Timer mode | TCPWM: Timer mode |
Counter Width | 16 bits or 32 bits (uses two 16-bit timer) | 16 bits or 32 bits |
Count Mode | Down | Up, Down, Up-down1/2 |
Operation Clock | Internal clock: 12 types: /1, /2, /4, /8, /16, /32, /64, /128, /256, /512, /1024 or /2048 | Internal clock: 8 types: /1, /2, /4, /8, /16, /32, /64 or /128 |
External clock: Rising-edge, falling-edge, or both-edge | Not supported | |
Operation mode | One shot mode: Stop event is underflow | One shot mode: Stop event depends on count mode. (underflow, overflow or both) |
Reload mode | Reload mode | |
Gate function | Supported | Supported |
Activation | Software | Software: via Trigger Multiplexer |
External trigger | External trigger | |
External Timer Match Starting | Not supported | |
Event Generation | Underflow | TC event: TC event depends on count mode. (underflow, overflow or both) |
Timer Activation trigger | Not Supported | |
Not supported | Compare match event | |
Debug Mode | Supported | Supported |
32-bit Free-run Timer
The Free-run timer in TRAVEO™ T1G Family counts up or up-down within a set value. In TRAVEO™ T2G Family, the same operation is possible using TCPWM Timer mode. However, in TRAVEO™ T2G Family there is no interrupt mask count function. Table 22 lists the main differences in Free-run Timer.
Table 22. Differences in 32-bit Free-run Timer
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer function | 32-bit Free-run Timer | TCPWM: Timer mode |
Counter width | 32 bits | 16 bits or 32 bits |
Count mode | Up, Up-down | Up, Down, Up-down1/2 |
Operation clock | Internal clock: 9 types: /1, /2, /4, /8, /16, /32, /64, /128 or /256 | Internal clock: 8 types: /1, /2, /4, /8, /16, /32, /64 or /128 |
External clock: Both-edge | Not supported8 | |
Operation mode | Not Supported | One shot mode: Stop event depends on the count mode (underflow, overflow, or both) |
Reload mode | Reload mode | |
Buffer function | Supported | Supported |
Activation | Software | Software: via Trigger Multiplexer |
Not supported | External trigger | |
Event Generation | Compare clear Zero Detection | TC event: TC event depends on count mode (underflow, overflow, or both) |
Not supported | Compare match event | |
Interrupt mask count Function | Not Supported | |
Debug Mode | Supported | Supported |
32-bit Reload Timer
The 32-bit Reload mode in TRAVEO™ T1G Family is a timer that counts down from a set value. In TRAVEO™ T2G Family, the same operation is possible using TCPWM Timer mode. Table 23 lists the main differences in 32-bit Reload Timer.
Table 23. Differences of 32-bit Reload Timer
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Function | 32-bit Reload Timer | TCPWM: Timer mode |
Counter Width | 32 bits | 16 bits or 32 bits |
Count Mode | Down | Up, Down, Up-down1/2 |
Operation Clock | Internal clock: 6 types: /1, /2, /4, /8, /16 or /32 | Internal clock: 8 types: /1, /2, /4, /8, /16, /32, /64 or /128 |
External clock: Rising-edge, falling-edge, or both edges | Not supported8 | |
Operation Mode | One shot mode: Stop event is underflow | One shot mode: Stop event depends on count mode (underflow, overflow, or both) |
Reload mode | Reload mode | |
Gate Function | Supported | Supported |
Activation | Software | Software: via Trigger Multiplexer |
External trigger | External trigger | |
Event Generation | Underflow | TC event: TC event depends on count mode (underflow, overflow, or both) |
Not supported | Compare match event | |
Simultaneous Soft Start | Supported | Supported: via Trigger Multiplexer |
Debug Mode | Supported | Supported |
32-bit Input Capture
The 32-bit input capture function in TRAVEO™ T1G Family measures the input pulse width and external clock cycle based on the value of the 32-bit free-run timer. In TRAVEO™ T2G Family, the same operation is possible using the TCPWM capture mode.
In TRAVEO™ T1G Family, the Input capture function is a linkage function with the free-run timer, but TRAVEO™ T2G Family has an independent timer for each TCPWM channel. Therefore, TRAVEO™ T2G Family does not need a different timer for the Input Capture function. Table 24 lists the main differences in 32-bit Input Capture.
Table 24. Differences in 32-bit Input Capture
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Function | 32-bit Input Capture | TCPWM: Capture mode |
Counter Width | 32 bits | 16 bits or 32 bits |
Count Mode | Follow Free-run Timer | Up, Down, Up-down1/2 |
Operation Mode | Follow Free-run Timer | One shot mode: Stop event depends on count mode. (underflow, overflow or both) |
Reload mode | ||
Clock Pre-scaling | Follow Free-run Timer | Internal clock: 8 types: /1, /2, /4, /8, /16, /32, /64 or /128 |
Capture Event | Rising-edge, falling-edge, or both-edge | Supported: via Trigger Multiplexer |
Buffer Function | Not supported | Double buffer Counter value is copied to the capture register and capture register is copied to the capture buffer register when a Capture event is detected. |
Event Generation | Capture event detection | Counter value is captured. |
Base Timer: PWC Timer Mode
Base Timer: PWC Timer mode in TRAVEO™ T1G Family measures the time and cycle between any input pulse events by using a counter.
TRAVEO™ T2G Family does not have the same operation mode. However, the TCPWM capture mode can measure via software the time between two events using two buffers. Figure 7 shows an example of the operation.
Figure 7. Example for Pulse Width Count Measurements
QPRC
The Quadrature decoder is used to measure the position of position encoder. Both TRAVEO™ T1G and TRAVEO™ T2G families implement Quadrature Decoder.
Both support x 1, x 2, x 4 count modes. However, Revolution counter operation mode is not supported in TRAVEO™ T2G Family. Table 25 lists the main differences in QPRC.
Table 25. Differences in QPRC
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer function | QPRC | TCPWM: QUAD mode |
Counter width | Two 16 bits (Position counter, Revolution counter) | 16 bits or 32 bits |
Position counter Operation mode | Up/Down count mode | Up/Down Rotary mode |
Not Supported | x 1 encoding | |
Phase difference count mode x2 mode Count edge: phi_B | x 2 encoding Count edge: phi_A | |
Phase difference count mode x4 mode | x 4 encoding | |
Count mode with direction | Not Supported | |
Revolution counter Operation mode | RC_mode1 | Not supported |
RC_mode2 | ||
RC_mode3 | ||
Event Generation | Count inversion | Not Supported |
Zero index | tc event with Reload/Index event | |
Overflow | Supported QUAD_RANGE1_CMP, QUAD_RANGE1_CAPT | |
Under flow | Supported QUAD_RANGE1_CMP, QUAD_RANGE1_CAPT | |
PC and RC match | Not Supported | |
PC match | Supported: QUAD_RANGE0_CMP QUAD_RANGE1_CMP | |
PC match and RC match | Not Supported | |
Out range | Not Supported | |
Capture | Not Supported | Supported: QUAD_RANGE1_CAPT |
Debug Mode | Not Supported | Supported |
32-bit Output Compare
The 32-bit output compare in TRAVEO™ T1G Family generates the PWM waveform with 32-bit Free-run timer. In addition, events can be generated at compare match. In TRAVEO™ T2G Family, the same operation is possible using TCPWM PWM mode. Table 26 lists the main differences in 32-bit Reload Timer.
Table 26. Differences in 32-bit Output Compare
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer function | 32-bit Output compare | TCPWM: PWM mode |
Counter width | 32 bits | 16 bits or 32 bits |
Count mode | Up, Up-down | Up, Down, Up-down1/2 |
Operation clock | 9 types Internal Clock
| Internal clock: 8 types
|
External clock
| Not supported8 | |
Buffer function | Supported | Supported |
Compare registers per channel | Two | Two |
Output pins per channel | Two
| Two
|
One shot mode | Not Supported | One shot mode:
|
Signal output | Invert mode | Supported |
Set/Reset mode | Supported | |
Activation | Software | Software: via Trigger Multiplexer |
Not supported | External trigger | |
Compare match | Supported | |
Not Supported | TC event:
| |
Kill modes | Not supported | Supported |
Debug Mode | Supported | Supported |
Base Timer: PWM Timer Mode
Base Trimer PWM mode in TRAVEO™ T1G Family can output waveforms of the set cycle either singly or continuously upon the detection of a trigger. In this mode, cycle and duty are set to generate PWM waveform.
In TRAVEO™ T2G Family, the same operation is possible using TCPWM PWM mode. Table 27 lists the main differences in Base Timer PWM Mode.
Table 27. Differences in Base Timer: PWM Timer Mode
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Function | Base Timer: PWM mode | TCPWM: PWM mode |
Counter Width | 16 bits | 16 bits or 32 bits |
Count Mode | Down | Up, Down, Up-down1/2 |
Operation Clock | Internal clock: 12 types /1, /2, /4, /8, /16, /32, /64, /128, /256, /512, /1024 or /2048 | Internal clock: 8 types /1, /2, /4, /8, /16, /32, /64 or /128 |
External clock: Rising-edge, falling-edge, or both-edge | Not supported8 | |
Operation Mode | One shot mode: Stop event is underflow | One shot mode: Stop event depends on count mode. (underflow, overflow or both) |
Continuous mode | Reload mode | |
Start Delay | Supported | Not Supported9 |
Buffer Function | Supported | Supported |
Activation | Software | Software: via Trigger Multiplexer |
External trigger | External trigger | |
External Timer Match Starting | Not supported | |
Signal Output | 1: Inverted output when cycle and duty match | 2: Inverted output when compare match LINE_OUT and LINE_COMPL_OUT |
Right-aligned PWM | Left-aligned, Right-aligned, Center-aligned, Asymmetric PWM | |
Output polarity control | Supported | |
Trigger Output | A/D convertor activation | Supported |
Event Generation | Underflow | TC event: TC event depends on count mode. (underflow, overflow or both) |
Duty match | Supported: compare match | |
Start Trigger Detection | Not Supported | |
Debug Mode | Supported | Supported |
9 Counters can be pre-loaded with values reflecting the desired phase shift and then started synchronously. Note that during the initial (start delay) period, some counters can already generate the PWM output, depending on the duty cycle.
Base Timer: PPG Timer Mode
The Base Trimer PPG mode in TRAVEO™ T1G Family can output single or continuous waveforms with the configured cycle either when a trigger is detected. In this mode, ‘L’ width and ‘H’ width are set to generate the PPG waveform.
In TRAVEO™ T2G Family, the same operation is possible using TCPWM mode. Table 28 lists the main differences in Base Timer: PPG Timer Mode.
Table 28. Differences in Base Timer: PPG Timer Mode
Counter | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Timer Function | Base Timer: PPG mode | TCPWM: PWM mode |
Counter Width | 16 bits | 16 bits or 32 bits |
Count Mode | Down | Up, Down, Up-down1/2 |
Operation Clock | Internal clock: 12 types /1, /2, /4, /8, /16, /32, /64, /128, /256, /512, /1024 or /2048 | Internal clock: 8 types: /1, /2, /4, /8, /16, /32, /64 or /128 |
External clock: Rising-edge, falling-edge, or both-edge | Not supported8 | |
Operation mode | One shot mode: Stop event is underflow | One shot mode: Stop event depends on count mode. (underflow, overflow or both) |
Continuous mode | Reload mode | |
Activation | Software | Software: via Trigger Multiplexer |
External trigger | External trigger | |
Signal Output | 1 Inverted output when cycle and duty match | 2
|
Event Generation | Underflow | TC event: TC event depends on count mode. (underflow, overflow or both) |
Start Trigger Detection | Not Supported | |
Debug Mode | Supported | Supported |
TCPWM: PWM_DT Mode
This mode adds Dead time to the PMW output waveform. This function is not supported in TRAVEO™ T1G Family. Figure 8 shows an example of the operation. The PWM_DT functionality is the same as the PWM functionality except for the following differences:
- PWM_DT supports dead time insertion; PWM does not support dead time insertion.
- PWM_DT does not support clock pre-scaling; PWM supports clock pre-scaling.
For more details, see the Technical Reference Manual.
Figure 8. Dead Time Timing
TCPWM: PWM_PR Mode
This functionality changes the counter value using the linear feedback shift register (LFSR). This results in a pseudo random number sequence; the generated signal has frequency/noise characteristics different from a regular PWM signal. This function is not supported in TRAVEO™ T1G Family. Figure 9 shows an example of the operation.
For more details, see the Technical Reference Manual.
Figure 9. PWM_PR Output
TCPWM: SR Mode
This functionality shifts the counter value to the right. This implements a signal delay function from the trigger input to the line output, which can be used for functions such as detecting frequency shift keying (FSK) signals. This function is not supported in TRAVEO™ T1G Family. Figure 10 shows an example of the operation. For more details, see the TRM.
Figure 10. SR Mode Operation
PWM line output is generated from an XOR combination of enabled counter taps (bit position) defined by PERIOD_BUFF.
8 The external clock cannot be used as the timer's count clock. However, when the count event is used in the rising edge (supported falling and both edge) detection mode, the timer will count with count event detection. In this case, the count event can be used as the external clock.
9 Counters can be pre-loaded with values reflecting the desired phase shift and then started synchronously. Note that during the initial (start delay) period, some counters can already generate the PWM output, depending on the duty cycle.
Serial Communication Block
The serial communication function realized by MFS on TRAVEO™ T1G Family is realized by SCB in TRAVEO™ T2G Family. In TRAVEO™ T2G Family, the LIN function is realized by a dedicated module.
Table 29. Differences in Serial Communication Block
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | |
---|---|---|---|
Function name | Multi-Function Serial (MFS) | Serial communication Block (SCB) | LIN |
Supported function |
|
| LIN (v 2.2A) |
UART
TRAVEO™ T2G Family SCB (UART) data transmission and reception are always executed in FIFO mode. In TRAVEO™ T2G Family, eight out of nine SCB blocks support full UART, and one SCB does not support UART mode. Table 30 lists the main differences.
Table 30. Differences in UART
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Data | Transmission and reception FIFOs (64 bytes each) (when FIFOs are used) | Transmission/reception FIFO (32/256/512 bytes each) (FIFO mode only) |
Serial Input | Oversampling is performed 3 times by the bus clock. The reception value is determined by majority decision. |
|
Transfer Format | Asynchronous | Asynchronous |
Baud Rate | Dedicated baud rate generator (15-bit reload counter configuration) | CTRL.OVS register supported
|
The external clock input can be adjusted by the reload counter. | Not supported | |
Data Length | 5 to 9 bits (for normal mode), or 7 to 8 bits (for multi-processor mode) | 4 to 16 bits (Standard/Multi-processor mode) |
Signaling Method | NRZ | NRZ |
Inverted NRZ | Not supported | |
Start Bit Detection | Synchronized to falling edges of the start bit (for NRZ method) | Synchronized with the start bit falling edge (NRZ system) |
Synchronized to rising edges of the start bit (for inverted NRZ method) | Not supported | |
Reception Error Detection | Framing error | Framing error |
Overrun error | Not supported | |
Parity error (Normal mode only) | Parity support (Odd parity and even parity) | |
Hardware Flow Control | Transmission/reception auto control by CTS and RTS | Transmission/reception auto control by CTS and RTS |
Interrupt Request | Reception interrupt | Reception interrupt (Frame error, Parity error) |
Reception FIFO interrupt | Reception FIFO interrupt (RX FIFO is full, RX FIFO is not empty, RX FIFO overflow, RX FIFO underflow) | |
Transmission interrupt | Transmission interrupt (TX done) | |
Transmission FIFO interrupt | Transmission FIFO interrupt (TX FIFO is not full, TX FIFO is empty TX FIFO overflow, TX FIFO underflow) | |
DMA transfer is supported for both transmission and reception | Not supported | |
Status interrupt | Not supported | |
Master/Slave-Type Communication Function (Multi-Processor Mode) | 1 (master) -to-n (slave) communication is supported. (Both master and slave systems are supported.) | 1 (Master)-to-n (slave) communication is supported (Both master and slave systems are supported) |
FIFO option | Transmission and reception FIFOs are provided | Transmission and reception FIFOs are supported |
Transmission FIFO and reception FIFO can be selected | Not supported | |
Transmission data can be retransmitted | Not supported | |
The timing of the reception FIFO interrupt can be changed by software | The timing of the reception FIFO interrupt can be changed by software | |
Independent FIFO reset is supported | Independent FIFO reset is supported |
I2C
TRAVEO™ T2G Family SCB (I2C) data transmission and reception are always executed in FIFO mode. In TRAVEO™ T2G Family, eight out of nine SCB blocks support full I2C and one SCB supports only I2C slave mode. Table 31 lists the main differences.
Table 31. Differences in I2C
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Data Buffer | Full duplex-double buffer (FIFO is unused). | Single memory buffer. (EZ I2C /Command-RESP). |
Transmission/reception FIFO (16 bytes each) (when FIFO is used). | Transmission/reception FIFO (32/256/512 bytes each) (FIFO mode only). | |
Serial Input | For serial clock and data input, noise from 2 to up to 38 bus clocks is filtered out. | Filtering glitches up to 50 ns. |
Transfer Mode | Synchronization | Synchronization |
Baud Rate | Dedicated baud rate generator provided (comprising 15-bit reload counter). |
|
Data Length | 8 bits | 8 bits |
Signaling Method | NRZ | NRZ |
Interrupt Request | Reception interrupt | Reception interrupt. (I2C STOP detection at the end of each transfer, I2C STOP detection at the end of a read transfer). |
Transmission interrupt | Transmission interrupt. (I2C STOP detection at the end of each transfer, I2C STOP detection at the end of a write transfer). | |
Status interrupt (INT interrupt, stop condition interrupt, repeated start detection interrupt, serial timer interrupt). | Status interrupt. (I2C master lost arbitration, I2C master received NACK, I2C master received ACK, I2C bus error, I2C slave lost arbitration, I2C slave received NACK, I2C slave received ACK, I2C slave received STOP, I2C slave received START, I2C slave address matched, I2C bus error). | |
Transmission FIFO interrupt (A transmission FIFO overrun error occurs when the transmission FIFO is not higher than the interrupt trigger level or when the transmission FIFO is empty). | Transmission FIFO interrupt (TX FIFO is not full, TX FIFO is empty, TX FIFO overflow, TX FIFO underflow). | |
Reception FIFO interrupt (reception FIFO under run) | Reception FIFO interrupt (RX FIFO is full, RX FIFO is not empty, RX FIFO overflow, RX FIFO underflow). | |
A DMA transfer support function is provided for both transmission and reception. | Not supported | |
Not supported | Wake up request on address match | |
FIFO |
|
|
Clock Stretching | Supported | Supported |
I2C Mode | Supported
| Supported
|
SPI
TRAVEO™ T2G Family SCB (SPI) data transmission and reception are always executed in FIFO mode. In TRAVEO™ T2G Family, eight out of nine SCB blocks support full SPI, and one SCB supports only SPI slave mode. Table 32 lists the main differences.
Table 32. Differences in SPI
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Data Buffer | Transmission and reception FIFOs (64 bytes each) (when FIFO is used) | Transmission/reception FIFO (32/256/512 bytes each) (FIFO mode only) |
Transfer Format | Clock synchronization (no start/stop bits) | Clock synchronization (no start/stop bits) |
Master/slave functions | Master/slave functions | |
Supports SPI (supports both master and slave) | Supports SPI (supports both master and slave) | |
Baud Rate | A dedicated baud rate generator is provided (configured from a 15-bit reload counter, during master operation). Maximum 8 Mbps |
|
External clock input is enabled (during slave operation) | Supports externally clocked slave operation | |
Data Length | 5 to 16, 20, 24, and 32 bits | Data frame size programmable from 4 bits to 32 bits |
Interrupt Request | Reception interrupt
| Not supported |
Reception FIFO interrupt
| Reception FIFO interrupt
| |
Transmission interrupt
| Transmission interrupt
| |
Transmission FIFO interrupt
| Transmission FIFO interrupt
| |
DMA Transfer support function is provided for both transmission and reception | Not supported | |
Status interrupt
| Status interrupt
| |
Serial Chip Select |
|
|
Synchronous Mode | Master or slave function | Master or slave function |
FIFO Option |
|
|
LIN
The TRAVEO™ T2G Family LIN block supports autonomous forwarding of LIN frames. Table 33 lists the main differences.
Table 33. Differences in LIN
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Serial Input | Over sampling is performed by the bus clock 3 times. The reception value is determined by the rule of majority. | 3 times oversample (noise filter) at sample point. |
Transfer Mode | Asynchronous | Asynchronous |
Baud Rate |
|
|
Data Length | 8 bits | 8 bits |
Signaling Method | NRZ | NRZ |
Start Bit Detection | Synchronized with falling edges of the start bit | Synchronized with falling edges of the start bit |
Error Detection |
|
|
Interrupt Request | Reception interrupt
| Reception interrupt
|
Reception FIFO interrupt
| Not supported | |
Transmission interrupt
| Transmission interrupt
| |
Status interrupts
| Status interrupts
| |
Interrupt request to ICU
| Not supported | |
Transmission FIFO interrupt
| Not supported | |
DMA transfer is supported for both transmission and reception. | Not supported | |
LIN Bus Option |
|
|
Wakeup Pulse |
|
|
LIN Transceiver Control |
|
|
UART protocol |
|
|
CAN FD
Table 34 lists the CAN FD features. TRAVEO™ T2G Family shares the message RAM and Timestamp function for global channel control. TRAVEO™ T2G Family supports the receive FIFO top pointer for DMA transfer.
Table 34. Differences in CAN FD
CAN FD | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Classical CAN | Supported | Supported |
CAN FD | Supported | Supported |
TTCAN | Not supported | Supported |
Message Buffer10 |
|
|
Message Handler | 1 | 1 |
Message RAM Access | Direct access | Direct access |
Message RAM | Dedicated type | Shared type |
Message RAM with ECC | Supported | Supported |
Timestamp Function | Supported | Supported
|
Receive FIFO Top Pointer | Not supported | Supported |
I/O Interface
Table 35 lists the I/O interface features. The main differences are the input threshold selection, output drive strength selection, noise filter, and Smart IO.
Table 35. Differences in I/O Interface
I/O Interface | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Input Threshold Selection
| Supported except TTL | Supported |
Output Drive Strength Selection | Supported
| Supported
|
Pull-up/Pull-down | Supported
| Supported
|
High-Z State | Supported | Supported |
Port Status Hold During Low-Power Mode | Supported | Supported |
Noise Filter | Supported per port pin
| Supported per port group
|
Smart IO | Not supported | Supported |
ADC
Table 36 lists the ADC features. The main differences are the result data format, averaging, and pre-conditioning.
Table 36. Differences in ADC
ADC | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
12-bit Resolution | Supported | Supported |
Logical Channel | Supported | Supported |
Software Trigger | Supported | Supported |
Hardware Trigger | Supported | Supported |
Idle Trigger (Continuous) | Supported
| Supported
|
Result Data per Each Channel | Supported
| Supported
|
Result Data Format |
|
|
Programmable Sample Time per Each Channel | Supported
| Supported
|
Comparison Time | ≥ 16 cycles (16-bit register) | 15 cycles (Fixed) |
Range Detection | Supported
| Supported
|
Pulse Detection | Supported
| Supported
|
Averaging | Not supported | Supported |
Group Scan | Supported | Supported |
Preemption Types when Group Interrupted | Supported
| Supported
|
Priority | Supported
| Supported
|
Interrupt | Supported
| Supported
|
DMA Request | Supported | Supported |
Calibration | Supported
| Supported
|
Pre-conditioning | Not supported | Supported
|
Diagnostic Reference Voltage | Supported
| Supported
|
Power Down Mode | Supported | Supported |
Debug Mode | Supported | Supported |
Software Abort | Supported
| Supported
|
RTC
Table 37 lists the RTC features. The main differences are the source clock, interrupts, and the counters of half-second/month/year.
Table 37. Differences of RTC
RTC | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Source Clock | Main clock oscillator (4 MHz) Sub clock oscillator (32 kHz) Internal low speed oscillator (100 kHz) | Watch Crystal oscillator (32 kHz) Internal low speed oscillator (32 kHz) |
Half-second Counter | Supported | Not supported
|
Second Counter | Supported | Supported |
Minute Counter | Supported | Supported |
Hour Counter | Supported | Supported |
Day Counter | Supported | Supported |
Month Counter | Not supported | Supported |
Year Counter | Not supported | Supported |
Automatic Leap Year Correction | Not supported | Supported |
Interrupt | Each counter (Day/Hour/Minute/Second/Half-second) | Two independent alarms (Month + Day + Hour + Minute + Second) |
Calibration | Supported
| Supported
|
CRC
In TRAVEO™ T1G Family, CRC was implemented in a dedicated CRYPT and DMA module.
Item | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series |
---|---|---|
Method | Supported CRC module
| Supported CRYPT module and DMA module
|
CXPI
TRAVEO™ T2G Family has a CXPI module only in CYT2B9 series MCUs.
CXPI supports the following:
- CXPI protocol support in hardware according to ISO/WD 20794-4
- Master node
- Autonomous request field and response transfer processing
- Network access method
- Event-triggered method
- Polling method
- Carrier sense multiple access and collision resolution (CSMA/CR)
- Data signal encoding/decoding format
- Non-return to zero (NRZ) mode
- Pulse width modulation (PWM) mode
- Wake pulse generation
- Clock detection
- 8-bit checksum for normal frame and 16-bit checksum for long frame
- 400x bit time oversampling
- Error detection
- Timeout detection
- Message buffers for the following:
- Protected identifier (PID) field
- Frame information (FI) field
- 16x depth transmission and reception FIFO buffer
- Checksum field
- Test modes include hardware error injection
FlexRay
TRAVEO™ T2G Family has a FlexRay module only in CYT4BF Series MCUs.
FlexRay provides the following functionalities:
- Conformance with FlexRay protocol specification v2.1
- Data rates of up to 10 Mbps on each channel
- Up to 128 message buffers configurable
- 8 KB Message RAM for storage. This can be 128 message buffers with max. 48-bytes data section or up to 30 message buffers with 254-byte data section.
- Configuration of message buffers with different payload lengths possible
- One configurable Receive FIFO
- Each message buffer can be configured as Receive buffer, as Transmit buffer, or as part of the Receive FIFO
- Host access to message buffers via Input and Output Buffer
- Input Buffer: Holds message to be transferred to the Message RAM
- Output Buffer: Holds message read from the Message RAM
- Filtering for slot counter, cycle counter, and channel
- Maskable module interrupts
- Network Management supported
FlexRay consists of the following major six sub-blocks implementing these interfaces:
- FlexRay protocol specification 2.1, and supports up to a 10 Mbps data rate
- CIF MMIO registers
- DMA control
- Synchronization trigger generator
- Decoder acts between the AHB interface and other functional blocks
- AHB slave interface drives the host requests to this FlexRay module
The following interfaces are supported:
- 32-bit AHB-lite interface to the Host processor. Only word (32-bit) transactions are supported. Half-word (16-bit) and byte (8-bit) transactions return bus error responses.
- FlexRay physical layer interface
- Interrupts to the Host processor.
- Trigger interface (DMA and External synchronization)
SDHC Host Controller
TRAVEO™ T2G Family has a SDHC Host Controller module only in CYT4BF Series MCUs.
The SDHC Interface provides the following functionalities:
- Standard compliance:
- SD 6.0 / SDIO 4.10 / eMMC 5.1
- SD SDR50: 50 MB/s (4-bits data @ 100 MHz)
- eMMC 52 MHz DDR: 104 MB/s (8 bits data @ 52 MHz DDR)
- SD 6.0 / SDIO 4.10 / eMMC 5.1
-
- HCI 4.2 (Host Controller Interface) spec shared by SD and eMMC
- AHB master interface
- With ADMA3
- Supports data prefetch for back to back WRITE operations
- With ADMA3
- Single ported RAM for packet storage
- Automatic packing/unpacking of data to fit buffer width
- AHB slave interface for configuration/control/status
Serial Memory Interface
TRAVEO™ T2G Family has a Serial Memory Interface (SMIF) only in CYT4BF Series MCUs.
SMIF provides an SPI master interface to serial memory devices that support a single, dual, or quad SPI protocol. SMIF provides the following functionality:
- HyperBus protocol
- SPI mode 0: clock polarity (CPOL) and clock phase (CPHA) are both ‘0’.
- Support for single, dual and quad SPI protocols.
- Support for dual-quad SPI mode: the use of two quad SPI memory devices to increase data bandwidth for SPI read and write transfers.
- Support for single data rate (SDR) and dual data rate (DDR) transfers.
- Support for up to four external memory devices. Support for device capacities in the range of [64 KB, 4 GB] in power of 2 multiples.
- Execute-in-place (XIP) and memory-mapped input/output (MMIO) operation modes.
- XIP operation mode supports both SPI read and write transfers.
- Support of a 4-KB XIP read cache.
- XIP operation mode supports on-the-fly encryption for write data and on-the-fly decryption for read data.
- SPI interface logic supports stalling of SPI transfers to address back pressure on FIFOs.
- SPI interface logic supports an asynchronous SPI transmit and receive interface clock.
- SPI interface logic supports multiple interface receive clocks.
- SPI interface logic supports flexible external memory devices data signal connections.
Ethernet
TRAVEO™ T2G Family has an Ethernet module only in CYT4BF Series MCUs.
Ethernet provides an interface to an external PHY to get Ethernet functionality. Ethernet provides the following functionality:
- 10, 100, and 1000 Mbps full-duplex operation
- RGMII, RMII, and GMII interfaces supported
- AXI Interface (64-bit)
- Support for up four Tx and 1 Rx Priority queues
- Support for 802.1AS and 1588 precision clock synchronization protocol
- Support for 1588 one-step clock for Tx Sync frames
- Optional IEEE 1588 timestamp unit
- Support for 802.3az EEE
- Support for 802.1Qbb priority-based flow control
- Receive and transmit IP, TCP, and UDP checksum offload
- Automatic pad and CRC generation on transmitted frames
- MDIO interface for PHY management
- Supports 802.1Qav traffic shaping on two highest-priority transmit queues
- Supports strict priority, DWRR, or Enhanced Transmission Selection (ETS - 802.1Qaz) on transmit queues
Development Tools and Flash Programming Tools
TRAVEO™ T1G and TRAVEO™ T2G families supports Green Hills Software (GHS) and IAR tools. In addition to these tools, TRAVEO™ T2G Family also supports the tools from other vendors such as iSystem, Lauterbach, and Segger.
Table 39 lists the main differences between development tools and Flash programming.
Table 39. Development Tools and Flash Programming Tools
Tools | S6J3428/9/A Series | CY2B7/B9, CYT4BF Series | ||
---|---|---|---|---|
Emulators/Probes | Software/Compiler | Emulators/Probes | Software/Compiler | |
Development Tool | GHS Probe | GHS Multi (v2015.1.6 or later) | GHS Probe (5.4.4) | GHS Multi V7 (Version 7.1.4) |
IAR I-JET | EWARM (v7.30.4 or later) | IAR I-JET | EWARM (8.11) | |
– | – | iSystem i-TAG Family | – | |
Lauterbach TRACE 32-ICE | ||||
Flash Programming Tool | GHS Probe | GHS Multi (v2015.1.6 or later) | GHS Probe (5.4.4) | GHS Multi V7 (Version 7.1.4) |
IAR I-JET | EWARM (v7.30.4 or later) | IAR I-JET | EWARM (8.11) | |
Serial Interface Cable (with serial programming mode) | Flash programmer | Cypress MiniProg3 | Cypress Programmer (CYP) | |
Minato | – | Segger J-Link | J-Flash | |
BPM Micro | Segger Flasher Arm (for mass-production) | J-Flash | ||
DTS INSIGHT |
MCAL Support
Table 40 lists MCAL features. The main differences are AUTOSAR revision, compiler, and OCU module.
Table 40. Differences in MCAL Support
MCAL | TRAVEO™ T1G Family | TRAVEO™ T2G Family |
---|---|---|
AUTOSAR Revision | 4.0.3 | 4.2.2 |
Compiler | GHS MULTI V2015.1.6 | GHS MULTI V2017.1.4 |
MCU module | Supported | Supported |
WDG module | Supported | Supported |
GPT module | Supported | Supported |
FLS module | Supported | Supported |
SPI module | Supported | Supported |
LIN module | Supported | Supported |
CAN module | Supported | Supported |
ICU module | Supported | Supported |
PWM module | Supported | Supported |
ADC module | Supported | Supported |
DIO module | Supported | Supported |
PORT module | Supported | Supported |
OCU module | Not supported | Supported |
Cluster Products
Target Products and TRAVEO™ T2G Family MCU Features
MCU Family | MCU Series |
---|---|
TRAVEO™ T1G Family | S6J3200 series |
TRAVEO™ T2G Family | CYT4DN series, CYT2C9 series |
Function | TRAVEO™ T1G Family | TRAVEO™ T2G Family | |
---|---|---|---|
S6J3200 Series | CYT4DN Series | CYT2C9 Series | |
Flash Memory (Code Flash) | 2112 KB | 6336 KB | 2112 KB |
Flash Memory (Work Flash) | 112 KB | 128 KB | 128 KB |
SRAM0 | 256 KB | 256 KB | 256 KB |
SRAM1 | – | 256 KB | – |
SRAM2 | – | 128 KB | – |
Not Supported | Supported | Supported | |
Graphics Interface | Video output
Video input
Graphics Engine
| Video output
Video input
Graphics Engine
| Not Supported |
Audio | I2S x2 Not Supported TDM PCMPWM x2 Sound Generator x1, Sound Waveform Generator x1 Mixer x5 Audio DAC x1 | I2S x4 TDM x4 PCMPWM x2 Sound Generator x1 Mixer x2 Audio DAC x1 | I2S x2 TDM x2 PCMPWM x1 Sound Generator x5 Mixer x1 Not Supported Audio DAC |
Supported (HSSPI, HyperBus) | Supported | Not Supported | |
Supported | Supported | Not Supported | |
Supported | Not Supported | Supported |
Product Overview
Figure 11 show the major architecture components of the CYT4DN series.
Figure 11. Block Diagram (CYT4DN Series)
On-chip System Features
CPU
TRAVEO™ T1G Family has a single Cortex-R5 processor, while TRAVEO™ T2G Family is a dual-processing CPU (two Cortex-M7s and a Cortex-M0+ processor). In TRAVEO™ T2G Family, dual-processing CPUs are configured as the CPU subsystem; two Cortex-M7 processors are the main CPU and Cortex-M0+ processor is the secondary CPU that can implement security, safety, and protection features. Note that as the CPU core changes, MCU features change according to the core specification.
Item | TRAVEO™ T1G Family (S6J3280 Series) | TRAVEO™ T2G Family (CYT4DN Series) | Remarks | |
---|---|---|---|---|
Main CPU | Secondary CPU | |||
CPU Core | Cortex-R5F | Cortex-M7 (x2) | Cortex-M0+ | |
Operation Frequency | Up to 240 MHz | Up to 320 MHz | Up to 100 MHz | Product specifications |
FPU | Single/Double precision | Single/Double precision | None | |
MPU | 16 regions | 16 regions | 8 regions | 11 |
Cache Memory | I-cache 16 KB/D-cache 16 KB | I-cache 16 KB/D-cache 16 KB | None | |
TCM Interface | Supported Implemented TCRAM | Supported | Not supported | |
Support for Interrupt Controller | Vector Interrupt Controller (VIC), Software nested interrupt | Nested Vector Interrupt Controller (NVIC) |
Memory Design
Table 44 lists the Code Flash features. The main differences are in program size, Read-While-Write operation, and redundancy.
Table 44. Differences in Code Flash
Code Flash | S6J3280 Series | CYT4DN Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Sector Size | 64 KB, 8 KB | 32 KB, 8 KB |
Program Size | 8 bits, 16 bits, 32 bits, 64 bits | 64 bits, 256 bits, 4096 bits |
Program and Erase Cycles/Retention | 1000/20 years | 1000/20 years |
Read-While-Write Operation | Not supported | Supported |
Table 45 lists the Work Flash features. The main differences are in the sector size, program and erase cycles, Read-While-Write operation, and redundancy. Comparing with TRAVEO, TRAVEO™ T2G families supports smaller sector size and higher program and erase cycles.
Table 45. Differences in Work Flash
Work Flash | S6J3280 Series | CYT4DN Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Sector Size | 4 KB | 2 KB, 128 B |
Program Size | 32 bits | 32 bits |
Program and Erase Cycles/Retention | 1000/20 years 10000/10 years 100000/5 years | 125000/20 years 250000/10 years |
Read-While-Write Operation | Not supported | Supported |
Table 46 lists the SRAM features. The main difference is the data retention in low power mode. TRAVEO™ T2G Family supports data retention in DeepSleep mode.
Table 46. Differences in SRAM
SRAM | S6J3280 Series | CYT4DN Series |
---|---|---|
ECC | SEC/DED | SEC/DED |
Data Retention in Low Power Mode | Not supported (TCRAM and SRAM are not retained in Shutdown mode. Backup RAM is retained in Shutdown mode) | Supported (SRAM is retained in DeepSleep mode) |
Debug
TRAVEO™ T1G and TRAVEO™ T2G families support JTAG and SWD Debug Interface. Table 47 shows the main differences in debugging.
Table 47. Differences in Debugging
Item | S6J3280 Series | CYT4DN Series |
---|---|---|
Debug interface | JTAG | JTAG SWD |
Mode Setting
This section is as same as the Body Entry/High Products. See section 2.3.4 Mode Setting.
Power Supply and Monitoring
The power supply of TRAVEO™ T2G Family is the same as that of TRAVEO™ T1G Family, but signal names of power supply are different. Also, the type of power monitoring mode has been enhanced in TRAVEO™ T2G Family.
Power Supply
Table 48 lists the power supply and differences in functionality.
Table 48. Power Supply
Power Supply | S6J3280 Series | CYT4DN Series | |||
---|---|---|---|---|---|
External | Digital | VCC5 | 4.5 to 5.5 V | VDDD | 2.7 to 5.5 V |
VCC12 | 1.1 to 1.3 V | VCCD | 1.09 to 1.21 V | ||
I/O | VCC53 | 3.0 to 3.6 V/4.5 to 5.5 V | VDDIO_GPIO | 2.7 to 5.5 V | |
DVCC | 4.5 to 5.5 V | VDDIO_SMC | 2.7 to 5.5 V | ||
VCC3 | 3.0 to 3.6 V | VDDIO_HSIO , VDDIO_SMIF_HV | 3.0 to 3.6 V | ||
VDDIO_SMIF | 1.7 to 2.0 V | ||||
Analog | AVCC3_DAC | VDDHA_FPD0 , VDDHA_FPD1 | 3.0 to 3.6 V | ||
VCC3_LVDS_Tx | VDDA_FPD0 , VDDA_FPD1 | 1.09 to 1.21 V | |||
VCC3_LVDS_PLL | VDDPLL_FPD0 , VDDPLL_FPD1 | 1.09 to 1.21 V | |||
VDDA_MIPI | 1.09 to 1.21 V | ||||
AVCC5 | AVCC5 | VDDA_ADC | 2.7 to 5.5 V |
Monitoring
This section is as same as the Body Entry/High Products. See section 2.3.5.2 Monitoring.
Reset Factor
This section is as same as the Body Entry/High Products. See section 2.3.6 Reset Factor.
Clock System
Compared to the TRAVEO™ T1G Family clock system, TRAVEO™ T2G Family has Spread Spectrum Clock Generator (SSCG). TRAVEO™ T2G Family does not have Clock Gear functions. In TRAVEO™ T2G Family, frequency-locked loop (FLL) featuring fast startup and low power is implemented. LPECO that operates in DeepSleep and Hibernate mode is added. Table 49 lists the main differences in the clock system.
See the datasheet for the AC characteristics of each clock.
Table 49. Differences in Clock System
Clock System | S6J3200 Series | CYT4DN Series | CYT2C9 Series | |
---|---|---|---|---|
Internal Clock Source | Fast CR: 4 MHz(Using source clock after reset) Slow CR: 100 kHz | IMO: 8 MHz(Using source clock after reset) ILO0/1: 32 kHz | IMO: 8 MHz(Using source clock after reset) ILO0/1: 32 kHz | |
External Clock Source | Main clock: 3.6 to 16 MHz Sub clock: 32.768 kHz | ECO: 3.988 to 33.33 MHz WCO: 32.768 kHz LPECO: 4 to 8MHz EXT_CLK : 0.25 to 100 MHz | ECO: 3.988 to 33.33 MHz WCO: 32.768 kHz LPECO: 4 to 8MHz EXT_CLK12 : 0.25 to 100 MHz | |
High-Speed Clock Generation | PLL | PLL x4 Input: 3.6 to 32 MHz Output: max. 400 MHz (PLL1) SSCG PLL x4 Input: 3.6 to 32 MHz Output: max. 400 MHz (SSCG3) | PLL without SSCG x3 Input: 3.988 to 33.34 MHz Output: max. 200 MHz PLL with SSCG x5 Input: 3.988 to 33.34 MHz Output: max. 400 MHz | PLL without SSCG x2 Input: 3.988 to 33.34 MHz Output: max. 200 MHz PLL with SSCG x1 Input: 3.988 to 33.34 MHz Output: max. 400 MHz |
FLL | Not implemented | FLL x1 Input: 0.25 to 80 MHz Output: 24 to 100 MHz | FLL x1 Input: 0.25 to 80 MHz Output: 24 to 100 MHz | |
Clock Gear | Supported | Not implemented | Not implemented | |
Clock Supervision | Main clock Sub clock PLL clock SSCG clock Slow CR Fast CR | CLK_REF (IMO or ECO or EXT_CLK) CLK_HF (PLL and FLL) ILO0 CLK_LF (ILO1 or WCO) | CLK_REF (IMO or ECO or EXT_CLK) CLK_HF (PLL and FLL) ILO0 CLK_LF (ILO1 or WCO) |
12 It can be sourced from a designated I/O pin.
Watchdog Timer
The watchdog timer (hardware) features are same as the features listed in Table 13.
Table 50 lists the multi-counter watchdog timer (software) features. The main differences are counter clock, counter, maximum timeout, and the behavior during debugging.
Table 50. Differences in Multi-Counter Watchdog Timer (Software)
Multi-counter Watchdog Timer (Software) | S6J3280 Series | CYT4DN Series |
---|---|---|
Trigger | User program | User program |
Counter Clock |
|
|
Counter | 32 bits | 2 * 16-bit, 32 bits only for interrupt |
Maximum Timeout | 36.4 hours | 2.11 seconds |
Window Function | Supported | Supported |
Warning Interrupt | Supported | Supported |
Timeout Expiration Action | Reset or NMI | Reset or Fault |
Behavior During Low-Power Mode | Can select stop/run by register | Can select stop/run by register |
Behavior During Debugging | Stop at debugging state | Can select stop/run by register |
Low Power Mode
This section is as same as the Body Entry/High Products. See section 2.3.9 Lower Power Mode.
Interrupt Structure
This section is as same as the Body Entry/High Products. See section 2.3.10 Interrupt Structure.
Data Transfer
This section is as same as the Body Entry/High Products. See section 2.3.11 Data Transfer .
TPU
This section is as same as the Body Entry/High Products. See section 2.3.12 TPU.
Fault Report
This section is as same as the Body Entry/High Products. See section 2.3.13 Fault Report.
Protection
The Protection function of TRAVEO™ T1G Family consists of the CPU’s Memory Protection Unit (MPU), DMA’s MPU, and Peripheral Protection Unit (PPU). TRAVEO™ T2G Family consists of MPU, Shared Memory Protection Unit (SMPU), and PPU. Table 51 lists the main differences in Protection Units.
In TRAVEO™ T2G Family, memory protection is provided by MPU and SMPU. MPU is implemented as part of the CPU and bus infrastructure. P-DMA, M-DMA, and encrypted components do not have MPU. Instead, they inherit the access control attributes of programmed bus transfer.
SMPU is shared by all masters; PPU is a protection unit for peripheral registers.
TRAVEO™ T2G Family supports a new protection attribute (Secure/Non-secure), and protection contexts. Protection contexts can change the access restriction without changing the setting of the protection unit.
For more details, see the Technical Reference Manual.
Table 51. Differences in Protection Configuration and Access Attribute
Item | S6J3280 Series | CYT4DN Series | Remarks |
---|---|---|---|
MPU implemented in the CPU | Cortex-R5: 16 Regions Access Attribute:
| Cortex- M0+: 8 Regions Cortex-M7: 16 Regions Access Attribute:
| |
MPU implemented in the bus infrastructure | Not supported | 16 Regions Access Attribute:
| For external master such as debugger |
SMPU | Not supported | 16 Regions Access Attribute:
| |
PPU | Access Attribute:
| Access Attribute:
| |
MPU16-AHB | Access Attribute:
| Not supported. DMA access protection is provided by SMPU and PPU. |
Boot Process
This section is as same as the Body Entry/High Products. See section 2.3.15 Boot Process .
Security
This section is as same as the Body Entry/High Products. See section 2.3.16 Security .
11 TRAVEO™ T2G has SMPU as memory protection in addition to the CPU's internal MPU. Refer to Protection.
12 It can be sourced from a designated I/O pin.
Peripherals
Timer
This section is as same as the Body Entry/High Products. See section 2.4.1 Timer.
Serial Communication Block
UART
This section is as same as the Body Entry/High Products. See section 2.4.2.1 UART .
I2C
This section is as same as the Body Entry/High Products. See section 2.4.2.2 I2C .
SPI
This section is as same as the Body Entry/High Products. See section 2.4.2.3 SPI .
LIN
This section is as same as the Body Entry/High Products. See section 2.4.2.4 LIN .
CAN FD
This section is as same as the Body Entry/High Products. See section 2.4.3 CAN FD.
I/O Interface
Table 52 lists the I/O interface features. The main differences are the input threshold selection, output drive strength selection, noise filter, and Smart IO.
Table 52. Differences in I/O Interface
I/O Interface | S6J3280 Series | CYT4DN Series |
---|---|---|
Input Threshold Selection
| Supported except TTL | Supported |
Output Drive Strength Selection | Supported
| Supported
|
Pull-up / Pull-down | Supported
| Supported
|
High-Z State | Supported | Supported |
Port Status Hold during Low-Power Mode | Supported | Supported |
Noise Filter | Supported per port pin
| Supported per port group
|
Smart IO | Not supported | Supported |
ADC
This section is as same as the Body Entry/High Products. See section 2.4.5 ADC.
RTC
Table 53 lists the RTC features. The main differences are the source clock, interrupts, and the counters of half-second/month/year.
Table 53. Differences of RTC
RTC | S6J3280 series | CYT4DN Series |
---|---|---|
Source Clock | Main clock oscillator (4 MHz) Sub clock oscillator (32 kHz) Internal low speed oscillator (100 kHz) | Watch Crystal oscillator (32 kHz) Internal low speed oscillator (32 kHz) Low Power External Clock oscillator |
Half-second Counter | Supported | Not supported
|
Second Counter | Supported | Supported |
Minute Counter | Supported | Supported |
Hour Counter | Supported | Supported |
Day Counter | Supported | Supported |
Month Counter | Not supported | Supported |
Year Counter | Not supported | Supported |
Automatic Leap Year Correction | Not supported | Supported |
Interrupt | Each counter (Day/Hour/Minute/Second/Half-second) | Two independent alarms (Month + Day + Hour + Minute + Second) |
Calibration | Supported
| Supported
|
CRC
This section is as same as the Body Entry/High Products. See section 2.4.7 CRC.
CXPI
TRAVEO™ T2G Family has a CXPI module in CYT4DN and CYT2C9 series MCUs.
CXPI supports the following:
- CXPI protocol support in hardware according to ISO/WD 20794-4
- Master node
- Autonomous request field and response transfer processing
- Network access method
- Event-triggered method
- Polling method
- Carrier sense multiple access and collision resolution (CSMA/CR)
- Data signal encoding/decoding format
- Non-return to zero (NRZ) mode
- Pulse width modulation (PWM) mode
- Wake pulse generation
- Clock detection
- 8-bit checksum for normal frame and 16-bit checksum for long frame
- 400x bit time oversampling
- Error detection
- Timeout detection
- Message buffers for the following:
- Protected identifier (PID) field
- Frame information (FI) field
- 16x depth transmission and reception FIFO buffer
- Checksum field
- Test modes include hardware error injection
Serial Memory Interface
TRAVEO™ T2G Family has SMIF only in CYT4DN Series MCUs.
SMIF provides an SPI master interface to serial memory devices that support a single, dual, or quad SPI protocol. SMIF provides the following functionalities:
- HyperBus protocol
- SPI mode 0: clock polarity (CPOL) and clock phase (CPHA) are both ‘0’.
- Support for single, dual, and quad SPI protocols.
- Support for dual-quad SPI mode: use of two quad SPI memory devices to increase data bandwidth for SPI read and write transfers.
- Support for single data rate (SDR) and dual data rate (DDR) transfers.
- Support for up to four external memory devices. Support for device capacities in the range of [64 KB, 4 GB] in power of 2 multiples.
- Execute-in-place (XIP) and memory-mapped input/output (MMIO) operation modes.
- XIP operation mode supports both SPI read and write transfers.
- Support of a 4-KB XIP read cache in AHB-Lite Bus.
- XIP operation mode supports on-the-fly encryption for write data and on-the-fly decryption for read data.
- SPI interface logic supports stalling of SPI transfers to address back pressure on FIFOs.
- SPI interface logic supports an asynchronous SPI transmit and receive interface clock.
- SPI interface logic supports multiple interface receive clocks.
- SPI interface logic supports flexible external memory devices data signal connections.
- Supports Data Learning Pattern (DLP) function.
Ethernet
TRAVEO™ T2G Family has an Ethernet module only in CYT4DN Series MCUs.
Ethernet provides an interface to an external PHY to get Ethernet functionality. Ethernet provides the following functionalities:
- 10, 100, and 1000 Mbps full-duplex operation
- RGMII, RMII, and GMII interfaces supported
- AXI Interface (64-bit)
- Support for up four Tx and 1 Rx Priority queues
- Support for 802.1AS and 1588 precision clock synchronization protocol
- Support for 1588 one-step clock for Tx Sync frames
- Optional IEEE 1588 timestamp unit
- Support for 802.3az EEE
- Support for 802.1Qbb priority-based flow control
- Receive and transmit IP, TCP, and UDP checksum offload
- Automatic pad and CRC generation on transmitted frames
- MDIO interface for PHY management
- Supports 802.1Qav traffic shaping on two highest-priority transmit queues
- Supports strict priority, DWRR, or Enhanced Transmission Selection (ETS - 802.1Qaz) on transmit queues
Graphics Interface
Table 54 lists the Graphics interface features. TRAVEO™ T1G Family comes with highly-efficient 2D/3D graphics engines. TRAVEO™ T2G Family supports a 2D graphics engine. Both TRAVEO™ T1G and TRAVEO™ T2G families have features with advanced feature-sets for memory saving, safety, and high image quality to help manufacturers take advantage of the lower overall system costs.
Table 54. Differences in Graphics Interface
Item | S6J3280 Series | CYT4DN Series |
---|---|---|
RSDS output | 1 unit available | Not available |
LVDS (FPD-Link) output | 1 unit available | 2 units available single (max display size: 1920 x 720) or 1 unit available dual (max display size is 2880 x 1080) |
DRGB output | 2 units available | 2 units available |
ITU656, YUV, RGB video input | 1 unit available | 1 unit available |
MIPI CSI-2 video input | Not available | 1 unit available |
MediaLB | 1 unit available | Not available |
Ethernet AVB | 1 unit available | 1 unit available |
Graphics Engine | 2D graphics engine (2.5D effects) 3D graphics engine | 2D graphics engine (2.5D effects) |
VRAM | 2048 KB | 4096 KB |
Audio Interface
Table 55 lists the Audio interface features. Both TRAVEO™ T1G and TRAVEO™ T2G families support Sound Processing.
Table 55. Differences in Audio Interface
Item | TRAVEO™ T1G Family (S6J3200 Series) | TRAVEO™ T2G Family (CYT4DN Series) |
---|---|---|
PCMPWM | 1 unit available | 2 units available |
TDM | Not Supported | 4 time-division multiplexing (TDM) Interface available |
SG | 1 unit available | 1 unit available |
SWFG | 1 unit available | Not available |
Mixer | 2 units available | 2 units available |
Audio DAC | Stereo 1ch available | Stereo 1ch available |
I2S | 2 units available | 4 units available |
LCD Controller
TRAVEO™ T1G Family S6J3200 Series and TRAVEO™ T2G Family CYT2C9 Series have an LCD controller. Table 56 lists the differences in LCD Controller.
Table 56. Differences in LCD Controller
Item | S6J3200 Series | CYT2C9 Series |
---|---|---|
Segments | Up to 32 segments (SEG) | Up to 32 segments (SEG) |
Commons | 4 commons (COM) | 4 commons (COM) |
Configurable Pin Assignment | Not Supported | Any GPIO pin can be configured as either COM or SEG. |
Power Efficient Waveform | Not Supported | Type A (standard) and Type B (low-power) |
Duty Drive | Duty Selection: 1/2, 1/3, and 1/4 Bias Selection: 1/2 and 1/3 | Duty Selection: 1/2, 1/3, and 1/4 Bias Selection: 1/2, 1/3, and Digital correlation |
Static Drive | Supported | Not Supported |
Device Power Modes | RUN/PSS timer | Active/Sleep/DeepSleep |
Digital Contrast Control | Not Available | Available |
Development Tools and Flash Programming Tools
This section is as same as the Body Entry/High Products. See section 2.5 Development Tools and Flash Programming Tools.
MCAL Support
This section is as same as the Body Entry/High Products. See section 2.6 MCAL Support.
Related Documents
Body Entry/High Products:
TRAVEO™ T1G Family series datasheets and hardware manuals:
- S6J3400 Series Datasheet
- S6J3 40 0 Series Hardware Manual
- TRAVEO™ T1G Family Hardware Manual Platform Part for S6J3400 Series
TRAVEO™ T2G Family series datasheets and technical reference manuals:
- Device datasheet (Contact Technical Support)
- CYT2B7 Datasheet 32-Bit Arm® Cortex®-M4F Microcontroller TRAVEO™ II Family
- CYT2B9 Datasheet 32-Bit Arm® Cortex®-M4F Microcontroller TRAVEO™ II Family
- CYT4BF Datasheet 32-Bit Arm® Cortex®-M7 Microcontroller TRAVEO™ II Family
- CYT3BB/4BB Datasheet 32-Bit Arm® Cortex®-M7 Microcontroller TRAVEO™ II Family
- Body Controller Entry Family (Contact Technical Support)
- TRAVEO™ II Automotive Body Controller Entry Family Architecture Technical Reference Manual (TRM)
- TRAVEO™ II Automotive Body Controller Entry Registers Technical Reference Manual (TRM) for CYT2B7
- TRAVEO™ II Automotive Body Controller Entry Registers Technical Reference Manual (TRM) for CYT2B9
- Body Controller High Family (Contact Technical Support)
- TRAVEO™ II Automotive Body Controller High Family Architecture Technical Reference Manual (TRM) for CYT4BF
- TRAVEO™ II Automotive Body Controller High Registers Technical Reference Manual (TRM) for CYT3BB/4BB
Cluster Products:
TRAVEO™ T1G Family series datasheets and hardware manuals:
- S6J3200 Series Datasheet
- S6J3200 Series Hardware Manual
- TRAVEO™ T1G Family Hardware Manual Platform Part for S6J3200 Series
TRAVEO™ T2G Family series datasheets and technical reference manuals:
- Device datasheet (Contact Technical Support)
- CYT4DN Datasheet 32-Bit Arm® Cortex®-M7 Microcontroller TRAVEO™ II Family
- Cluster 2D Family (Contact Technical Support)
- TRAVEO™ II Automotive Cluster Family Architecture Technical Reference Manual (TRM)
- TRAVEO™ II Automotive Cluster Registers Technical Reference Manual (TRM)
Attention:
Revision history
Document version | Date of release | Description of changes |
---|---|---|
** | 2017-12-19 | New application note. |
*A | 2019-02-20 | Added items shown below: Figure 2 and Figure 3 of the Section “2.1. Block Diagram”, Section “2.1 Features Specific Functions of TRAVEO™ T2G Family MCUs”, Section “4.8 CXPI” and Part Numbers of CYT2B9 Series MCU, Section “4.9 FlexRay”, “4.10 Secure Digital Host Controller”, “4.11 Serial Memory Interface”, “4.12 Ethernet” and Part Numbers of CYT4BF Series MCU |
*B | 2019-08-08 | Added Cluster Products Specifications. |
*C | 2020-03-23 | Added items shown below: TRAVEO™ T2G Family Cluster Products of the “Table 1. MCU List for Comparison”. Expanded Target Products for Cluster Entry series following tables at “3. Cluster Products”: Table 41. Target Products, Table 42. Comparison of TRAVEO™ T1G and TRAVEO™ T2G Family MCUs, and Table 48. Differences in Clock System. |
*D | 2021-03-18 | Updated to Infineon template. |
*E | 2023-11-10 | Updated template; no content update. |
1 TRAVEO™ T2G family has SMPU as memory protection in addition to the CPU’s internal MPU. Refer to Protection.
2 Programmable Trip point (2 points)
3 Fixed Trip point
4 Reset or Fault report can be selected
5 It can be sourced from a designated I/O pin
6 System Interrupts are interrupts generated from peripheral functions and external inputs. For the list of system interrupts supported by the device variants, see the following documents:
- TRAVEO™ T1G Family: Hardware Manual by the device variants.
- TRAVEO™ T2G Family: Architecture Technical Reference Manual by the device variants.
7 For the list of system interrupts supported by the device variants, see the Technical Reference Manual.
8 The external clock cannot be used as the timer's count clock. However, when the count event is used in the rising edge (supported falling and both edge) detection mode, the timer will count with count event detection. In this case, the count event can be used as the external clock.
9 Counters can be pre-loaded with values reflecting the desired phase shift and then started synchronously. Note that during the initial (start delay) period, some counters can already generate the PWM output, depending on the duty cycle.
10 For TRAVEO™ T1G and TRAVEO™ T2G the listed numbers indicate the maximum addressable message buffers; utilization depends on available MRAM size.
11 TRAVEO™ T2G has SMPU as memory protection in addition to the CPU's internal MPU. Refer to Protection.
12 It can be sourced from a designated I/O pin.