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. PIC32CX-BZ3_DFP

PIC32CX-BZ3_DFP

1.4.259
Microchip

  • Pack Type

    Device Support

Microchip PIC32CX-BZ3 Series Device Support

Overview

The Microchip PIC32CX-BZ3 Series Device Family Pack (DFP) is a CMSIS-Pack that:

Related packs

    - pack: ARM::CMSIS

Devices

PIC32CX5109BZ31032

Part of the PIC32CX-BZ family, PIC32CX5109BZ31032 is a secure, low-cost 32-bit microcontroller with an inbuilt wireless subsystem certified for Bluetooth® and Zigbee®. Designed from the ground up to enable you to go to market quickly, PIC32CX5109BZ31032 is powered by a 64 MHz ARM® Cortex® M4F and is packed with features.---Ultra-low power 2.4 GHz transceiver: Build applications enabling Bluetooth Low-Energy (LE) 6.0, IEEE® 802.15.4 / Zigbee 3.0 connectivity with hardware-level arbitration for multi-protocol wireless functionality.Hardware-based security (secure boot): Protect applications with NIST-compliant authentication and secure boot ROM to ensure only trusted software runs on your system. Robust analog peripherals: Industrial-grade capacitive touch, ADCs, DAC and comparators enable versatile sensor integration and analog management for a wide range of applications.Functional safety: This device supports the ISO 26262 (ASIL B), and IEC 61508 (SIL 2) functional safety standards. The Functional Safety Manual, FMEDA and Diagnostic Software information are available under NDA. Contact us for more information.

Documentation:

Application Notes:

Additional Documents:

PIC32CX5109BZ31032_SL3

PIC32CX5109BZ31048

Part of the PIC32CX-BZ family, PIC32CX5109BZ31048 is a secure, low-cost 32-bit microcontroller with an inbuilt wireless subsystem certified for Bluetooth® and Zigbee®. Designed from the ground up to enable you to go to market quickly, PIC32CX5109BZ31048 is powered by a 64 MHz ARM® Cortex® M4F and is packed with features.---Ultra-low power 2.4 GHz transceiver: Build applications enabling Bluetooth Low-Energy (LE) 6.0, IEEE® 802.15.4 / Zigbee 3.0 connectivity with hardware-level arbitration for multi-protocol wireless functionality.Hardware-based security (secure boot): Protect applications with NIST-compliant authentication and secure boot ROM to ensure only trusted software runs on your system. Robust analog peripherals: Industrial-grade capacitive touch, ADCs, DAC and comparators enable versatile sensor integration and analog management for a wide range of applications.Functional safety: This device supports the ISO 26262 (ASIL B), and IEC 61508 (SIL 2) functional safety standards. The Functional Safety Manual, FMEDA and Diagnostic Software information are available under NDA. Contact us for more information.

Documentation:

Application Notes:

Additional Documents:

PIC32CX5109BZ31048_SL3

PIC32CX5109BZ36032

Part of the PIC32CX-BZ family, PIC32CX5109BZ36032 is a secure, low-cost 32-bit microcontroller with an inbuilt wireless subsystem certified for Bluetooth® and Zigbee®. Building on the foundation of the PIC32CX-BZ3, the PIC32CX-BZ36 introduces a new low-power operating mode to further reduce consumption and an enhanced secure boot process for added protection.Designed from the ground up to enable you to go to market quickly, PIC32CX5109BZ36032 is powered by a 64 MHz ARM® Cortex® M4F and is packed with features.---Ultra-low power 2.4 GHz transceiver: Build applications enabling Bluetooth Low-Energy (LE) 6.0, IEEE® 802.15.4 / Zigbee 3.0 connectivity with hardware-level arbitration for multi-protocol wireless functionality.Buck (DC-DC/switching) mode: Supports high power (PWM) and low power (PSM) mode, providing efficient power management for a wide range of operating conditions.Hardware-based security (secure boot): Protect applications with NIST-compliant authentication and secure boot ROM to ensure only trusted software runs on your system. Robust analog peripherals: Industrial-grade capacitive touch, ADCs, DAC and comparators enable versatile sensor integration and analog management for a wide range of applications.Functional safety: This device supports the ISO 26262 (ASIL B), and IEC 61508 (SIL 2) functional safety standards. The Functional Safety Manual, FMEDA and Diagnostic Software information are available under NDA. Contact us for more information.---Ultra-low power 2.4 GHz transceiver: Build applications enabling Bluetooth Low-Energy (LE) 6.0, IEEE® 802.15.4 / Zigbee 3.0 connectivity with hardware-level arbitration for multi-protocol wireless functionality.Buck (DC-DC/switching) mode: Supports high power (PWM) and low power (PSM) mode, providing efficient power management for a wide range of operating conditions.Hardware-based security (secure boot): Protect applications with NIST-compliant authentication and secure boot ROM to ensure only trusted software runs on your system. Robust analog peripherals: Industrial-grade capacitive touch, ADCs, DAC and comparators enable versatile sensor integration and analog management for a wide range of applications.Functional safety: This device supports the ISO 26262 (ASIL B), and IEC 61508 (SIL 2) functional safety standards. The Functional Safety Manual, FMEDA and Diagnostic Software information are available under NDA. Contact us for more information.

