MCC in VS Code®: Introduction to Multiple MCC- and MPLAB® Project-Configurations | Videos
MCC in VS Code®: Introduction to Multiple MCC- and MPLAB® Project-Configurations
Getting Started Using MCC Harmony in VS Code® (for PIC32C and SAM Development) Playlist:
https://youtube.com/playlist?list=PLtQdQmNK_0DTGNRV0qKkIEFn2fmrN0q31&si=K9Z9WB0hkz-LrlSh
Getting Started with MPLAB® Melody in VS Code® (for PIC16/PIC18/AVR Development) Playlist:
https://youtube.com/playlist?list=PLtQdQmNK_0DTt4jZ7BQiFBV51zTt3MGqO&si=evOSLi5ww8ycAe0R
Managing multiple MCC- (MPLAB® Code Configurator) and MPLAB Project-configurations can be confusing. Should you keep everything in one project with multiple configurations, or use separate related projects in a shared workspace?
In this introduction video, we explain:
• What an “MPLAB project configuration” is
• When it makes sense to use multiple MCC configurations inside a single project (same device & toolchain = more likely)
• When separate projects are cleaner (different devices, toolchains, or board variants)
• Real-world examples from MCC Melody (Printf, Data Streamer, DV-Run-Time) and MPLAB Harmony (supporting two different boards)
• By the end, you’ll know exactly how the options are available to you, in terms of structuring your projects for maximum clarity and reuse — whether you’re targeting one device with multiple feature sets or supporting completely different hardware.
To view this video, please click manage cookies below and accept functional cookies.
{"SalesForceSecurePath":"https://microchip.my.salesforce-scrt.com","EmbeddedServiceName":"Messaging_For_Microchip","SalesForcePath":"https://microchip.my.site.com/ESWMessagingForMicrochi1755319480924","AgentAvailableHeader":"No problem. Chat with our engineering experts or schedule a call that's convenient for you.","ScheduleCallUrl":"https://microchip.my.site.com/schedulemeetingportal/s/","SalesforceOrgId":"00Do0000000KAkK","JsUrl":"https://microchip.my.site.com/ESWMessagingForMicrochi1755319480924/assets/js/bootstrap.min.js"}