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. PIC32CK-GC_DFP

PIC32CK-GC_DFP

1.3.221
Microchip

  • Pack Type

    Device Support

Microchip PIC32CK-GC Series Device Support

Overview

The Microchip PIC32CK-GC Series Device Family Pack (DFP) is a CMSIS-Pack that:

Related packs

    - pack: ARM::CMSIS

Devices

PIC32CK0512GC00064

PIC32CK0512GC00100

PIC32CK0512GC01064

PIC32CK0512GC01100

PIC32CK1012GC00048

PIC32CK1012GC00064

PIC32CK1012GC00100

PIC32CK1012GC01048

PIC32CK1012GC01064

PIC32CK1012GC01100

PIC32CK1025GC00064

PIC32CK1025GC00100

PIC32CK1025GC01064

Arm® Cortex®-M33 Based 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

Documentation:

Application Notes:

Additional Documents:

PIC32CK1025GC01100

Arm® Cortex®-M33 Based 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

Documentation:

Application Notes:

Additional Documents:

PIC32CK1025GC01144

Arm® Cortex®-M33 Based 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

Documentation:

Application Notes:

Additional Documents:

PIC32CK2051GC00064

PIC32CK2051GC00100

PIC32CK2051GC00144

PIC32CK2051GC01064

Arm® Cortex®-M33 Based 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

Documentation:

Application Notes:

Additional Documents:

PIC32CK2051GC01100

Arm® Cortex®-M33 Based 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

Documentation:

Application Notes:

Additional Documents:

PIC32CK2051GC01144

Arm® Cortex®-M33 120 MHz MCUs with Connectivity PeripheralsThe PIC32CK SG/GC family of microcontrollers (MCUs) is based on Arm® Cortex®-M33 technology. The M33 is optimized for power-sensitive microcontroller and mixed-signal applications. It improves performance over the previous generation, real-time determinism, energy efficiency, software productivity, and system security. The PIC32CK SG/GC family offers a large memory capacity with 2 MB of Dual Panel Flash and 512 KB of SRAM.The SG variants are intended for highly secure connectivity and applications needing the most secure key management and cryptographic operations. The SG family combines an on-chip, fully isolated Hardware Security Module (HSM) with Arm TrustZone® technology. The GC variants are intended for general-purpose mixed-signal applications that do not need the HSM and advanced security features.The PIC32CK SG/GC devices have connectivity options including standard serial communications (UART, USART, SPI, I2C, etc.,) I2S, USB, CAN FD, and 10/100 Ethernet. Advanced analog includes a 12-bit 3 Msps ADC and Peripheral Touch Controller.The PIC32CK SG/GC is fully supported by MPLAB X IDE and MPLAB® Harmony Integrated Design Environment. CAN FD and 10/100 Ethernet IEEE1588. These MCUs are available in 144-pin and 100-pin, 64-pin package options.

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.