USB EZ-PD™ Type-C Forum Discussions

I want to analyze the messages that occur during mobile charging with a charger that supports PPS.

ALERT, GET_STATUS, STATUS messages were confirmed like attachments.

The mobile charging operation is repeatedly charged and blocked.

I would like to confirm the cause of the incorrect charge with that message.

Please tell me the solution or the cause of the message.

Hi

I'm going to use a dp application.

There seems to be a problem between DP to HDMI and CYPD3125.

DP CHIP fails when connected to CYPD3125.

DP CHIP works normally.

As HPD is detected, communication with CYPD3125 seems to be poor.

Can we see why this is happening?

Hi All,

In the production process, our products need to be burned in batches and verified under different voltages, so miniPROG4 is not suitable for use. Segger can be used as a product burner. Therefore, how to make J-Link support CCG5 product burning?

BTW, I find a similar solution in :https://community.infineon.com/t5/USB-EZ-PD-Type-C/How-do-I-use-Jlink-to-program-CCG4-HEX-file-into-chip/td-p/113955?start=0&tstart=0 ,Does this also apply to CCG5? 

As we known, CCG3PA (3171) get TID and pass - pd compliance test.

Could you please provide us the Test Report and Eye diagram?

I am working with a CYPD6125 and am trying to use the SBU1 and SBU2 pins as a side band communications channel between two devices.  I see a few mentions in the CYPD6125 TRM that the chip contains an SBU mux that can be set so that the AUX_P and AUX_N pins are connected to the SBU pins.  However, I have not been able to find any support or examples showing how to configure that mux.

What functions or registers should I be using to set the SBU pins to be driven by the AUX pins, and is there a document or sample project that details how to use them?

Hi,

I'm in need of wiring out an extra (full speed usb) via a type-c port managed by a CCG5.

Is it safe to route a USB signal via the UART_TX_P2 (H11/J11) to the outside DPLUS/MINUS pins?

the alternative would be to use SBU1/2 and route AUX_P/_N as a debug output

didn't manage to find any electrical spec on those pins from an usb signal perspective

Hi all, 

I am studying through the CCG3 USB-C to DisplayPort Cable Solution for designing USB-C to DP cable using DP Alt-mode.

In description of the solution, it can be applied for Alt-mode standard's scenarios 2a(Source/USB-C to Sink/DP) and 2b(Source/DP to Sink/USB-C) and I have question about it.

- If I use CCG3(CYPD3120), is there difference of the firmware code between scenarios 2a and 2b? or Can I apply same configuration for both scenario 2a and 2b?

Because, I am just studying the USB-C to DP cable with an example of scenario 2a (Source/USB-C to Sink/DP) and I couldn't find some application like USB-C to DP Adapter for scenario 2b(Source/DP to Sink/USB-C) yet. So I am wondering if the same firmware code can be applied for both 2a and 2b.

Thank you.

Best Regards,

Hyunjun

Hello,

I may have missed something obvious but cant seem to find the EZ-PD SDK 3.0.2 download as mentioned in

https://www.infineon.com/cms/en/design-support/tools/sdk/usb-controllers-sdk/ez-pd-host-software-development-kit/?utm_source=cypress&utm_medium=referral&utm_campaign=202110_globe_en_all_integration-software

I am building an application based on the charge through dongle app note, but need to customize the operation of the ccg3. It appears like the EZ-PD SDK 3.0.2 has the necessary examples for both the CCG3 and CCG2, but I cant seem to find that specific version or a reference to an updated version.

As I understand the "host SDK" version is not the correct version, and it cannot do ccg2

Previous Post:

"CCG7 Samples have arrived, now we need Firmware

we actually need 88-Watts per port out of it, so what do we need to do to enable Vconn and Cable Discovery"

CYPD7291-68LDXS_rsc was provided to us to test our board based on your reference schematic, our application requires Vconn to be turned on in code and in config utility

please help

P.S we know how to use the configure utility since 2017 so can only assume vconn support is not turned on in the code of the compiled hex that was provided to us