USB EZ-PD™ Type-C Forum Discussions

Dear Cypress,

During production of powerbanks (with CYPD3171 as USBC PD 60W controller) we found problem that we hadn't noticed before:

One of three devices cannot charge. After connecting charger with correct PD profile (or even simply 5V) CYPD3171 locks up and appears to be dead. After some time, when BMS disable power supply (because of discharging) and when charger is connected again, CYPD3171 works correctly. We are afraid that our clients can have the same situation. Can You check our configuration file for errors? I am adding also schematic.

Best regards

Lukas

i have to units  of cypd3175      connceting   via i2c    

when  master unit    send  first time  to slave    the slave unit  does not repones   only  the second   attempt from the master    after   first time the slave coressponding  well

        /*handle  with cypd3175 */

     attached    cypd3175_recieve_packet();

        CyDelay(100);

        /* Handle the device policy tasks for each PD port. */

        for (port = PORT_START_IDX ; port < NO_OF_TYPEC_PORTS; port++)

        {

            dpm_task(port);

            app_task(port);

Q1 :     do i need    special conciduration  in PD stack   ? 

Q2  : why need delay in slave  code  all examples  show with delay ?

Q3   : how hanle slave i2c  in power adapter  project

it is possible  create task which handle i2c slave  or master  in PD task  like call back   i try also  run this  cypd3175_recieve_packet    from timer  bat i get  stack overflow  ?   timer call  back have  max size stack ? 

Hello,

I am using CYPD3175 (24-pin QFN) in a USB-PD direct feedback DC/DC application. I am experiencing issues with a current spike dished out on the FB pin on positive VBUS transitions to, and exceeding, 20V.

To step up the DC/DC output voltage from the initial 5V Vsafe setting, the USB-PD controller needs to pull current from the FB node (let's assign a negative connotation to current leaving the FB node), which it does. However, the control current steps are associated with transitory initial positive disturbances (current flowing into the FB node) of varying magnitude, likely due to internal (to CYPD3175) switching of current source paths to ground or whatever D/A circuitry is being used to generate it.

I have been able to isolate the offending disturbance to a very finite step in the (VOUT/VBUS) voltage transition: 20.34V to 20.36V, in the firmware and circuit I use. The expected 100nA increase in the negative FB current is preceded, in this case, by a >10uA positive current spike, high and long enough to trigger OVP in the DC/DC controller.

Filtering the FB node using a capacitor to ground is not a great option, since it creates a pole, at relatively low frequency, in the feedback loop.

It appears to me this is an issue related to how the FB control sink current is generated, a hardware issue within the CYPD3175. Is there anything that can be done in software to mitigate this problem?

EZ-PD^TM CCG3PA-NFET is now available for your next power adapter designs!

CCG3PA-NET is a highly integrated USB-C Power Delivery port controller for power adapters.

It integrates a NFET gate driver and is compatible with the latest USB-C Power Delivery standard.

In addition, CCG3PA-NFET supports legacy charging protocols without additional BOM.

Designers now can choose either NFET or PFET to work with the CCG3PA family of USB-C port controllers – Use NFET with CCG3PA-NFET, or PFET with CCG3PA.

Highlighted features:

• Supports USB PD 3.0 with Programmable Power Supply (PPS)
• Supports QC4+, QC4.0, QC3.0, QC2.0, Samsung AFC, Apple charging and BC v1.2
• Integrates NFET gate driver to drive the load switch
• 5 m Ω Current sense resistor
• Supports independent constant current (CC) and constant voltage (CV) modes of operation
• Protects against accidental VBUS to CC short
• 24-QFN package (4 x 4) with –40 °C to +105 °C extended industrial temperature range
• USB-C Reference schematics available for both opto coupler and Direct feedback designs.

Here's the: Product Brief

Here's the: Reference Design for a 65W power adapter

Hi!

We are seeing some strange behaviour on our USB-C dock, more or less based on the CCG4 dock ref-design. Sometimes (maybe every 20th time) alt-mode fails to negotiate and based on the PD-signalling it looks it is the CCG4 alt-mode state-machine that fails. There might maybe be an underlying hardware problem (maybe I2C communication to mux or something), but a bit hard to understand how the alt-mode state-machine will change behaviour based on this.

I have attached two traces. dp_alt_mode_failed the error is around line 179 were CCG4 sends NAK. In dp_alt_mode_failed_2 the error is in the last part (line 730 and below) CCG4 doesn't respond to "Enter Mode" sent from the sink. The other traces are successful attempt for comparison.

Again, this is rather random occurrences so it might well be some timing or hardware stability issue, but maybe you can come up with some clues based on what external factors the CCG4 code will act on.

Cheers

Olof

Hello,

I am working on a custom board using the CYPD-3171, and I am encountering issues when attempting to program, both using the PSOC-MiniProg4 part through the SWD Lines, and through the CC Programming using the CCG3PA EVK Power Board.  the Hex file I am attempting to program is the generic PB application included in the SDK with a modified Config.c file as generated through the EZ-PD configuration tool. the Hex file as well as the images of each step of my attempts are attached to this post.

One error I note is that after programming over the MiniProg4 device, a subsequent verification fails as shown in VerificationFail.PNG.

In addition, when doing a CC-Program, the device claims to still be in a bootloader state even after the application is loaded.

Any assistance would be much appreciated.

Thank You,

Nate Hinshaw

CYPD2103 has passed the USB-IF test procedure for USB4 e-Marker and the test result has been posted on the USB-IF Integrator's List. 

Customers designing USB-C cables can now start incorporating CYPD2103 in their cable assembly to serve the emerging USB4 market.

Product Test Information

Company: Cypress Semiconductor Corp.
Product Name:  EZ-PD CCG2 EMCA
Model: CYPD2103
Revision: B
Product Test ID: 3869

void led_timer_cb (

    uint8_t port,

    timer_id_t id)

{

    (void)port;

    (void)id;

    gpio_set_value (FW_LED_GRREN_GPIO_PORT_PIN, !(gpio_read_value (FW_LED_GRREN_GPIO_PORT_PIN)));

    timer_start (0, LED_TIMER_ID, LED_TIMER_PERIOD, led_timer_cb);

}

if i put   more  code  i have  stack overflow  for example  send I2C master    and  expeted recieve  answer from slave

The EZ-PD Barrel Connector Replacement (BCR) controller is a USB-C Power Delivery solution dedicated to power sink applications. The BCR controller acts as a Up Facing Port (UFP) and interoperates with any USB-C Down Facing Port (DFP) or Dual-Role Port (DRP) for establishing a USB-PD contract. The BCR controller can be fully configured by hardware using pin-strapping, or by software using Host Processor Interface (HPI) commands from an external I2C master (e.g. MCU). The EZ-PD BCR HPI Utility is a GUI-based application that guides users through the process of configuring the BCR controller using HPI. The utility allows users to:

• Evaluate the usage of HPI using the EZ-PD BCR Kit and a Windows-based PC.
• Select and configure the desired BCR controller settings using HPI that overrides the preset hardware configuration on the BCR Kit.
• Monitor the real-time status of USB-C connection, Power source capabilities, USB PD power contract, VBus voltage, etc.

The EZ-PD BCR HPI utility and associated documentation are available to download at:

     https://www.cypress.com/documentation/software-and-drivers/ez-pd-bcr-hpi-utility

We have had a couple of CYPD3175 IC's fail in a prototype dedicated charging port design using the direct feedback system. The most faults we've had is that the chips stop responding to a plug insertion. We verify that the internal core is running because we can measure 1.8V and the CC line is pulled up to +3.3V before insertion and drops to 1.7V or so during insertion. These are prototype boards that were working until this sudden fault. 

We've also had the controller IC suddenly start running very hot and fail after working with no problems for two weeks. We only noticed the failure because after a plug insertion the port turned on and off contiuously. We remove the cable and reinsterted it and the controller chip started to heat up and stop running.

We have studied the switch mode power supply for stability and the phase and gain margins are according to industry standards.