USB EZ-PD™ Type-C Forum Discussions

Hello

I am designing a board with a CYPD5225.

Question1: Do I need to "program" the device CYPD5225 in the manufacturing process before the first power-on

Question2: Is it possible do buy the device already programmed ?

Question3: Do I need the pin "XRES" (reset) on a connector for programming the device ?

Question 4: How many times is it possible to program the device CYPD5225 ?

Question 5: I was not able to fond the default setting of the different pin (when the pin has multi-function), can you send me the default setting ?

Question 6: When a I2C bus of the CYPD5225 is not used, do i have to add external pull-up on I2C lines or is it possible to leave the I2C pin left floating ?

Best Regards,

TD83

Hello,

On our board, we have no EC (Embedded Controller):

Question1: is it possible to use the pin SWD_IO/SWD_DATA to program the device CYPD5225 ?

Question2: what do i need to program the device CYPD5225 ?

Question3: do i need to route a particular I2C bus to a connector to be able to program the CYPD5225 device ?

Question4: what is the ref of the board and the software to program the CYPD5225 device.

Thank you for help, best regards,

TD83.

I have the EZ-PD BCR dev kit and I wrote some arduino software to communicate to it through I2C. I am able to read and write to registers and confirmed it by resetting the I2C line using the RESET register and afterwards reading the  DEV_RESPONSE register and got a proper response. But I am having a problem sending the "Discover Identity" command to the port partner (I have a source device that will respond to this command). 

In the USB spec I found this example command and sent this to the device.

I know you do not have to write the message header because the BCR will create that for you so I wrote the VDM header to the data memory which comes to be 0xFF00A001 . 

To my understanding the next step is to write to DM_CONTROL

but here all the bits should be set to zero except the length. I set DM_control to a few values 0x8000, 0x2000, 0x6000, and 0x0000 but I got an error for all the commands except 0x0000 where I got a success in the PD_response register but  I never recieved anything in memory. 

Are these the correct command to write into data memory and DM_CONTROL or is one of them wrong? 

Hello, I just want to ask if I must always connect the CCG Lines CC1 & CC2 ?

The background is that I have only one CC - Line available from an USB PD capable Power Source. Lets imagine I have only CC1 of an USB-Plug connected to CC1 of the CCG2. Can I left CC2 of the CCG2 open ? OR is it impossible to do so ? ( I know this connection is non-standard 😉

THX for any Help, Enrico

Hi, we want to use the 5126 for a new project however as this is the first use of a cypress CCG product there are several questions which I wasn't able to solve:
1. It looks as if the CCG5 FW update/parameter programming is via the I2C port. I guess it's via SCB1?
2. We already have a sort of USB to serial converter build into the system which we would like to use for FW updates and parameter programming. Is there a document on how to achieve this via I2C? I've only found 002-22328 Rev. *G which discussed programming via SWD(?) but couldn't find anything for I2C.
3. during development we'd like to circumvent our USB to serial solution and rather use a "cypress-approved" one (there are only so many possible points of failure you want to deal with at any given time). However I haven't found a definitve answer on whether the MiniProc3 or MiniProg4 would support both FW programming and Configuration via the EZ-PD Configuration utility or whether we'll have to nail a PCB with a cypress USB-serial bridge together (and, as I asked before, which SCB port we'll have to connect to).

Thanks for any reply.

Hi,

We're using CYPD5225 at the host side in source mode and have to cope with power hungry devices. There is need to power off these devices completely to reduce wear and tear and then re-enable later. This can be done easily by disabling the port as this disconnects the device and powers it down. 

This approach has a problem that the port stays disabled even when the device is disconnected, because PD firmware does not detect the cable plug-out. Is there way to disable power so that PD still detects plug-out of the device and the firmware can re-enable port? We've tried e.g. disabling VBUS only but this did not work.

Thanks!

Hi, 

Based on CCG3 USB-PD subsystem, how to disable the internal Switch (e.g. VDDD is only provided by VBUS_C)?

Hello

About Cypress's EZ-PD CY4533 (CYPD7133).

Q1) Please tell me the DC characteristics of VBUS_FET_EN.

>VBUS_FET_EN pin Behavior
>The VBUS_FET_EN pin is a PFET gate driver that drives to either 0 V or VBUS_IN depending on the state of the Type-C >connection.Contact Cypress Technical Support for more details on how to use this pin for specific applications.

>

In the data sheet Page9 of CYPD7133, it is described as above.

Therefore, when measuring the voltage on the VBUS_FET_EN  pin  and the FET gate side of R16 with CY4533KIT, the following measurement results were obtained.

SEL    R16 (FET gate side)      VBUS_FET_EN
5V                  1.1V                                 0.6V
9V                     2V                                 1.1V
12V                  2.6V                             1.4V
15V                  5V                                 2.8V
20V                  10V                               5.7V

Q2)As a result mentioned above,  it seems that the VBUS_FET_EN is not 0V or VBUS_IN voltage,

Could you please tell me the reaon on this.

Q3) 

Please let me know if there is a logic (Hi, Low) signal line other than VBUS_FET_EN  when the USB-PD obtains an effective voltage.