Configuration Utilityを用いて、Port Information→PR_Swap responseの項目をRejectからAcceptに変更しました。

しかし、このConfigurationを適用したCCG3にてパケットを確認しますと、通信相手のデバイスからPR_Swapを送信された際にRejectを返しています。

なにか設定上AcceptでもRejectを送信してしまうような条件はありますでしょうか。

また、設定以外でも注意すべき点があればご教示ください。

Hello,

We were settling on CCG3PA in a new design which is a Type C/Type A dual port charging only, with fixed 5V supply. I had a few more questions about the implementation I was hoping to get answered:

- Does Cypress have a design/schematic check service?

- There seems to be GPIO that is preferred for certain functions in design examples (i.e. external VCONN FET enable, Type A current sensing etc.) - is there a definitive listing of these? Can this all be changed in firmware?

- There appears to be no RCP (Reverse Current Protection) on the CCG3PA - is this possible using an external current sensor (into an ADC pin) and modifying the firmware (for both Type A and Type C ports)?

- I've read in a notice and in the forums that the FW was closed source - what does this mean? Is it possible to get full access under NDA if we run into issues when we customise the higher level code?

- For CSP connection - is there a way to make this Kelvin connection? Is Pin 22 the -ve input of the current sense amplifier or is this just a general ground? Any recommendations here?

- Is there a schematic of internal PFET drivers? How does the internal pull-up on the VBUS_P_CTRL path function if VBUS_IN_DIS is used in the configuration shown here (CCG3PA Power Adapter/Car Charger (1C+1A) single chip solution hardware design tips) for a Type C/Type A port - what is it pulling up to? In this case do we need an external pull-up?

- With respect to the PFET drivers again - are they able to continuously sink current if shorted to VBUS = 20V while trying to pull-down? It would seem that with an internal pull-down of 3kΩ max the dissipation is a minimum of 133mW - can we add external resistor in series with the pin to reduce dissipation in this instance? Also noticed there is difference in sink currents vs drive strengths given (Table 32. Gate Driver DC Specifications) is there a firmware control aspect here too? I think a schematic of how this works might clarify things for me.

- Is it possible to disable FW upgrade over CC pins after an initial FW update?

- We eventually want to extend this to control an external supply up to 20V/5A - this will be over an I2C/UART comms port instead of direct feedback. Is there any device that is preferred to implement this between CYPD3171-24LQXQ, CYPD3174-24LQXQ and CYPD3175-24LQXQ? Are there any application examples of firmware/hardware modified to support digitally controlled power supply via I2C/UART/SPI?

Regards

djs

I want to build a system with USB Type-C (both UFP/DFP power ports) and need to select a CCGx device.

I need to transfer 100W and have VBUS short protection, so this rules out CCG1-3 and 4/4M .CCG5 is not recommended for new designs, so it is ruled out.

100W requires Vconn to detect EMCAs so I can prefer CCG5 or CCG6  (instead of CCG3PA, BCR, and PAG1S).

There's a chance I would want to use authentication, so I might prefer the CCG6.

How is my logic and is the CCG6 generally available and supported for smaller customers (I'm looking at ~5k ICs/year for a ~10 year product life)?

Hi,

There is an "old" reference design with CCG3PA + ACT475x.

Question:

- Is there source-code available for the Qorvo buck/boost available?

- If yes, does the CCG3 implementation work on the CCG5 series!?

Thx David

Hello

They plan to write CCG5 Firmware  to CCG5C using Miniprog or ROM writer, but is it possible to program CCG5 build FW to CCG5C?

Since the PartNumber is different between CCG5 and CCG5C, I am thinking that an error will occur when programming. Because , I think that the built ROM has PartNumber information written, and I think that a verification error will occur on the tool(ROM writer or PSoC Programmer). In that case, it is necessary to specify the device as CCG5C in PSoC Creator and rebuild.
Is it correct recognition?

Best Regards

Arai

I am working on implementing my first USB PD design, and I have been having difficulties determining what the right controller IC for my product application would be for the most straight-forward implementation.  The contorller is going into a battery powered device and needs to charge up to 30W, it will never source power outside of itself, it charges a LI-Ion battery and powers the system at 5V.  I think I need the CCG2 series as the most appropriate but I can't tell for sure and would like some clarification on where the different models fit most effectively, especially as the dev kit for CCG2 is ~$50 and for CCG1 is closer to ~$550.

Hi,

I want to design a USB-PD application. I want to add PD functionality for a device that has no PD functionality. I also want to show voltage and current values on a I²C display. I am struggled to select the right CCGx device. So, at the end my application will be UFP device only. It will have 2 USB-C connector one for power input, one for power output. The power output USB-C socket will not have USB-PD functionality, maybe only USB 2.0 connections.

Which device CCGx is suitable for my application?

Where can I find UFP CCGx schematics?

Thanks.

Hi,

For CCG5 or CCG6, what's the best/fastest way to flash the firmware onto the CCG's?

Note: we have to run from Linux machines, so miniprog/psoc programmer is not an alternative

現在CCG3に設定しているすべてのSource PDOに対し、EZ-PD Configration Utilityを用いて[Unchunked Extend Messages Supported]をYesからNoに設定変更しました。

しかしながら、このConfigurationを適用したCCG3にてパケットを確認すると、PDO1 (First PDO)の Unchunked Extend Messages Supportedは1(Yes)と表示されます。PDO2に関しては、設定されたままの値、ここでは0(No)が表示されます。

本件は、USB-PDの仕様によるものでしょうか、それとも本来切り替えられるものなのでしょうか。