CYPD5225_thunderbolt_tgl firmware resets with xiaomi headphones on one port

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
lock attach
Attachments are accessible only for community members.
KiLe_4629881
Level 3
Level 3
25 sign-ins 10 replies posted 10 questions asked

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

0 Likes
1 Reply
Sananya_14
Moderator
Moderator
Moderator
750 replies posted 500 replies posted 250 solutions authored

Hello,

From the logs, the behavior seems similar on both the ports where the earphones isnt responding to any of the PD messages since its Type-C only. As you mentioned, the PD configuration is same for both the ports.

-Could you please provide the CC1, CC2, VBUS waveforms when the earphones is connected to both the ports?

-Please let us know if you have made any changes to the default firmware and the firmware version you are using.

-Could you also test with any other Type-C only device and let us know if the issue can be reproduced? It would also help if you could provide the schematic showing the CCG5 connections since this could be due to a hardware issue on Port 1.

Best Regards,
Sananya

0 Likes