This video series shows the steps for getting started. It is a video walkthrough to help visualize the steps detailed in "Installation steps for MCUXpresso for VS Code".
Part 1: MCUXpresso for Visual Studio Code
NXP has made it easier for developers to work with NXP microcontrollers in Visual Studio Code. The user can get a high-level overview of the NXP support at www.nxp.com/vscode.
You will need the following software:
MCUXpresso Installer (Win; MacOS; Linux)
Microsoft Visual Studio Code Download
Part 2: What MCUXpresso Installer Prepares
Why do you need to use MCUXpresso Installer? There are many required tools to support embedded development within Visual Studio Code. This program installs the required tools so the user does not need to understand the complex dependencies to configure the different environments.
Part 3: Add the MCUXpresso for VS Code Extension
The NXP extension will eventually be installed by visiting the Extension Marketplace found in Visual Studio Code. Until the public launch in July 2023, the extension can be manually added in the Extensions menu found by clicking the ellipsis to the right of the extensions search bar.
You will require the latest extension. Download: mcuxpresso-0.5.60.vsix
Part 4: Review the MCUXpresso Perspective
The NXP extension provides a perspective within Visual Studio Code that makes it easy to view the necessary information, resources and tools.
Part 5: Add a Software Repository / SDK
The NXP extension provides a tool that imports software repositories from popular sources. The developer can import from a remote repo, NXP archive file, or an existing local repo.
Part 6: Import the first Project
The NXP extension provide a Project Importing tool. It is quick and easy to browse available projects and add them to the current workspace. Users can import from a repository or an existing local project.
Part 7: Build a Project in VS Code
The NXP installer and extension prepares the toolchain for your platform. After completing the installer and extension, NXP projects should build properly.
Part 8: Start a Debug Session
The NXP extension has added support to launch the default tools within VS Code using popular Debug Probes. Segger J-Link, NXP LinkServer and PE Micro debug probes are identified and configured. The Debug session launches and the user is able to analyze their project.
An error has occurred when reading existing sub-variable "Language_PG_Configuration"; see cause exception! The type of the containing value was: extended_hash+string (lithium.coreapi.webui.template.models.NamedValueByNameTemplateModel wrapped into f.e.b.StringModel)
----
FTL stack trace ("~" means nesting-related):
- Failed at: #assign redirect_lingo_page_url = web... [in template "language_macro_header.ftl" at line 173, column 1]
- Reached through: #include "language_macro_header.ftl" [in template "Language_translator_Dashboard" at line 3, column 1]
----
An error has occurred when reading existing sub-variable "Language_PG_Configuration"; see cause exception! The type of the containing value was: extended_hash+string (lithium.coreapi.webui.template.models.NamedValueByNameTemplateModel wrapped into f.e.b.StringModel)
----
FTL stack trace ("~" means nesting-related):
- Failed at: #assign redirect_lingo_page_url = web... [in template "language_macro_header.ftl" at line 173, column 1]
- Reached through: #include "language_macro_header.ftl" [in template "Language_CP_BulkTranslation_Angular" at line 33, column 5]
----
The following has evaluated to null or missing:
==> translatorRole [in template "Language_CP_BulkTranslation_Angular" at line 36, column 14]
----
Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing#if>. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)??
----
----
FTL stack trace ("~" means nesting-related):
- Failed at: #if translatorRole == "" || roleStatu... [in template "Language_CP_BulkTranslation_Angular" at line 36, column 9]
----