3.2 Firmware Migration Considerations

Since the application firmware developed for existing 8-bit microcontroller-based designs is not directly compatible with PIC32CM microcontrollers, the firmware requires changes to system module configuration, I/O mapping, and peripheral configuration, depending on the selected microcontroller. Even when the firmware is developed using the MCC tool, the driver or peripheral library code generated for 8-bit microcontrollers with MCC Melody cannot be directly ported to PIC32CM microcontrollers using MCC Harmony and therefore requires modification.

The API References section explains how to access MCC library and driver API documentation and provides guidance on using these APIs within application code. During migration, APIs must be appropriately mapped for system modules such as clock control, interrupts, I/O pin configuration, and the peripherals used in the application. Note that the MCC-generated code handles the initialization of both system and peripheral modules, while developers are responsible for mapping the remaining application code.