Arm Keil MDK v6 Essential and Professional editions are now available to buy as monthly or annual subscriptions from our Developer Tools store. Visit the store to get access to the tools suite today!

  1. Packs
  2. PIC32CM-MC_DFP

PIC32CM-MC_DFP

1.5.244
Microchip

  • Pack Type

    Device Support

Microchip PIC32CM-MC Series Device Support

Overview

The Microchip PIC32CM-MC Series Device Family Pack (DFP) is a CMSIS-Pack that:

Related packs

    - pack: ARM::CMSIS

Devices

PIC32CM1216MC00032

The Microchip PIC32CM series of 5V Cortex M0+ devices is designed for consumer, commercial, industrial and automotive applications in noisy environments. These products feature robust communications peripherals including the SERCOM module and LIN, along with advanced motor control peripherals. These devices operate from a true 5V supply (2.7 to 5.5V) offering increased robustness in applications such as home appliance motor control by increasing the dynamic range of the ADC above the common noise floor. Application demo code including Sensorless FOC motor control is available via the Motor Control Library featured in HarmonyV3Supported by MPLAB X IDE, and MPLAB Harmony. In addition, external tools from vendors KEIL and IAR are also supported. Functional SafetyThis device supports the IEC 61508 (SIL 2/3) Functional Safety standard.  ·   To request any information about the SIL 2/3 STL, please fill out and submit the request form on Industrial Safety Self-Test Library web page·  Learn more about  32-bit MCUs with Functional Safety capabilities including device hardware and certified software libraries. 

Documentation:

Application Notes:

Additional Documents:

PIC32CM1216MC00048

The Microchip PIC32CM series of 5V Cortex M0+ devices is designed for consumer, commercial, industrial and automotive applications in noisy environments. These products feature robust communications peripherals including the SERCOM module and LIN, along with advanced motor control peripherals. These devices operate from a true 5V supply (2.7 to 5.5V) offering increased robustness in applications such as home appliance motor control by increasing the dynamic range of the ADC above the common noise floor. Application demo code including Sensorless FOC motor control is available via the Motor Control Library featured in HarmonyV3Supported by MPLAB X IDE, and MPLAB Harmony. In addition, external tools from vendors KEIL and IAR are also supported. Functional SafetyThis device supports the IEC 61508 (SIL 2/3) Functional Safety standard.  ·   To request any information about the SIL 2/3 STL, please fill out and submit the request form on Industrial Safety Self-Test Library web page·  Learn more about  32-bit MCUs with Functional Safety capabilities including device hardware and certified software libraries. 

Documentation:

Application Notes:

Additional Documents:

PIC32CM6408MC00032

The Microchip PIC32CM series of 5V Cortex M0+ devices is designed for consumer, commercial, industrial and automotive applications in noisy environments. These products feature robust communications peripherals including the SERCOM module and LIN, along with advanced motor control peripherals. These devices operate from a true 5V supply (2.7 to 5.5V) offering increased robustness in applications such as home appliance motor control by increasing the dynamic range of the ADC above the common noise floor. Application demo code including Sensorless FOC motor control is available via the Motor Control Library featured in HarmonyV3Supported by MPLAB X IDE, and MPLAB Harmony. In addition, external tools from vendors KEIL and IAR are also supported. 

Documentation:

Application Notes:

Additional Documents:

PIC32CM6408MC00048

The Microchip PIC32CM series of 5V Cortex M0+ devices is designed for consumer, commercial, industrial and automotive applications in noisy environments. These products feature robust communications peripherals including the SERCOM module and LIN, along with advanced motor control peripherals. These devices operate from a true 5V supply (2.7 to 5.5V) offering increased robustness in applications such as home appliance motor control by increasing the dynamic range of the ADC above the common noise floor. Application demo code including Sensorless FOC motor control is available via the Motor Control Library featured in HarmonyV3Supported by MPLAB X IDE, and MPLAB Harmony. In addition, external tools from vendors KEIL and IAR are also supported. 

Documentation:

Application Notes:

Additional Documents:

MISRA-C:2023 Compliance Deviations List

Deviation ID: MFWCG-40

  • Rule 5.5: Identifiers shall be distinct from macro names.
  • Use case: Identifiers corresponding to register names.

Example:

```C typedef union { struct { uint32_t GPIO:29; uint32_t :3; } vec; uint32_t reg; } ECIA_SRC8_Type;

#define GPIO (0x40081000) ```

  • Reason: Access to hardware.

The macros expand into the same identifiers, which allow users to detect for the presence of specific registers during preprocessing.

  • Scope: Device headers for the DEC15xx and MEC15xx family (<device-name>.h).

Deviation ID: MFWCG-42

  • Rule 20.9: All identifiers used in the controlling expression of #if or #elif preprocessing directives shall be #define'd before evaluation.
  • Use case: Use of compiler builtin macros.

Example:

C #ifdef (__ARM_FP == 14) || (__ARM_FP == 4) fpu_enable(); #endif

  • Reason: Access to hardware.

Headers may rely on builtin macros from the compiler and are written under the assumption that if the macro is not defined, its value is zero.

  • Scope: All device headers (<device-name>.h).

Deviation ID: MFWCG-43

  • Rule 21.1: #define and #undef shall not be used on a reserved identifier or reserved macro name.
  • Use case: Reserved names, beginning with _ followed by a capital letter or __ followed by a lower-case are within the compiler's namespace.

Example:

C #define __IO volatile

  • Reason: Access to hardware; Code Quality (Usability: Accessibility).

Within these headers originate many reserved names that are within the compiler's namespace.

  • Scope: All device headers (<device-name>.h).

Deviation ID: MFWCG-44

  • Rule 21.2: A reserved identifier or reserved macro name shall not be declared.
  • Use case: Reserved names, beginning with _ followed by a capital letter or __ followed by a lower-case are within the compiler's namespace.

Example:

C extern const VECTOR_TABLE_Type __VECTOR_TABLE;

  • Reason: Access to hardware; Code Quality (Usability: Accessibility).

Within these headers originate many reserved names that are within the compiler's namespace.

  • Scope: All device headers (<device-name>.h).

Support

For support questions, contact Microchip Support through https://www.microchip.com/en-us/support.