Migrating from Atmel Studio IDE to the MPLAB® X IDE

Although MPLAB^® X IDE and Microchip Studio (formerly Atmel^® Studio) are two different Integrated Development Environments (IDEs), there are many functional similarities. Understanding these similarities, as well as the differences, will simplify migration.

Terminology Differences

		Description
Main Project	Startup Project	Project that contains main() code.
Make	Build	Compile project files. If a new project, compile all files. Otherwise, compile files that have changed.
Clean and Build	Rebuild	Delete all generated files and compile all files in the project.
Run	Start	Begin program execution.
Configuration Bits	Fuses	Bits in special registers that configure device operation.

Concept Differences

Concept			Notes
Make for debug / production	Program Device for Debugging Main Project Make all the files in the project and add a debug executive to the build image. Remove previous build files and make all the files in the project. Add a debug executive to the built image.	Same compiler settings for Debug/Production Developers may set compiler optimization to a lower  level when debugging, but Make/Build is the same. Studio 7 has no such differentiation since a debug executive is not needed for debugging. Debugging is supported through different means.	N/A
Configuration Bits / Fuses	Configuration (Config) Bits Have a default value on RESET. SOFT recovery: Just reset the part if values don't work. Config bit values in HEX file.	Fuses Independent of chip reset, default value from factory (available in the datasheet). HARD recovery: Fuse settings should be chosen with care. Note: If an external clock source fails while used as CLK_MAIN source, only the WDT can provide a mechanism to switch back via System Reset. Fuse values in ELF file.	N/A
Project/Solution	Organizes development at a project level. A project can be stand-alone or work with other projects.	Organizes development at a solution level. A solution is comprised of a number of related projects.	N/A
Read Device ID / Signature	Device ID read automatically by hardware tool. Click image to enlarge.	Verifying a kit connection in Studio 7 is often done by reading a device signature. Click image to enlarge.	N/A
Communication Interface for PIC® / AVR® MCU	In-Circuit Serial Programming™ (ICSP™) communication between debug tool and target PIC device. MPLAB REAL ICETM in-circuit emulator provides additional communications options for trace.	There are a number of communication interfaces for different families of AVR and SAM MCUs.	N/A
Set/Clear Bit Values	Clear bit: Bit value = 0 Set bit: Bit value = 1	Clear bit: Bit value = 1	N/A

Although functionality may be similar, behavior may not be exactly equivalent. The tables below show the commands related to Programming and Launching Debug Sessions, and what functionality is associated with each, both in MPLAB X IDE v4.xx and Atmel Studio 7.

Programming and Debug Launch IDE Comparisons

Function	IDE	Button / Shortcut	Description	Notes
Execute Program		Run Main Project	Build-program-execute	Essentially equivalent functionality: MPLAB X IDE builds project. Studio builds all projects in solution.
		Start Without Debugging	Project (Solution - Studio 7) is built (if changes have been made), device is programmed and program begins execution.
Build Program		Build, Clean and Build	Make all the files in the project.
		Rebuild solution	Remove previous build files and make all the files in the project.	Studio 7 shows warnings only the first time files are built, but bugs are always shown. A rebuild is needed to see all compiler warnings.
Debug Program		Debug run main project	Run code in the project specified as main.
		Start debugging	Start debugging a solution.