Documentation:

Application Notes:

Additional Documents:

PIC32CX5109BZ36032_SL3

PIC32CX5109BZ36048

Part of the PIC32CX-BZ family, PIC32CX5109BZ36048 is a secure, low-cost 32-bit microcontroller with an inbuilt wireless subsystem certified for Bluetooth® and Zigbee®. Building on the foundation of the PIC32CX-BZ3, the PIC32CX-BZ36 introduces a new low-power operating mode to further reduce consumption and an enhanced secure boot process for added protection.Designed from the ground up to enable you to go to market quickly, PIC32CX5109BZ36048 is powered by a 64 MHz ARM® Cortex® M4F and is packed with features.---Ultra-low power 2.4 GHz transceiver: Build applications enabling Bluetooth Low-Energy (LE) 6.0, IEEE® 802.15.4 / Zigbee 3.0 connectivity with hardware-level arbitration for multi-protocol wireless functionality.Buck (DC-DC/switching) mode: Supports high power (PWM) and low power (PSM) mode, providing efficient power management for a wide range of operating conditions.Hardware-based security (secure boot): Protect applications with NIST-compliant authentication and secure boot ROM to ensure only trusted software runs on your system. Robust analog peripherals: Industrial-grade capacitive touch, ADCs, DAC and comparators enable versatile sensor integration and analog management for a wide range of applications.Functional safety: This device supports the ISO 26262 (ASIL B), and IEC 61508 (SIL 2) functional safety standards. The Functional Safety Manual, FMEDA and Diagnostic Software information are available under NDA. Contact us for more information.

Documentation:

Application Notes:

Additional Documents:

PIC32CX5109BZ36048_SL3

PIC32WM_BZ3601

PIC32WM_BZ3601_SL3

PIC32WM_BZ3602

PIC32WM_BZ3602_SL3

WBZ350

WBZ350_SL3

WBZ351

WBZ351_SL3

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

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 #define WDTCON WDTCON extern volatile uint32_t WDTCON attribute((section("sfrs"), address(0xBF800000)));

#if defined(WDTCON) // Code that accesses WDTCON register #endif ```

  • 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: All device headers (<device-name>.h).

Deviation ID: MFWCG-41

  • Rule 5.8: Identifiers that define objects or functions with external linkage shall be unique.
  • Use case: Unions of bitfield structures that represent the implemented and semantic bits of the register.

Example:

C extern volatile uint32_t SYSKEY __attribute__((section("sfrs"), address(0xBF800030))); typedef struct { uint32_t SYSKEY:32; } __SYSKEYbits_t;

  • Reason: Access to hardware.

The names assigned are the same as those in the device data sheet. These are in direct correspondence to simplify code comprehension.

  • Scope: All device headers (<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 #if defined(__PIC32_HAS_MICROMIPS) // Conditional code for micromips #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 _ICDSTAT _ICDSTAT

  • 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 volatile uint32_t _ICDSTAT __attribute__((section("sfrs"), address(0xBF801010)));

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