UPD360 datasheet(73/221 Pages) MICROCHIP

73 / 221 page

 2016-2017 Microchip Technology Inc.

DS00002084C-page 73

UPD360

9.2.3

SOURCE DETACH DETECTION

When configured as a source, the detachment of the partner UFP is determined by monitoring the appropriate CC pin

(with the Rd pull-down) for a voltage exceeding DFP_UFP_DEF, DFP_UFP_1A5 or DFP_UFP_3A0, depending on the

charging current advertised by the device.

The following describes the steps that are taken to determine if a detach has occurred when operating in companion

mode:

APPLICATION NOTE: Software must not look at the CC detect status while a PD contract is in place, even though

the Type-C spec permits doing so, in order to avoid false-disconnects in the Attached.SNK

state during heavy PD message traffic.

APPLICATION NOTE: Software should set a 3A advertisement while it's a source and a PD contract is in place in

order to avoid false-disconnects in the Attached.SRC state during heavy PD message traffic;

a 1.5A advertisement (even though permitted by the Type-C spec) is not sufficient to avoid

this issue due to the lower vOPEN threshold. An exception to this recommendation is when

“Collision Avoidance” is implemented.

The following steps assume the CC debouncer has previously been used to detect attachment per the prior section.

Software accesses the device via I2C/SPI which wakes the device up and enables the 48 MHz oscillator.

Software programs the CCx Debounce Clear Enable Registers (CCx_DBCLR_EN) as required to enable per

threshold debouncing. Typically this only involves disabling the thresholds not corresponding to vOPEN.

Software enables CC1_MATCH_CHG or CC2_MATCH_CHG interrupt via CC Interrupt Enable Register

(CC_INT_EN).

Software enables IRQ_N via asserting the respective CC_INT bit in the Interrupt Enable Register (INT_EN).

Software programs the CC Comparator Control to sample appropriate CC pin.

The device samples the respective CC pin while operating off of 20 kHz clock.

Changes in state of the CC are reflected in the respective CCx Match Registers (CCx_MATCH) and CCx Change

Status Registers (CCx_CHG_STS).

CC1_MATCH_CHG, or CC2_MATCH_CHG, interrupt asserts, CC_INT asserts which in turn asserts the IRQ_N

pin.

Software implements a further debounce of the CC match for tCCDebounce in order to detect the detachment.

10. If VCONN is being supplied, than the VCONN FET shall be disabled in software by appropriately setting the

VCONN1 Control or VCONN2 Control in the VBUS Control Register (VBUS_CTL). In this case, software must

also discharge VCONN as defined in Section 9.7.1, "VCONN Discharge Programming Model".

11. Software disables the PPC which causes the internal 5V power switch to open if required. Power may have alter-

natively been provided by external power source.

12. Internal 100 Ohm VBUS discharge switch is closed if required.

13. Discharge switch remains closed until vSafe0V threshold is crossed.

14. If vSafe0V threshold is not crossed within VBUS Off Register (VBUS_OFF) which asserts VBUS Discharge Error

interrupt and asserts IRQ_N pin.

15. Internal discharge switch is opened.

16. The part is configured by software to detect a UFP attach. The 48 MHz oscillator is disabled. Only the keep-alive

clock remains enabled.

Note:

Occurrence of VBUS Discharge Error interrupt indicates a potentially catastrophic system power issue.

UPD360 Datasheet(PDF) 73 Page - Microchip Technology

UPD360 Datasheet(HTML) 73 Page - Microchip Technology

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL