- 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
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- 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
- S32Z/E
-
- 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
- Generative AI & LLMs
-
- 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
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- General Purpose Microcontrollers
- :
- LPC Microcontrollers
- :
- Missing ACK on USB OUT Transactions
Missing ACK on USB OUT Transactions
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Missing ACK on USB OUT Transactions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My team is having some issues with missing ACKs on USB OUT transactions.
Some info on our system:
* The MCU is LPC5528
* SDK version is 26.03.00.
* For call to USB_DeviceInit, we supply kUSB_ControllerLpcIp3511Fs0 as the first parameter (controllerId) so we're using USB full speed.
It's hard to say much about patterns. What we can state is:
* When we send a lot of messages over USB, once in a while an OUT transaction is missing the ACK. We've caught this with an Ellisys USB analyser. We can see the missing OUT, then 3 retries from the PC and then a USB reset.
* It happens rarely. We set up a script repeating the same simple USB message (target just returns some data, no heavy computing etc.). Sometimes it takes a few iterations, other times thousands of iterations, before the error happens.
We'd like to know if this is a known issue or perhaps there are some tricks to debugging it.
Harry_Zhang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have checked the errata of LPC55S2x/LPC552x and have not found any known issues with the lack of ACK directy corresponding to USB0 full speed device OUT. Currently, USB errata mainly focuses on high-speed mode, so it is not directly applicable to your configuration.
From the phenomenon, the more likely reason is that the OUT endpoint did not prepare the receiving buffer in a timely manner at certain moments, resulting in the device being unable to respond to ACK when the host sends OUT, triggering retry or even reset. It is recommended to focus on confirming whether USB_SeviceRecvRequest() is immediately called after each OUT is completed, and try to minimize the processing in the callback. It is also recommended to check the priority of USB interrupts, avoid long shutdown interrupts.
BR
Harry
