MCUXpresso SDK USB Power Delivery

Size: px

Start display at page:

Download "MCUXpresso SDK USB Power Delivery"

Brianna Singleton
5 years ago
Views:

1 NXP Semiconductors Document Number: Quick Start Guide Rev. 1.0, 04/2017 MCUXpresso SDK USB Power Delivery 1. Introduction Today many devices charge or get their power from USB port connected in laptops, cars or wall sockets. Users need USB to fill their requirements not only in terms of data but also to provide power to, or charge their devices. The USB Power Delivery Specification enables the maximum functionality over a single cable. Some spec. features include: Increased power level from existing USB standards, power direction is no longer fixed, optimize power management across multiple peripherals, intelligent and flexible system level management of power, allows low power cases. This document includes step-by-step instructions to run MCUXpresso USB Power Delivery stack. Contents 1. Introduction Software Folder structure Building the Demo Running the Demo Hardware Demo setup Setup FRDM-KL27Z and USB-PD/Type C Shield boards Request from original sink role Power swap from sink role Request from original source role Power swap from source role Hard Reset test Test other commands PD compliance test Known issues NXP B.V.

2. Software The software is built based on MCUXpresso SDK2.2 FRDM-KL27Z package. 2.1.

2 2. Software The software is built based on MCUXpresso SDK2.2 FRDM-KL27Z package Folder structure Folder boards/ CMSIS/ devices/ docs/ middleware/ rtos/ boards/frdmkl27z/usb_examples/ middleware/usb_1.6.3/pd Description MCUXpresso SDK2.2 FRDM-KL27Z package directory. There are three USB Power Delivery demos project. USB Power Delivery source codes. 2 NXP Semiconductors

3 Note: There is another doc called MCUXpresso SDK USB PD Stack Reference Manual in the docs/usb directory. You can see the detail description of the MCUXpresso USB PD stack in this doc Building the Demo The demo projects are located in the path below, <root>/boards/frdmkl27z/usb_examples/usb_pd <root>/boards/frdmkl27z/usb_examples/usb_pd_battery <root>/boards/frdmkl27z/usb_examples/usb_pd_source_charger To build the projects please refer to section 3 in SDK root/docs/getting Started with MCUXpresso SDK.pdf Note. 1. This doc introduces the common PD functions based on the usb_pd demo in <root>/boards/frdmkl27z/usb_examples/usb_pd. 2. The Debug target of usb_pd demo cannot be built because of the SOC limit Flash, to pass the build, the customer needs to change the optimization level from o0 to o2. 3. For the usb_pd_battery and the usb_pd_source_charger example usage, you can refer to the readme in the demos directory Running the Demo Please refer to section 3 in SDK root/docs/getting Started with MCUXpresso SDK.pdf Note. Please make sure the default debug interface is J-Link/J-Trace, and please refer to section 3.2 in SDK root/docs/getting Started with MCUXpresso SDK.pdf for the detailed step to configure the debug interface NXP Semiconductors 3

Shield board Rev 1. FRDM-KL27Z and USB-PD/Type C Shield board 4.

4 3. Hardware Because PD stack needs one provider and one consumer, the demo hardware needs two same set of devices: FRDM-KL27Z and USB-PD/Type C Shield board Rev 1. FRDM-KL27Z and USB-PD/Type C Shield board 4. Demo setup The following instructions show how to run the demo. 4 NXP Semiconductors

5 4.1. Setup FRDM-KL27Z and USB-PD/Type C Shield boards a) Connect the OpenSDA USB port J13 of the frdm-kl27z to the PC. b) The jumpers sets of shield board are as follow picture: J5: 1-2, J4: 1-2, J11: 1-2, J12: 1-2, J13: 1-2, J14:1-2 c) Connect a 9V power source to the J1 jack in the USB-PD/Type C Shield board. The shield LEDs status are as follow: NXP Semiconductors 5

6 d) Make sure you run the usb_pd demo by the instructions at Section 2.3 e) pd init success will print in the debug console Request from original sink role a) Connect a USB Type-C cable between two boards, one will works as sink and one works as source, you can see it through the debug console. b) Connect a voltmeter to VBus of the sink role board. The voltmeter at the sink role shall show 5V. 6 NXP Semiconductors

7 c) Long press SW1 for about 3s on the frdm-kl27z board to make 9V request. After the request is completed successfully, the voltmeter shall show 9V. d) Short press SW1 on the frdm-kl27z board to make 5V request. After the request is completed successfully, the voltmeter shall show 5V Power swap from sink role a) Short press SW3 on the sink s frdm-kl27z board to make PR_SWAP. b) The Voltage of the vbus will drop to 0V and then back to 5V Request from original source role a) Connect a voltmeter to VBus of the new sink role board. After the power role swap the original source role becomes the sink role. The voltmeter at the source role shall show 5V. NXP Semiconductors 7

