Announcements

Live Webinar: USB-C adoption. Simple & Cost-efficient solutions | April 18th @9am or 5pm CEST. Register now !

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
PaRi_1293246
Level 3
Level 3
First solution authored 25 replies posted 50 sign-ins

Hello,

We have implemented a CYPD3125 on our latest ultrasound scanner.  We use the firmware of the evaluation kit with some modifications to the configuration table.  We have one source PDO (5V / 1.5A) and two sink PDO (5V / 900 mA and 15V / 3A).  Our system required 15V / 3A to work.

When we connect a USB-C power adapter our system request 15V / 3A and it starts working properly.  But sometime  after few seconds or few minutes the CYPD3125 turn off the consumer path and our system stop working.  When we measure the VBUS the 15 volts is still there but the gate of the two transistors that control the consumer path are at 0 volt.

What can cause the CYPD3125 to turn off the consumer path?

Thank you

Best Regards,

Patrice

0 Likes
1 Solution
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Partice,

 

CYPD3125 on CY4531 board firmware example could be downloaded from the link: https://www.infineon.com/dgdl/Infineon-EZPDCCGXHOSTSDKSetupOnlyPackage_3.4.exe-DevelopmentTools-v01_... 

 

The condition of VBUS_C_CTRL may cut off by firmware (Recommend confirm the MOS FETs on customer path is good before firmware debug):

1. There are fault on VBUS or VCONN: VBUS OVP, VBUS OCP, VCONN OCP for CCG3. 

2. CCG3 firmware logic customize incorrect. 

 

VBUS_C_CTRL marco define is under config.h, you could use a software UART to debug it if the vbus_c_ctrl disabled consumer path or not.

 

Best  Regards,

Lisa

 

 

View solution in original post

0 Likes
4 Replies
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Partice,

 

CYPD3125 on CY4531 board firmware example could be downloaded from the link: https://www.infineon.com/dgdl/Infineon-EZPDCCGXHOSTSDKSetupOnlyPackage_3.4.exe-DevelopmentTools-v01_... 

 

The condition of VBUS_C_CTRL may cut off by firmware (Recommend confirm the MOS FETs on customer path is good before firmware debug):

1. There are fault on VBUS or VCONN: VBUS OVP, VBUS OCP, VCONN OCP for CCG3. 

2. CCG3 firmware logic customize incorrect. 

 

VBUS_C_CTRL marco define is under config.h, you could use a software UART to debug it if the vbus_c_ctrl disabled consumer path or not.

 

Best  Regards,

Lisa

 

 

0 Likes

Hello Lisa,

Few pins that are connected on the evaluation kit are floating on our system.  Maybe one of the floating pin cause the random consumer power path turn off.

Here is the list of pins that are floating on our system.  I have used the same name of the evaluation kit daughter board to name the pin.

Pin 11 /  DP_AUXP_P1
Pin 14 / DP_AUXN_P1
Pin 12 / SBU1_P1
Pin 13 / SBU2_P1

Pin 23 / MOS_TYPE

Pin 15 / SWD0_DAT
Pin 16 / SWD0_CLK

Pin 24 / TXD_P1
Pin 25 / RXD_P1

Pin 7 / GPIO_UART2_TX
Pin 8 / GPIO_UART2_RX

Pin 21 / USB2_DP
Pin 22 / USB2_DM

Pin 28 /  VSEL1_P1
Pin 27 / VSEL2_P1

Pin 6 / VCONN

Pin 38 /  VCONN_OCP_STS

Which one of those pins are inputs?

Which one of the inputs require a pull-up resistor?

Which one of the inputs require a pull-down resistor?

Is pin 38 / VCONN_OCP_STS can be the cause of the random turn off of the consumer power path?

Thank you

Best Regards,

Patrice

0 Likes

Hello Lisa,

When I open the firmware project in PSoC Creator how can I identify which pins are inputs and which pins are output?

Thank you

Best Regards,

Patrice 

0 Likes
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Patrice,

If you have opened the project, please following below ways to confirm the pin is configured as input or not. 

1. Double click the pin on .cysch file.  (below is example of output configuration.)

ShifangZ_26_0-1656401997408.png

 

2. Make sure the port information of the specified pin. for example, pin#35 is port 3.3. And then, use GPIO_PORT_3_PIN_3 to search all in firmware. Make sure this pin is not change configuration by API: 

/**
* @brief Select the IO mode for a CCG device IO.
*
* This API configures the IO mode for a CCG device IO. It does not do any
* error check and will just set the HSIOM configuration for the GPIO. Care
* should be taken to make sure that wrong indexing is not done.
*
* @param port_pin Pin to be configured.
* @param hsiom_mode Desired IO mode.
*
* @return None
*
* @see hsiom_mode_t
*/
void hsiom_set_config(gpio_port_pin_t port_pin, hsiom_mode_t hsiom_mode);

 

Best Regards,

Lisa

0 Likes