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-LS_DFP

PIC32CM-LS_DFP

1.4.351
Microchip

  • Pack Type

    Device Support

Microchip PIC32CM-LS Series Device Support

Overview

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

Related packs

    - pack: ARM::CMSIS

Devices

PIC32CM1216LS00032

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM1216LS00048

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM2532LS00048

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM2532LS00064

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM2532LS00100

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS00048

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS00064

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS00100

PIC32CM LS00 family of devices based on Arm® Cortex®-M23 processor bring ultra-low power, superior touch, security and smart analog integration in one chip. They feature innovative low power techniques including SleepWalking peripherals, Arm TrustZone, immutable secure boot, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS60048

PIC32CM LS60 family of devices based on Arm® Cortex®-M23 processor bring hardened security, ultra-low power, superior touch, and smart analog integration in one package. They feature integrated Trust Platform ATECC608, Arm TrustZone, immutable secure boot, innovative low power techniques including SleepWalking peripherals, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS60064

PIC32CM LS60 family of devices based on Arm® Cortex®-M23 processor bring hardened security, ultra-low power, superior touch, and smart analog integration in one package. They feature integrated Trust Platform ATECC608, Arm TrustZone, immutable secure boot, innovative low power techniques including SleepWalking peripherals, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

PIC32CM5164LS60100

PIC32CM LS60 family of devices based on Arm® Cortex®-M23 processor bring hardened security, ultra-low power, superior touch, and smart analog integration in one package. They feature integrated Trust Platform ATECC608, Arm TrustZone, immutable secure boot, innovative low power techniques including SleepWalking peripherals, industry leading water tolerant touch, Op Amps, Analog to Digital Converter (ADC) & Digital to Analog Converter (DAC). They are supported by MPLABX IDE, MPLAB Harmony v3 and MPLAB Code Configurator (MCC).

Documentation:

Application Notes:

Additional Documents:

MISRA Compliance Deviations List

MISRA-C:2023

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).

MISRA-C:2025

Deviation ID: MFWCG-44

  • Rule 5.10: 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).

Deviation ID: None

  • Rule 11.4: A conversion shall not be performed between a pointer to object and an arithmetic type.
  • Use case: Setting special registers from linker-generated symbols.

Example:

C pSrc = (uint32_t *) & __svectors; SCB->VTOR = ((uint32_t) pSrc & SCB_VTOR_TBLOFF_Msk);

  • Reason: Access to hardware.

Some hardware registers do not have a pointer type but hold an address.

  • Scope: Device startup code (startup_<name>.c)

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 20.15: #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).

Support

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