USB EZ-PD™ Type-C Forum Discussions

I brought a CY4521 kit from Cypress store, and got it today. The Order number is 1383701. I try to test my FW which modify from CYPD2122-24LQXI_notebook project, I programming my FW by EZ-PD Configuration Utility several times without problem, but the last time the programming was fail and interrupted, I don't know the reason why, there are not any hardware issue like USB cable unpluged or loss power when programming FW. After that, the EZ-PD Configuration Utility can not find CY4521 anyway that I cannot program CY4521. I try press reset button and re-power to CY4521, but the EZ-PD Configuration Utility still can not find CY4521, this CY4521 might be malfunction, please help me fix this problem, or this CY4521 need to RMA? This is very serious and urgent, I can not develop my FW without CY4521, please Cypress help me fix this problem.

Does Cypress have any USB Power Delivery examples or Reference Designs that utilize Analog Devices components?

Greg

Community Post Getting Started with Cypress USB Type-C Products - KBA204071 states, "Cypress provides limited support for CCG1 and CCG2 controllers, and does not recommend their use in new designs."

If NRND (Not Recommended for New Designs), please update product selection websites and datasheets.

--Main USB Type-C and Power Delivery @ https://www.cypress.com/products/usb-type-c-and-power-delivery promotes both CCG1 and CCG2.

--EZ-PD CCG2 Type-C Port Controller website @ https://www.cypress.com/products/ez-pd-ccg2-type-c-port-controller  has "New Update" and NO indication the part is NRND.

--EZ-PD CCG2 Datasheet @ https://www.cypress.com/documentation/datasheets/ez-pd-ccg2-datasheet-usb-type-c-port-controller provides NO indication of NRND.

If CCG2 is still supported for new designs, is there a clean example to program a CCG2 with PSoC Creator?

I understand the components in the examples from Creator need updating

I'm not clear what to do with a missing -lusbpd_gcc after updating components and running a Clean and Build.

Community Post Psoc creator 4.0: Build error: cannot find -lusbpd_gcc indicates to change toolchain but doesn't provide a location for firmware binaries

Community Post ERROR: The command 'arm-none-eabi-gcc.exe' failed with exit code '1'. Chanage toolchain? disputes the need to change toolchain and indicates there are C coding issues in the files

Greg

What causes VBUS_C_CTRL_P1 to remain high after the USB-c cable is removed?  We have designed a test board, and this signal goes high when a USB cable is inserted, and stays High after removal.

Hi,

My project has to use the recovery mode for VBUS. The project is based on the reference SDK project CYPD3120-40LQXI_dp_dongle.

The CYPD3123 is powered all the time and the high-side MOSFET switch is turned off so the VBUS has no power before Samsung is plugged.

I need the CYPD3123 functioning as power source to charge the Samsung when it is plugged in the USB-C connector.

The MOSFET will be turned on by a command in the APP_EVT_CONNECT of  the function void app_event_handler(uint8_t port, app_evt_t evt, const void* dat).

Could you tell me where the default port configuration table is and how I can change the power sink to power source in the default configuration?

Thanks,

Derong Yuan 

I have a new CY4532 evaluation kit with the Power Adapter firmware in it. I would like to change the configuration of the CCG3PA on the main board. When I load the configuration using the EZ-PD Configuration Utility, the device info indicates that it is the CYPD4126 which is on the power board. The documentation is not clear as to whether the configuration table being changed is in the Power Board or is passed on to the Main Board over the CC lines. Any clarification would be appreciated. I want to add some additional PDOs and have not had much luck.

Hi,

I used the Dock board, designed by CCG4 4236, and when I encountered charging, I CCG4 not send Source_Cap action on NB.

This image is designed for the circuit architecture

The following figure is the message caught using CC analyzer, pictured above for normal charging, the following figure is due to CCG4 did not send out Source_Cap after the stop.

Currently rechargeable case with a case that cannot be recharged,

The difference in CC Log cannot be sent out in Source_Cap.

The CASE,CC Log that can currently be recharged is as follows:

The CASE,CC Log, which is currently not rechargeable, is as follows:

I was looking into upgrading our firmwarefirmware platform for our CCG4 solution, from SDK version 3.2.1 to the latest 3.3 release as part of the normal maintenance.

The first thing I notice is the change from having several linker files, to having one linker file and a post_build.bat script.

I am not very happy with this change.

The first thing is the same issues as described here.

https://community.cypress.com/community/usb/ez-pd-type-c-usb/blog/2018/09/11/ccg5-host-sdk-new-project-build

• The project name is hardcoded
• cyelftool.exe is not in the path
• The project depend on "backup_fw.cydsn"

Specifically the last element is not properly thought out I think. With version 3.2.1 I already need to keep 2 schematic files (cysch) in sync regarding pin functions and their names. Luckily only one is for the "release" version and the other is only used for the no bootloader version used for debugging.

With the "backup_fw" another schematic file is added, and I need to keep yet another project in sync with the main project.

I will much prefer the 3 linker files setup as in SDK version 3.2.1 then the post_build.bat solution from SDK 3.3.

And based on the fact that project name is hardcoded in the post_build.bat it seems a bit hastily released.

• What is your plan for the next SDK release?
• With SDK release 3.3. you put CCG3 into maintenance mode. What is the plan for CCG4?

I am considering skipping the 3.3 for now, and wait to see what changes you bring out in the next release - so it will be nice to know what your plan is. Do you return to the 3 linker script setup. Do you evolve the post_build.bat way to an usable solution?

How ist it possible to read the logic level on the configuration channel pins CC1 and CC2 of the CCG3 PSoC in PSoC Creator?

In the Pins view it looks like the pins CC1 and CC2 can't be configured like other GPIOs:

I am using the CYPD3125 in a one chip solution, where I need to control a USB C MUX dependant on the USB C connector rotation. As this is my first project with USB and PSoC, I don't have any previous knowledge in this area.