Module 7: Avoiding Pitfalls and Feature Mapping

Learn the key MPLAB commands in the Command Palette:

• MPLAB: Create Project
• MPLAB CMake: Full Build
• MPLAB: Data Visualizer
• MPLAB: Edit Project Properties

Users open a .X project folder and expect it to behave exactly like it does in MPLAB X IDE.

The project usually needs to be imported using the Project Importer extension.

To avoid problems:

1. Import the MPLAB X IDE project by simply opening the folder.
2. Check any generated project configuration files to ensure they are correct.
3. Check any imported configurations before building.

After installing a compiler:

• Run MPLAB: Reinitialize Toolchains Registration
• If necessary, manually register the compiler by running MPLAB: Add Toolchain

Users often look for MPLAB X IDE-style project property windows and build configuration dialogs.

Learn where the project configuration files are stored and understand:

• .vscode - this project-specific folder contains configuration files
• *.mplab.json
• CMake configuration files

but VS Code heavily uses a CMake-based workflow:

• MPLAB CMake: Full Build
• MPLAB CMake: Clean Build

Understand that Configure, Generate, and Build are separate steps when troubleshooting build issues.

Users sometimes open the wrong folder level.

VS Code distinguishes between: Folders, Workspaces, and Projects

For VS Code:

• Open the correct project root.
• Save a workspace file for multi-project development.
• Keep related repositories in the same workspace when appropriate.

Before attempting to debug, verify:

• Debug probe selection
• Launch configuration
• Device selection
• Project configuration

When things fail:

• Check the Output window
• Check MPLAB extension logs
• Verify toolchain registration
• Ensure device packs are installed