Failed to enter VDM mode process

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.
MaLi_3529141
Level 3
Level 3
25 replies posted 25 sign-ins 10 replies posted

Dear,

I made a dock and used the CYPD4236-40LQXI_dock sample code.

(1) In the initial state, I am a Power sink.

(2) Then, I actively initiated PR_Swap to become a Power source.

(3) Finally, I call dpm_start(TYPEC_PORT_0_IDX) to get back to the initial state.

(4) After CC re-communicates, sometimes the enter VDM mode process fails.

In the Fail case, Enter VDM mode process failed.

Pass case:

pastedImage_3.png

Fail case:

pastedImage_5.png

1. How to avoid this happening?

2. When I enter this state, where can I read the information?

Thank you.

0 Likes
1 Solution

Hello,

(1) The hard reset is a part of the sequence of soft resets that come after seeing no GoodCRC'c from the port partner. This is normal.

(2) I am not sure which message belongs to CYPD4236, since the log does not match the sequence of commands you are sending as in post #1.

Regards,

Rajath

View solution in original post

0 Likes
3 Replies
RajathB_01
Moderator
Moderator
Moderator
250 replies posted 100 replies posted 50 replies posted

Hello,

You can try update dp_sid.c to ensure that Discover SVID message is acked. Following is the associated function:

bool get_modes_vdo_info(uint8_t port, uint16_t svid, pd_do_t **temp_p, uint8_t *no_of_vdo)

Regards,

Rajath

0 Likes

Hello,

In Fail Case 01.ccgx,

pastedImage_2.png

(1) Is the reason for the hard reset started on line 37?

(2) Why does CYPD4236 not respond to GoodCRC?

Thank you.

0 Likes

Hello,

(1) The hard reset is a part of the sequence of soft resets that come after seeing no GoodCRC'c from the port partner. This is normal.

(2) I am not sure which message belongs to CYPD4236, since the log does not match the sequence of commands you are sending as in post #1.

Regards,

Rajath

0 Likes