Home > On-Demand Archives > Theatre Talks >
Dive Deeper into NXP's MCUXpresso Ecosystem for VS Code and Application Development
Kyle Dando - NXP - Watch Now - Duration: 40:22
***** Giveaway Alert! *****
Watch this talk before May 5, 2024, for a chance to win one of 30, that's right, 30 FRDM Development Board for MCX N94/N54 MCUs !!!
NXP’s MCUXpresso Ecosystem has added exciting new advantages for developers. NXP’s Visual Studio Code extension makes it easy to use the MCUXpresso suite of software and tools. In addition, the new Application Code Hub provides quick access to examples from NXP’s internal experts that solve challenging requirements of popular applications. Learn how you can benefit from VS Code and the Application Code Hub.
Excellent presentation. I definitely need to try these VScode extensions. I see it is very similiar to the workflow of Nordic SDK, and it might not be a coincidence due to Zephyr support. I am very interested in the LPC59 family but definitely I'd like to start with the N94/N54 board.
Thank you Kyle.
Love to see NXP adopt VS Code for editing, deployment, and debugging. This is enticing to try the boards.
Interested in the FRDM-MCX.
Does the MCUXpresso VSCode extension only work with the Cortex-M series chips or others as well?
Thank you for your great job presenting NXP flavored VS Code!
What missing debug feature do you want to see added to NXP’s Visual Studio Code extension?
Thank you very much for this overview!
It would be nice to see integrated in VSCode a way to generate a project through a gui like MCUXpresso Config Tools for both MCUXpresso SDK and Zephyr.
For debug porpuses:
- is there a disassembly view?
- when using an RTOS is it possible to debug using thread aware?
Thank you again
How can I convert existing MCUXpresso projects to CMake based VSCode projects? I've been struggling with this.
@dcblack
You can review online documentation MCUXpresso IDE Project Converter
The Project Import wizard handles all of the conversion.
You select the folder with the existing MCUXpresso IDE project.
The Wizard notes that it detects the MCUXpresso project in the folder. (Also notes issues)
You select location for converted project. It then converts for VS Code.
Only issue is that the existing project must be Built successfully. That provides the necessary linker file for the conversion.
Interested in the FRDM-MCX.
I'd like to signup for the draw of the development boards.
This happens automatically when you watch the session. Thanks.
Re:
Watch this talk before May 5, 2024, for a chance to win one of 30, that's right, 30 FRDM Development Board for MCX N94/N54 MCUs !!!
Apart from watching the video (which I already did yesterday as "gmacario", see below) what else should I do to have a chance of getting one Eval Board?
Thanks for the presentation, great job!
I am interested in receiving one of the coupons for a free eval boards if you have any left.
Thanks.
Thank you for the presentation. MCUXpresso and VS Code a great combination to test
Thanks for the presentation. Not a big fan of Visual Studio but I like to keep up to date on NXP development updates.
Very good presentation Kyle. All of these tools look promising. I will definitely be trying out Microsoft Visual Studio Code for NXP with SDK and Zephyr.
Are the settings for the debug configurations at parity with MCUExpressoIDE?
*Specifically configuring JLink Server (Ex. switching between JTAG and SWD, connecting to an external vs creating a new one)
Hi Kyle,
Thank you for the informative video.
Can I use the card of NXP with ESP 32 and program it using NXP's MCUXPRESSO ?
Hi Kyle,
Thank you for the informative video! It is nice to see more and more manufacturers embracing VS code and adding plugins/extensions for it.
VS Code is great for setting up individual developers, but not ideal for setting up CI/CD.
Are there any pointers on how to leverage this for setting up a CI/CD?
Does NXP have plans to support build systems like bazel ?
Thanks for the video!
Hi Kyle,
For the VS Code Tools, are there any plans, or a roadmap for support for the CLANG compiler for your components?
Also, it wasn't clear if you have control over the versions of components such as GCC, and how those components are maintained (local workspace or shared locations?).
Thanks for the video!
Thank you for the informative presentation. I have one question about the debugger: does it support thread-level debugging on Zephyr apps? I mean, can we set a breakpoint on one thread while leaving the other threads running?
Thanks for the great overview of the vscode support you've added. What of interest to me is support for building with a toolchain/sdk in a docker container to ensure a consistent build environment and also to build using docker on our jenkins build server. It would be great if this was integrated into your plug in.
Just watched the Q&A. Thanks for the response!
Is it possible to convert existing MCUXpresso IDE project to VSCode? Is there a guide which explains how to perform such process which also contains solutions to common problems?
What DSP tools and librarier are available for MCX N94 ?
What tools are available, whether thru Visual Studio Code or not, for GUI development?
What IDE supports the latest MISRA C standard? What level does MCUXpresso or Visual Studio Code support?
Which debug interfaces are supported?
Hi KyleDando-NXP, thanks for your sharing. Can we import a .elf file from a custom build cmake project and debug using NXP’s Visual Studio Code extension?
More verbose output from your Zephyr installer and hints what to do in case it gets stuck would be helpful.
When I tried the installer from within the VSCode plugin on Windows, it first stoppped at not finding gperf sources. Had to manually install gperf. After that it stopped with the message "not finding pip" (but root cause was i had no py.exe).