USB EZ-PD Type-C

Hi,

I have two questions:

1. Is there any difference between CYUSB4347-BZXCES and CYUSB4347-BZXC?

2. Would you please explain what is the main difference between signed and unsigned firmware for CYUSB4347/ CYUSB4357?

Thanks,

Nilufar

Hi,

I am designing CY6611 EZ-USB HX3PD PCB. The main component CYUSB4347/CYUSB4357 is not available in the stock. Can you please suggest alternate part for this one ??

Thanks

Sugreev

I have a total of 16 PWBs build of which two I am unable to program the CYUSB4357-BZXC.  I checked all the supply voltages, chip selects , and so forth and everything seems okay.  On one PWB, I've replace the flash and USB HUB twice and still can't program the USB HUB.  Additionally the PWB was X-ray'd in that area and nothing out of the ordinary was observed.  Via X-ray both the USB connector and transient protection devices seem soldered down properly.  I'm not sure what to do next.  What specific signals, voltages does the USB HUB need for programming?  I included my design implementation and screen capture of the programming errors.  What signals should I be concerned with?  I did notice D+/D- levels appear to be transitioning logic low/logic high versus looking at a those signals on a working device where the levels are much faster and smaller (differential voltages). 

Our firmware is monitoring a fault gpio line from a load switch that is asserted when a connected device is faulting and pulling too much current. If fault condition does not clear within certain time I call app_disable_pd_port() to disable further activity on the port. 

After a delay and when the fault flag has cleared I want to enable the port again. What is the correct way to do this? There is no symmetric API call to enable the port.

We're using CYPD5225-96BZXI. Source mode only.

Hello

Customers are using the CY4533 kit for evaluation.

V_MIN = VMAX = 5V, current is set at ISNK_COARSE = 2A, ISNK_FIN = 0A.

When the PD compatible adapter and the evaluation board were connected with a Type-C cable, the VBUS Power LED emitted light and the 5V voltage could be confirmed from the VBUS line.

Even when a PD-incompatible Type A adapter and evaluation kit are connected with an A to C cable, the VBUS Power LED emits light and is output from the VBUS line at a voltage of 5V.

(Maximum output of Type A adapter is 5V / 2.4A)

After checking the kit guide, it was recognized that the Fault pin was set up (red LED was lit) and 5V / 900mA was output from Safe_5V Output.

However, the output from Safe_5V Output could not be confirmed.
Why is this?

Best Regards

Hayato 

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]
......