Version: **
Reference hardware designs of Tiger Lake platfrom for new notebooks/desktops are based on EZ-PD™ CCG5. Currently, the latest compliance test suites need firmware updates for CCG5.
This KBA describes how to pass latest compliance tests and enable the CCG6DF/SF device to work with the Tiger Lake platform. After you make the following hardware changes from CYPD5225 to CYPD6227/CYPD6228, the firmware binaries (CYPD6227-96BZXI_notebook_tgl.hex) generated by the EZ-PD™ Host SDK 3.5 example code can be used directly with the test suite.
Table 1 lists differences in device resources (hardware and firmware) between CCG5 and CCG6DF.
Table 1 Hardware and firmware features between CCG5 and CCG6DF
|
HW/FW |
Features |
CCG5 (2-port) |
CCG6DF (2-port) |
|
HW |
Package |
96-BGA (6*6 mm: 36 mm2) |
96-BGA (6*6 mm: 36 mm2) |
|
Power Delivery support |
Yes (Thunderbolt) |
Yes (Thunderbolt) |
|
|
MUX (SBU, SS, or HS) |
SBU and High Speed |
High Speed |
|
|
20-V protection on SBU/CC |
Yes |
Yes |
|
|
Includes BC1.2 Source or Sink |
BC1.2 Source only |
No |
|
|
VBUS Consumer path gate driver |
PFET |
NFET, OVP, S/R |
|
|
VBUS Provider load switch - VBUS RCP, SCP, OCP, OVP, and programmable slew rate control |
No |
Yes Improved SCP performance |
|
|
VBUS OCP current sense resistor |
10 mΩ |
5 mΩ |
|
|
VCONN RDS (on)/OCP limit |
1.5 Ω/440 mA-600 mA |
0.7 Ω/550 mA – 750 mA |
|
|
GPIOs/I2C interface |
28/4 |
23/4 |
|
|
FW |
Embedded Controller (EC) FW compatibility and USB Type-C Connector System Software Interface (UCSI) support |
Yes |
Yes |
|
Flash/RAM/ROM |
128/12/8 KB |
64/16/96 KB |
|
|
Extra ROM with stable PD code to free up flash |
No |
Yes |
|
|
Signed FW download |
No |
Yes |
|
|
Secured boot |
No |
Yes |
|
|
System Policy Manager |
No |
Yes |
|
|
USB Type-C authentication |
No |
Yes |
Based on these differences, you need to make the following hardware changes in the original reference design based on CCG5:
- Remove CCG5’s VBUS Provider path and use the internal integrated VBUS FETs of CCG6DF. CCG6DF offers short-circuit protection (SCP) and reverse current protection (RCP) benefits with this change.
- Pay attention to the hardware resources: current sense resistor for overcurrent protection (OCP), SCP, and RCP. The VBUS OCP current sense resistor uses 10 mΩ for CCG6DF. Load the RCP capacitance (shown in green box in Figure 1) to CSP_P (shown in red box in Figure 1) at each port of the CCG6DF design.
Figure 1 Rsense and RCP capacitance placement on CCG6DF schematic
- CCG6DF integrates only the HS switch; SBU crossbar is not integrated. If the CCG6DF design is intended to support USB4, Thunderbolt, or both, no additional components are required. However, an SBU mux is required if the CCG5 design was targeted at supporting only USB3 and DisplayPort Alt Mode.
- Change the VBUS FETs on the VBUS Consumer path from P-MOS FET for CCG5 to N-MOS FET for CCG6DF (see Figure 2).
Figure 2 VBUS Consumer schematic
- See the following pinout considerations in the CCG6DF design:
1) CCG6DF pins connected to EC:
|
CCG6DF pins |
Can be re-routed? |
|
D11 - I2C_SCL_SCB0/P4.0 |
No |
|
C11 - I2C_SDA_SCB0/P4.1 |
No |
|
F11 - I2C_INT_EC/P1.2 |
No |
2) CCG6DF pins connected to Tiger Lake:
|
CCG6DF pins |
Can be re-routed? |
|
H7 - I2C_SCL_SCB1/P0.3 |
No |
|
K9 - I2C_SDA_SCB1/P0.2 |
No |
|
L9 - I2C_INT_TBT_P0/P0.4 |
Yes, firmware supports re-routing |
|
H8 - I2C_INT_TBT_P1/P0.5 |
Yes, firmware supports re-routing |
3) CCG6DF pins connected to BB re-timer:
|
CCG6DF pins |
Can be re-routed? |
|
E10 - I2C_SCL_SCB2/P2.2 |
No. |
|
E11 - I2C_SDA_SCB2/P2.1 |
No. |
|
D10 - RETIMER_PWR_EN_P1/P2.4 |
Yes, firmware supports re-routing |
|
K6 - RETIMER_PWR_EN_P2/P0.1 |
Yes, firmware supports re-routing |
|
E8 - RETIMER_RESET_N_P1/P2.3 |
Yes, firmware supports re-routing |
|
L4 - RETIMER_RESET_N_P2/P0.0 |
Yes, firmware supports re-routing |
|
G8 - RETIMER_FORCE_PWR_EN/P1.1 |
Yes, firmware supports re-routing |