We have a project imported, have built it, time to debug it on the hardware.
VS Code: Debugging
2
Category Archives: Tips & Tricks
VS Code: Building the Project
In a previous article I have imported an example project. Now I want to compile and build it.
Traditionally, the build action inside VS Code is somewhat hidden. There is a keyboard shortcut, but recent additions to VS Code making the build action more accessible.
VS Code: Import Example from MCUXpresso Repository
After having imported the repository with the SDK, it is now time to create a first project.
VS Code: MCUXpresso SDK Repository
In a previous article I have installed the MCUXpresso extension and used the MCUXpresso Installer to install the necessary development tools.
In this article I’m going to import the SDK.
Assigning Nicknames to Debug Probes
Dealing with and debugging distributed systems, I end up with multiple debug probes and target boards on my desk. When starting a debugging session, it can be hard to identify a debug probe by its serial number. What I do in such a situation: put a color stick on the debug probe and have it assigned a nickname.
That nickname then shows up during the debug connection, and I’m sure I connect to the right probe and board that way.
Continue readingVS Code: MCUXpresso Installer
VS Code is managing its extensions (see VS Code: MCUXpresso Extension). But to make it usable for embedded development, you need more tools: compiler, linker, debugger, libraries, build system, debug probe support, …
For the experts, this is not a big deal: you know where to get them, and you install them, as shown with another tutorial. But for a class full of students or newcomers to VS Code, this can be a a time consuming and daunting task.
To make the installation easier, NXP has released a ‘dependency checker and installer’ along with their VS Code extension, which makes the setup much easier and simpler.
VS Code: Telemetry-free VSCodium
“There is no such thing as a free lunch.”
https://en.wikipedia.org/wiki/No_such_thing_as_a_free_lunch
And this applies to VS Code and many of its extensions. You agree to the licensing conditions, and you pay with your data.
VS Code source code is MIT licensed, but the binaries you can download and install have telemetry built in: you are giving Microsoft your usage data in return for using VS Code.
If you are concerned about this, and looking for free and libre open source binaries of VS Code, then have a look at MIT-Licensed VSCodium.
VS Code: Color Themes
Now about the biggest reason why everyone loves VS Code: colors!
Seriously, one of the first things you might change is the color theme, and VS Code features this in the getting started:
VS Code: Getting Started, literally
This is another article in my series about Visual Studio Code. After having it installed (see VS Code: IDE Installation), this one is about starting the IDE
I can start the IDE from the shortcut (if created during the installation) or by typing code in console/command prompt shell (e.g. Windows PowerShell). To be able to use the code command requires VS Code to be present in the PATH.
VS Code: Uninstall completely
Nothing has to last forever, and VS Code might not be the right thing for everyone. VS Code can go overboard with all the extensions and things it had proposed to install. Up to a point that one needs to get re-started again. Or because you tasted VS Code, but you did not like it.
That’s OK, you can uninstall it, after you have installed it (see VS Code: IDE Installation). The catch is: the uninstall does not a full removal, as settings and extensions do not get removed.
This article shows how to fully uninstall VS Code.
Continue reading
MCU on Eclipse 