There appears to be a new USB Device Stack described in NXP Document Number: MCUXSDKUSBDAPIRM, Rev. 0, Oct 2025 [https://mcuxpresso.nxp.com/mcuxsdk/25.12.00-pvw1/html/_static/usb/MCUXpresso_SDK_USB_Stack_Device_Re...]. I would like to use this to implement a USB CDC ACM (VCOM) class driver for an LPC55S26 based project.
As far as I can see the new stack is not installed into a new project via MCUXpresso IDE Config Tools. According to online NXP instructions I have seen [https://mcuxpresso.nxp.com/mcuxsdk/latest/html/middleware/usb/docs/MCUXSDKUSBSUG/topics/developing_a...] it appears to require copying files and configuration from one of the examples projects included in the latest MCUXpresso SDK. This seems a bit hokey but if this is what is required, ok.
However I would like to get confirmation of this before I spend too much time on. Any feedback or guidance would be much appreciated.
I checked and found that the two demo projects ...cdc_vcom_bm and ... cdc_vcom_bm_lite look extremely complex and difficult to leverage without major effort (shades of the NFC reader stack).
In contrast IDE support for the USB Device stack middleware using Config Tools - Peripherals seems pretty straightforward. Is there any reason not to use the built-in IDE implementation?
Hi @MarkPotts
I think you can
BR
Harry
Thanks for the feedback. I think this is the approach I'll try. I also found the following article which looks helpful: https://community.nxp.com/t5/LPC-Microcontrollers-Knowledge/Using-ConfigTool-to-create-USB-Project-F....
I'm still not very clear on the relationship between the "new" USB stack and the SDK installed version.
Hi @MarkPotts
The SDK USB stack was released since 2016, it is not a new stack. You can get different releases from the mcuxpresso.nxp.com.
You can refer to the SDK USB examples or use the peripheral config tool to implement your own USB application. Both are OK, the config tool works based on the SDK USB stack, it provides one GUI way to configure the usb application.
Note: The Config tool don't support all the SDK USB stack classes (like: cdc ecm etc).
Thanks for breaking down the changes in the USB Device Stack—this update will definitely make device management more transparent. For those who need additional guidance on legal documentation, I found the Franklin court access resource very helpful in understanding procedural records. It’s great to see tools that make complex systems easier to navigate. This kind of clarification really helps both beginners and advanced users stay informed.
Thanks for breaking down the updates in the new USB Device Stack. For those who need related administrative or procedural references, I found the Lake court documents section really helpful in providing organized access to recent filings and case management details. It complements technical documentation by offering a clear view of official records. This makes staying updated on both device changes and corresponding procedural implications much easier.