USB EZ-PD™ Type-C Forum Discussions

I try to design USB 3.1 gen 2 TYPE C with PD using CYUSB4347-BZXC Chip.

Application is USB Dock with bus power.

I'm designed to USB circuit for the first time, so I don't really understand USB design.

I thought that the CY6611 EZ-USB HX3PDEVK would be good if the circuit was changed from self-power to bus power.

Please see the attached file that draw the Block Diagram.

(DS2～DS7 is not use this time ,but will use in feature.)

I don't know how it works with this block diagram configuration as USB TYPE C DOCK using bus power.

Is  there any problem about this block diagram configuration?

Or Is there a better circuit configuration?

Would you tell me advice?

Best Regards,

Takashi Igarashi

Hi Cypress support team,

We are going to use CYPD3120 in our design along with TI cross-switch TUSB564RNQT. Please have a look on the questions along with block diagram. (please note that I have already asked these questions in another post but I wasn't able to get the answers);

1. Please have a look on the block diagram for CYPD3120 (we will be using power from USB-C only and acts as upstream facing port), and kindly let me know if it supports by default the addition of cross-mux as marked in red or we have to alter the firmware?

2.  Please clarify about the firmware updates. I can see that these chips has SWD interface to program the flash and along with it is also mentioned in that datasheet that the devices have default firmware, for example CYPD3120 has default FW of USB Bootloader. I am assuming that it means we can program the CYPD3120 via USBC? Also, once the firmware is loaded then we don't need to program or boot it via USB or I2C each time? Actually this may help us to eliminate the addition of Embedded Controller on the board. 

3. Lastly, the CYPD3120 will be using USB 2 lines for Billboard support but at the same time the USB 2 lines will be going to the USB hub. I have added the green lines in above block diagram. Usually we can do it if the USB2 lines are just used for charge detection and we can connect them to the PD and stub along with passing the USB 2 lines onwards to the HUB or any other location. Do you think it will be OK to do so in this case where the USB2 lines will be used by CYPD3120? If this is not possible then may be we can connect it via DNP to CYPD3120 and use the billboard support within the hub. 

These points are important before implementing it and due to time constraint I would really appreciate a reply on these above points.

Thanks and regards,

Muhammad Awais

Dear All, 

My plan for Project type-c monitor：

1. Base on  project example 3120 dp dongle

2. rebuild boot loader for 3121 

3. change device to 3121 and SID from 1D00 to 1D02

4. update config by EZ-PD configuration Utility

My questions are:

1. Am I miss anything for this plan?

2. Currently,  the VBus is 0V on my PCBA , but my configuration is 5V,  can anybody give me a direction to fig out it , thank you very much.

Best Regards,

King

Hello. Further to the following thread,

Lenovo yoga c930 NM-B741 Doesn't boot or charge USB type-C controller issue. - Badcaps Forums

Attempting to assist others in a repair of this logic board. The CYPD4226 controller is available from authorized distributors.

Q1: Is the USB Type C controller able to replace the original component on this Lenovo logic board? Understand that there is a factory I2C bootloader but is there custom firmware onboard from Lenovo that may hinder this repair?

Q2: Can the firmware be read out of a similar logic board?

Q3: Read on another thread in this forum that Lenovo offers such firmware. Lenovo was useless on this case and did not want to assist further. We can attempt to reverse engineer the details for the public review but wish to understand if the CYPD4226 is a protected flash memory or not. Which tool can allow us to R/W to this USB Type C controller over I2C? Totalphase tools?

The owner is sourcing a 'blank' CYPD4226 device for this replacement.

In hindsight, the CCx lines must have been zapped by the high Vbus rail after a PD contract was enabled. Very common but the device should have had protection against this issue. We reported the same quirk ages ago to Via Semiconductor as I almost burnt my hands with the spec. Nasty and still evolving cases. Even after investing close to $1k USD on Cypress tools, your kits claimed to support 100W of negotiation yet the kit featured traces thinner than my hair. Apparently no one cross checked the reference designs.

I've developed a design based on the EZ-PD™ CCG3 USB Type-C to DisplayPort Cable Solution reference circuit (and firmware). One big difference in my design is that I need access to the legacy USB 2.0 datapath (pins A6/A7 on the USB-C connector, pins 21/22 on the CYPD3120). My understanding is that the CCG3 uses these pins for:

1. Programming Firmware
2. Establishing Billboard (for hosts that don't support DisplayPort over USB-C Alt-Mode)

Is that correct? If I don't need billboard functionality, can I disconnect the DP/DM lines from the CYPD3120 (after initial programming) and use them for other purposes (while still running DisplayPort over USB-C Alt Mode)?

My plan is to run DP/DM through a DIP switch, which will be set one-way during initial programming and another during runtime operation. Does that sound like a reasonable approach? Thank you!

I'm building a custom PCB based on the USB EZ-PD CCG3 USB Type-C to DisplayPort Demo reference schematic. The schematic itself is very easy to follow (and convenient since it's a single-chip solution). However, I'm concerned about the firmware. The CCG3 C-DP Dongle User Guide Rev3 states the following:

The firmware source project for the EZ-PD™ CCG3 C-DP Dongle Solution Demo using CYPD3120 device is provided as an example project along with the CCGx EZ-PD Software Development Kit (version 2.2 or above).

I've installed versions 2.2 and 3.4 but neither contains a *.cyacd file (or example project) for the USB-C to DisplayPort application. I did find the configuration file: CYPD3120-40LQXI_dp_dongle_config.xml but assume that alone isn't sufficient to attain operation.

Bottom line: where can I find the necessary firmware required to get the USB EZ-PD CCG3 USB Type-C to DisplayPort Demo up-and-running?

I'm building a simple USB-C to DisplayPort + USB-A out adapter PCB. My hope was to start with the CCG1 Type-C To DisplayPort Reference and simply branch the USB 2.0 data lines. My question is, are DP and DM used by the CY7C65210 for anything other than programming? If so, my solution is simple... just run them through a DIP Switch so I can either program or access as USB 2.0. Would this work?

• Can the USB 2.0 DP/DM lines be used independently (to communicate with a legacy USB device) while the SuperSpeed lines are carrying DisplayPort in Alt-Mode?
  
  
• Are the DP/DM inputs to the CY7C65210 needed for run-time or are they for programming only?

Thank you!

Sorry - had to open this again as a new issue - as I can no longer reply to the old issue. 

I have attached waveforms requested, please review. You can see after some time the PD controller kills the bus voltage - I presume when it is resetting. 

The old issue is here;  https://community.cypress.com/t5/USB-EZ-PD-Type-C/CYPD5225-thunderbolt-tgl-firmware-resets-with-xiaomi-headphones/m-p/268853#M5151 

We found an issue where I am not sure if this is an issue with the cypress sdk. 

but if we plug a pair of XiaoMi Type-C earphone BRE02JY into port 0 the device will continuously reset. 

If we plug the device into port 1, then the reset does not happen and these headphones work normally.

I have checked the configuration (attached) in ez_pd configurator and as far as I can tell both ports are setup the same. 

Looking at interrupts coming from the device over the EC i2c interface - this part will continuously respond with code 0x80 on the device interrupt register which is the RESET_COMPLETE event. indicating that the device is rebooting over and over as long as this device is attached to the port. 

[814.508406 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]
[814.582658 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]
[815.862641 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]
[815.936897 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]
[817.216020 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]
[817.290269 PD Controller 1 Port 255 Code 0x80 Response Len: 0x00]