USB EZ-PD™ Type-C Forum Discussions

The HX3PD's datasheet says (under "DC Electrical Characteristics" section) that "VBUS for upstream port" voltage must not exceed 5.25V. At the same time VBUS itself can clearly be up to 20V nom. What exactly is VBUS pin (M7 in BGA pacakage) intended for? The pin description section hints that it is a digital input. So I assume that is is kind of VBUS present/not present. Can I interface it to the actual VBUS with a huge resistor hoping that any excessive voltage will be clamped at the pin? See the screenshot attached. Thank you.

In my application CYPD3177 is configured to accept any voltage between 5 and 20V and at least 900 mA current. I also do not use safe_pwr. So in the end the schematics looks like the one in the attachment. It is clear that the part will expect zero volts at VDC_OUT when VBUS_FET_EN is not asserted and will generate FAULT when facing the situation it does not expect.

So here we have fault condition that can not be removed. The question is - how will it affect the part operation? Is there any workaround that does not involve additional FETs and supply ORing controllers?

Thank you.

Dear all,

There are some "VCONN FET Circuit" in the following application diagrams.
What is the purpose of adding the external driving circuit?
I think driving circuits for supplying eMarker are integrated in the CC1/2 functional block. Correct?

Regards,
Nagata.

Hello,
I'm developing a system that seems to be based on the CY6611 evaluation platform. The block diagram is shown  below and here are few words about the development. The system should be configured as sink on the US, so laptop should provide a power for the system. We will need ~50W(20V@2.5A). System should have 6 DS ports, no need for PD on these ports, but only constant 5V, so I believe regular USB load switch should be sufficient for it. 

As I sow in one of the post here that US can be configured as sink port, could you confirm that.  I also believe I can eliminate usage of U20(NCP81239MNTXG) BB controller.

I would appreciate your opinion of design feasibility. If other evaluation platform(as you you have a lot) are more appropriate I would glad to know about them. Can I submit my design for your verification at the latest stage?

Dear,

I use the MUX_CTRL_I2C Read function in the cypd4236_dock Example code. I use the following MUX_CTRL_I2C api to read it, and even the start signal cannot be generated.

Do you need an init process, or enable those functions?

Best Regards,

Manu

Hi!

Read the great news that next PD release will include up to 48V@5A, very good. Will ensure that USB-C covers next generation charging use-cases as well. 

Are there any official roadmaps from Cypress / Infineon when this will be supported by the EZ-PD SDK and IC's?

Cheers

Olof

Hello Everyone,

My Lenovo yoga C930 and the charger stopped working after my dog bit the usb type c cable. After buying a new charger I found out that my laptop doesn't charge anymore. I opened the laptop and plug it in then I found the problem. The CYPD4226-40LQXI was heating up like crazy. I disordered the part and found that pin 23 V5V_P1 was shorted to GND.

I ordered the part from Mouser and I should receive it tomorrow but after going through the datasheet again it seems this chip is programmable. Does it comme with a working firmware out of the box ? 

Thank you,

Our system NB has dual port type C with DP function
Type C adapter supplies 20V voltage to the system
After ESD test
DP still outputs the screen normally
The system only has battery power left
We measured that the type C adapter still has power
But it looks like CCG5 disconnected the power
After the test, it should be able to receive power from the adapter normally
Does CCG5 activate any protection?

Which part would you say is the absolute easiest to get a PD source only solution up & running?
it should preferably support PPS, but a few fixed PDO's would be ok as well.

I know CCG3PA is most common, or at least the part with most ref-designs with OnSemi + Qorvo regulators. The issue is that the stack is closed source, so if you need to change to another regulator from them or another company, you'd have to write it from scratch.

What would be the preferred choice here?

ps.

I really like the simplicity of EZ-PD BCR that comes pre-programmed but still offers additional features via I2C.
...really wish there was a EZ-PD PD Source equivalent, simple, pre-programmed (no swd needs) with support for a few well known buck and buck/boost power regulators.