Packet-Master USB-PET Report on Product Copyright © 2010-2015 MQP Electronics Ltd. Scripts OTG 2.0 Rel:1.4.1.0, BC 1.2 Rel:1.2.1.7 Test run on Friday, June 22, 2018 10:48:44 __________________________________________ Opening script: CT_PD_DBP.mpet Compile successful [0.112,693] PD - Dead Battery Provision Test DCP or CDP [0.112,702] Purpose: To verify that the UUT complies with requirements of the ‘Dead Battery Provision – Unconfigured Clause’ [0.112,734] Initial State: UUT has been fitted with a ‘Dead Battery’. Special Test Cable A is connected to PD. No VBUS voltage applied. Any mechanical switches on the PD required for it to be able to power up have been operated. [0.112,769] 1. PET applies CADP_VBUS max (6.5µF) and a pull-down resistor of ROTG_VBUS min (10k) to VBUS and turns on VBUS to 5V. ID pin is left floating. [1.112,828] 2. Connect 0V via 15k resistor to D+. Connect 0V via 15k resistor to D-. [1.112,839] 3. Wait TSVLD_CON_PWD max plus a margin (1 sec + .5 sec = 1.5 sec). [2.612,840] 4. Set up a watch-block to monitor the current drawn from VBUS, and be triggered if this current exceeds IUNIT (100mA). [2.612,846] 5. Check that D+ is below VLGC min (0.8v). If UUT connects at any time during the remainder of the test, skip to Step 15. We must assume that the dead battery provision is no longer required by the UUT. [2.612,847] [2.612,847] PD under test should now have detected SDP (development aid). [2.612,847] 7. For the next 30 seconds, follow the procedure in steps 8-10. [2.612,848] 8. Measure the average current drawn from VBUS, sampling every 1ms for a period of 1 second. Record whether this value exceeds ISUSP (2.5mA). [2.612,848] 9. If the value does exceed ISUSP for two consecutive averages, then check that D+ is at VDP_SRC (0.5V-0.7V). [DPB3] [2.612,849] 10. Check that the watch-block has not been triggered. [DPB1] [3.615,577] - IB_UNCFG average was 98.30mA - above ISUSP. [3.615,586] - IUNIT was not exceeded before connect. [4.625,566] - IB_UNCFG average was 98.30mA - above ISUSP. [4.625,573] FAIL: Voltage on D+ (0.009V) is not in range for VDP_SRC. [4.625,582] - IUNIT was not exceeded before connect. [5.635,652] - IB_UNCFG average was 98.30mA - above ISUSP. [5.635,659] FAIL: Voltage on D+ (0.008V) is not in range for VDP_SRC. [5.635,668] - IUNIT was not exceeded before connect. [6.645,656] - IB_UNCFG average was 266.50mA - above ISUSP. [6.646,675] - D+ went high. (Hardware debounce started.) [6.646,680] FAIL: IUNIT was exceeded before connect. [6.746,576] - PD connection now debounced. [6.746,577] [6.746,577] Enumerating [6.746,578] 15. Wait TA_BCON_LDB min (100ms) then issue a bus reset to the B-UUT (this time was included in debounce). [6.746,582] 16. Check that PET can enumerate UUT (at HS if possible), and Set Configuration 1. [6.746,583] 17. For the next 30 seconds, check current drawn does not exceed bMaxPower. [6.746,588] Resetting UUT [6.771,795] Reset complete - Full Speed communications [6.818,828] Getting Device Descriptor from address 0 [6.818,890] Resetting UUT [6.910,849] Setting UUT address to 1 [6.932,864] Getting Device Descriptor from address 1 [6.932,982] Getting String 0 Descriptor [6.933,042] Getting String 1 Descriptor [6.933,215] Getting String 2 Descriptor [6.933,440] Getting String 3 Descriptor [6.933,678] Getting Configuration Descriptor (first 9 bytes) [6.933,976] Getting Config Descriptor (all bytes) [6.934,281] - bMaxPower required by UUT is 500mA [6.934,281] - This correctly does not exceed vendor declared bMaxPower (500mA) [6.934,287] Setting config to 1 [6.934,956] 17. For the next 30 seconds, check current drawn does not exceed bMaxPower. [6.934,986] NOTE: Following readings are made on 2A range, so low currents will not be as accurate as usual, and are for information only. A margin is allowed so that the PET tolerance will not cause failure on a marginal current draw. [7.943,581] - VBUS current drawn = 473mA [8.953,581] - VBUS current drawn = 475mA [9.963,581] - VBUS current drawn = 474mA [10.973,581] - VBUS current drawn = 474mA [11.983,581] - VBUS current drawn = 474mA [12.993,581] - VBUS current drawn = 474mA [14.003,581] - VBUS current drawn = 474mA [15.013,581] - VBUS current drawn = 475mA [16.023,581] - VBUS current drawn = 474mA [17.033,581] - VBUS current drawn = 473mA [18.043,581] - VBUS current drawn = 473mA [19.053,581] - VBUS current drawn = 474mA [20.063,581] - VBUS current drawn = 474mA [21.073,581] - VBUS current drawn = 473mA [22.083,581] - VBUS current drawn = 474mA [23.093,581] - VBUS current drawn = 455mA [24.103,581] - VBUS current drawn = 452mA [25.113,581] - VBUS current drawn = 449mA [26.123,581] - VBUS current drawn = 449mA [27.133,581] - VBUS current drawn = 453mA [28.143,581] - VBUS current drawn = 451mA [29.153,581] - VBUS current drawn = 451mA [30.163,581] - VBUS current drawn = 449mA [31.173,581] - VBUS current drawn = 450mA [32.183,581] - VBUS current drawn = 453mA [33.193,581] - VBUS current drawn = 452mA [34.203,581] - VBUS current drawn = 455mA [35.213,581] - VBUS current drawn = 450mA [36.223,581] - VBUS current drawn = 456mA [36.943,858] Suspending UUT [36.943,867] [36.943,867] - VBUS current watchblock did not detect VBUS current in excess of bMaxPower [36.943,870] 18. Turn off VBUS and disconnect capacitance and pull-down resistance from VBUS. [36.943,871] 19. Disconnect 15k pull-down resistors. [36.943,871] 20. Wait 5 seconds for detachment to be recognized. [36.943,872] [36.943,872] End of Test [36.943,873] Note: Parameters and behavior such as TSVLD_CON_WKB, TDBP_VDPSRC_CON are verified by vendor declaration. [36.943,889] FAILED TEST ===End of Script=============================================== Opening script: CT_PD_REP_DBP.mpet Compile successful Checklist for Portable Devices (PDs) - Dead Battery Provision. -------------------------------------------------------------- DBP1: Does PD draw no more than IUNIT when PD is not able to connect? - NO (FAIL) DBP2: Does PD reduce current drawn to ISUSP within TSVLD_CON_WKB after attach if it is unable to connect and be enumerated? - Vendor Declaration DBP3: Does PD enable VDP_SRC within TDBP_ATT_VDPSRC of attach and maintain it if it is unable to connect? - NO (FAIL) DBP4: Does PD connect within TDBP_ VDPSRC_CON of disabling VDP_SRC ? - Vendor Declaration DBP5: Does PD prevent the use of DBP current to perform tasks unrelated to battery charging? - Vendor Declaration DBP6: If the PD uses the DBP, can the device normally operate stand-alone from internal battery power. - Vendor Declaration DBP7: Can the PD, with a dead battery, pass the inrush test? - Vendor Declaration ===End of Script=============================================== ===End of Test Sequence======================================== ----RESULT SUMMARY---- FAIL - CT_PD_DBP.mpet Pass - CT_PD_REP_DBP.mpet ===End of Report===============================================