8 b) Long press SW1 for about 3s on the frdm-kl27z board to make 9V request. After the request is completed successfully, the voltmeter shall show 9V. c) Short press SW1 on the frdm-kl27z board to make 5V request. After the request is completed successfully, the voltmeter shall show 5V. 8 NXP Semiconductors

4.5. Power swap from source role a) Short press SW3 on the source s frdm-kl27z board to make PR_SWAP. b) The Voltage of the vbus will drop to 0V and then back to 5V. 4.6.

9 4.5. Power swap from source role a) Short press SW3 on the source s frdm-kl27z board to make PR_SWAP. b) The Voltage of the vbus will drop to 0V and then back to 5V Hard Reset test a) Long press SW3 on the frdm-kl27z board to make HARD_RESET. b) The Voltage of the vbus will drop to 0V and then back to 5V. c) Source and sink state machine will re-start and sink will request power again, you can see the logs in the debug console Test other commands a) Input 0 in the debug console, the follow menu will print in the debug console (the menu is little different for source and sink): NXP Semiconductors 9

b) Input the menu to test the corresponding command. c) For example: you input f, data role swap command will start, the debug console will print the result. 5.

10 b) Input the menu to test the corresponding command. c) For example: you input f, data role swap command will start, the debug console will print the result. 5. PD compliance test Hardware: Ellisys USB explorer 350 Software: Ellisys USB explorer 350 examiner version The usb_pd example support the PD2.0 compliance test with ellisys ex350 device. To do compliance test the follow configurations need be enable in the usb_pd_config.h file. PD_CONFIG_COMPLIANCE_TEST_ENABLE, PD_CONFIG_TRY_SNK_SUPPORT and PD_CONFIG_TRY_SRC_SUPPORT. Five configurations are verified and passed: correspondingly, one dedicated MACRO and one VIF files are needed to enable each of them. The MACROs are defined in the pd_app.c and the VIF files are in boards\frdmkl27z\ usb_examples\usb_pd\freertos\vif: Dual-role port PD_COMPLIANCE_TEST_DRP needs to be enabled in pd_app.c and the file drp.txt is the dedicated VIF file for this test. Dual-role port with Try.SNK PD_COMPLIANCE_TEST_DRP_TRY_SNK needs to be enabled in pd_app.c and the file drp_try_snk.txt is the dedicated VIF file for this test. 10 NXP Semiconductors

Note: Dual-role port with Try.SRC PD_COMPLIANCE_TEST_DRP_TRY_SRC needs to be enabled in pd_app.c and the file drp_try_src.txt is the dedicated VIF file for this test.

11 Note: Dual-role port with Try.SRC PD_COMPLIANCE_TEST_DRP_TRY_SRC needs to be enabled in pd_app.c and the file drp_try_src.txt is the dedicated VIF file for this test. Consumer/Provider port PD_COMPLIANCE_TEST_CONSUMER_PROVIDER needs to be enabled in pd_app.c and the file consumer_provder.txt is the dedicated VIF file for this test. Provider/Consumer port PD_COMPLIANCE_TEST_PROVIDER_CONSUMER needs to be enabled in pd_app.c and the file provder_consumer.txt is the dedicated VIF file for this test. 1. Only one macro can be enable at the same time for these five configurations. 2. The DisplayPort related test items are not included. 6. Known issues Two issues are found during the compliance test as below. Hardware: Ellisys USB explorer 350 NXP Semiconductors 11

12 Software: Ellisys USB explorer 350 examiner version Issue1: TD.PD.LL.E2 Issue2: TD NXP Semiconductors

14 How to Reach Us: Home Page: nxp.com Web Support: nxp.com/support Information in this document is provided solely to enable system and software implementers to use NXP products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits based on the information in this document. NXP reserves the right to make changes without further notice to any products herein. NXP makes no warranty, representation, or guarantee regarding the suitability of its products for any particular purpose, nor does NXP assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. Typical parameters that may be provided in NXP data sheets and/or specifications can and do vary in different applications, and actual performance may vary over time. All operating parameters, including typicals, must be validated for each customer application by customer s technical experts. NXP does not convey any license under its patent rights nor the rights of others. NXP sells products pursuant to standard terms and conditions of sale, which can be found at the following address: nxp.com/salestermsandconditions. NXP, the NXP logo, NXP SECURE CONNECTIONS FOR A SMARTER WORLD, and Tower, are trademarks of NXP B.V. All other product or service names are the property of their respective owners. ARM, the ARM Powered logo, and Cortex are registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved NXP B.V.

i.mx 7 Dual/Solo Product Lifetime Usage

NXP Semiconductors Document Number: AN5334 Application Note Rev. 1, 05/2017 i.mx 7 Dual/Solo Product Lifetime Usage 1. Introduction This document describes the estimated product lifetimes for the i.mx