- NXP 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
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- 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
-
- 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
- Vigiles
- 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
-
-
- Home
- :
- MCUXpresso Software and Tools
- :
- MCUXpresso SDK
- :
- USB Freezes on KL26
USB Freezes on KL26
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have a custom board with MKL26Z256VLH4 and I'm working with the latest version of its SDK (v2.4.1).
I have exactly the same problem posted with this title "K22 USB device CDC and HID problem"
https://community.nxp.com/t5/MCUXpresso-SDK/K22-USB-device-CDC-and-HID-problem/m-p/817565
My application is similar; the only difference is that my USB device is simpler, infact it is only an HID without CDCs as in the above-mentioned post.
This post suggests a possible solution modifying USB_DeviceHidSend and USB_DeviceHidRecv functions.
The functions in my KL26 SDK are the same of those in the v2.4.1 of K22 SDK.
Analyzing the build of the next K22 SDK (v2.5.0), the two functions has been modified in a different mode compared to the one indicated in the post.
In the last K22 SDK (v2.8.2) the two functions has been modified again returning equal to the v2.4.1 of K22 SDK.
What is the reason for this regression ?
There is an official solution from NXP for the KL26 microcontroller ?
Thank you in advance for your attention.
Best regards,
Daniele
Solved! Go to Solution.
Sabina_Bruce
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Daniele,
Hope you are doing well.
Could you please specify which section of the functions are you referring to. I have checked between the versions you mention and between 2.5 and 2.8.2 of the FRDM-k22 I do not see any difference. The different file out of the three is the SDK version 2.4.1. Where "hidHandle->interruptOutPipeBusy = 1U;" is insider the Interrupt Out Pipe Stall if-statement.
If you change this line to match the new versions does it fix the behavior you are experiencing?
Best Regards,
Sabina
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Sabina_Bruce
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Daniele,
Hope you are doing well.
Could you please specify which section of the functions are you referring to. I have checked between the versions you mention and between 2.5 and 2.8.2 of the FRDM-k22 I do not see any difference. The different file out of the three is the SDK version 2.4.1. Where "hidHandle->interruptOutPipeBusy = 1U;" is insider the Interrupt Out Pipe Stall if-statement.
If you change this line to match the new versions does it fix the behavior you are experiencing?
Best Regards,
Sabina
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Sabina.
I changed this line to match the new version and the problem is solved !
Thank you.
Best regards,
Daniele.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have a custom board with MKL26Z256VLH4 and I'm working with the latest version of its SDK (v2.4.1).
I have exactly the same problem posted with this title "K22 USB device CDC and HID problem"
https://community.nxp.com/t5/MCUXpresso-SDK/K22-USB-device-CDC-and-HID-problem/m-p/817565
My application is similar; the only difference is that my USB device is simpler, infact it is only an HID without CDCs as in the above-mentioned post.
This post suggests a possible solution modifying USB_DeviceHidSend and USB_DeviceHidRecv functions.
The functions in my KL26 SDK are the same of those in the v2.4.1 of K22 SDK.
Analyzing the build of the next K22 SDK (v2.5.0), the two functions has been modified in a different mode compared to the one indicated in the post.
In the last K22 SDK (v2.8.2) the two functions has been modified again returning equal to the v2.4.1 of K22 SDK.
What is the reason for this regression ?
There is an official solution from NXP for the KL26 microcontroller ?
Thank you in advance for your attention.
Best regards,
Daniele
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have a custom board with MKL26Z256VLH4 and I'm working with the latest version of its SDK (v2.4.1).
I have exactly the same problem posted with this title "K22 USB device CDC and HID problem"
My application is similar; the only difference is that my USB device is simpler, infact it is only an HID without CDCs as in the above-mentioned post.
This post suggests a possible solution modifying USB_DeviceHidSend and USB_DeviceHidRecv functions.
The functions in my KL26 SDK are the same of those in the v2.4.1 of K22 SDK.
Analyzing the build of the next K22 SDK (v2.5.0), the two functions has been modified in a different mode compared to the one indicated in the post.
In the last K22 SDK (v2.8.2) the two functions has been modified again returning equal to the v2.4.1 of K22 SDK.
What is the reason for this regression ?
There is an official solution from NXP for the KL26 microcontroller ?
Thank you in advance for your attention.
Best regards,
Daniele
