- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- How to set up USBHS dual role / OTG on Kinetis K70F150
How to set up USBHS dual role / OTG on Kinetis K70F150
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
How to set up USBHS dual role / OTG on Kinetis K70F150
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello folks,
I am trying to get USB OTG or at least a dual role scenario functioning on a K70f150 cuostom board.
We have placed a USB-3300 Phy along with a TPS2052D for VUSB control as well as a TUSB320i to handle the TYPE C connector orientation and We are using MQX 4.2 RTOS.
Our product spec requires that we be able to function as a USB host for MSD as well as be able to function as a USB Device for CDC communication. To date I have modified the base USBH and USBD libraries to run HS. When I compile one or the other into our application I see proper functionality ... eg thumb drives enumerate and read/write or CDC communication is established and data can be passed back and forth between a Host and our system.
It was decided to code this system as dual role for simplicity. We currently have a system where attach and detach events are detected by the TUSB320i. Based on the data provided, the application chooses which stack to use. This functions well for the CDC device aspect. The system recognize the attach, loads the stack and proceeds to communicate. We have no issues with repeated attache/detach events.
The Host MSD side of things however seems to be giving us some issues. It seems that the system can only attach once. If a thumb drive is detached the system can no longer recognize subsequent attach events. When this happens the system does not recognize any form of attach event.
I have tested the system without a stack loaded and it (TUSB320i) continues to see attach/detach events as long as the Host stack does not get loaded. It seems as though the ULPI controller looses contact with the phy and is unable to reconnect/resume. I tried using the various commands in the stack to try to force a reset or a resume but have not had any results.
Triggering the external reset for the phy did not seem to rectify the issue either. It would be difficult to physically cut power to the phy due to our layout so we have avoided that at this point.
Can anyone offer suggestions as to how I should proceed at this point?
Thank you for your time.
