PIC32CM GC00 Curiosity Pro

Overview

The PIC32CM GC00 Curiosity Pro evaluation kit is a hardware platform to evaluate the Microchip PIC32CM GC microcontrollers, and the evaluation kit part number is EV17V75A. This kit provides a comprehensive set of features that allow users to explore the PIC32CM GC peripherals and gain insight into integrating the device into their own designs.

Hardware

100-pin TQFP PIC32CM5112GC00100 microcontroller
Arm® Cortex®-M23 core running at up to 72 MHz
512 KiB flash memory and 128 KiB of RAM
Up to 80 I/O lines with external interrupt capability
12 MHz crystal oscillator
32.768 kHz crystal oscillator
Two user LEDs (Red and Green)
One green board power LED
Two mechanical user push buttons, one touch button and one reset button
10 kOhms thumb wheel potentiometer on PB06
3.3V high-precision voltage reference (MCP1501)
TA101 CryptoAuthentication footprint, unpopulated on the shipping board
Micro USB interface (Type-AB) wired to the microcontroller
Programming and debugging through Serial Wire Debug (SWD), from the on-board PKoB4 debugger or from the Cortex® 10-pin debug header
Virtual COM port (VCOM) provided by the PKoB4
Two Xplained Pro extension headers, EXT1 (J400) and EXT2 (J401)
One extension power header
One mikroBUS™ socket
One Arduino UNO R3 compatible shield interface
Two CAN interfaces with ATA6561 transceivers
USERLDO header and RTC header

Supported Features

The pic32cm_gc00_cpro board supports the hardware features listed below.

on-chip / on-board: Feature integrated in the SoC / present on the board.
2 / 2: Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo: Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.

`pic32cm_gc00_cpro/pic32cm5112gc00100` target

On-target memory for this board target: 128 KiB of RAM, 66048 KiB of Flash.

Type	Location	Description	Compatible
CPU	on-chip	ARM Cortex-M23 CPU1	`arm,cortex-m23`
ARM architecture	on-chip	Microchip SERCOM module3	`microchip,sercom-g1`
Clock control	on-chip	Microchip PIC32CM_SG_GC SOC family clock1	`microchip,pic32cm-sg-gc-clock`
	on-chip	PIC32CM_SG_GC Crystal Oscillator (XOSC)1	`microchip,pic32cm-sg-gc-xosc`
	on-chip	PIC32CM_SG_GC Internal Oscillator (OSC48M)1	`microchip,pic32cm-sg-gc-dfll48m`
	on-chip	PIC32CM_SG_GC DPLL clock1	`microchip,pic32cm-sg-gc-dpll`
	on-chip	PIC32CM_SG_GC RTC clock1	`microchip,pic32cm-sg-gc-rtc`
	on-chip	PIC32CM_SG_GC External Crystal Oscillator (XOSC32K)1	`microchip,pic32cm-sg-gc-xosc32k`
	on-chip	PIC32CM_SG_GC Generic clock generator1	`microchip,pic32cm-sg-gc-gclkgen`
	on-chip	PIC32CM_SG_GC Generic clock peripheral1	`microchip,pic32cm-sg-gc-gclkperiph`
	on-chip	PIC32CM_SG_GC Main clock domains1	`microchip,pic32cm-sg-gc-mclkdomain`
	on-chip	PIC32CM_SG_GC MCLK peripheral1	`microchip,pic32cm-sg-gc-mclkperiph`
DMA	on-chip	Microchip G2 DMA Controller1	`microchip,dmac-g2-dma`
Flash controller	on-chip	Microchip flash controller1	`microchip,nvmctrl-g3`
GPIO & Headers	on-chip	Microchip Port G1 GPIO3 1	`microchip,port-g1-gpio`
Hardware information	on-chip	Microchip G1 hwinfo driver1	`microchip,hwinfo-g1`
I2C	on-chip	Microchip SERCOM G1 I2C driver1	`microchip,sercom-g1-i2c`
Input	on-board	Group of GPIO-bound input keys1	`gpio-keys`
Interrupt controller	on-chip	ARMv8-M NVIC (Nested Vectored Interrupt Controller)1	`arm,v8m-nvic`
LED	on-board	Group of GPIO-controlled LEDs1	`gpio-leds`
MMU / MPU	on-chip	ARMv8-M MPU (Memory Protection Unit)1	`arm,armv8m-mpu`
MTD	on-chip	Microchip NVMCTRL G3 Flash1	`microchip,flash-g3`
Pin control	on-chip	Microchip PORT Pinctrl container node1	`microchip,port-g1-pinctrl`
Reset controller	on-chip	Microchip RSTC Reset driver1	`microchip,rstc-g1-reset`
Serial controller	on-chip	Microchip SERCOM UART controller1	`microchip,sercom-g1-uart`
SPI	on-chip	Microchip SERCOM SPI1	`microchip,sercom-g1-spi`
SRAM	on-chip	Generic on-chip SRAM1	`mmio-sram`
Timer	on-chip	ARMv8-M System Tick1	`arm,armv8m-systick`
Watchdog	on-chip	Microchip Watchdog g1 driver1	`microchip,wdt-g1`

Limitations

No entropy source. The die carries no hardware random number generator, so CONFIG_ENTROPY_GENERATOR has nothing to bind to on this board. Anything needing random numbers has to bring its own source.
Flash erase stalls execution from flash. The flash controller has a single panel (PFM_NUM_PANELS is 1), so there is no read-while-write: code and interrupt handlers executing from flash cannot be fetched until an erase completes. The data sheet gives 20 ms as the maximum page erase time (TFEP). Erasing from a path with a shorter deadline - including a settings write that triggers a garbage collection - can miss it.

Connections and IOs

The PIC32CM SG00/GC00 Curiosity Pro User Guide has detailed information about board connections.

Warning

PC07 is SWDIO and PC08 is SWCLK. Configuring either as a GPIO clears PINCFG.PMUXEN and takes the debug interface away from the running system, which leaves the board unable to accept another programming session until it is erased through an external probe holding the target in reset.

Programming & Debugging

The pic32cm_gc00_cpro board supports the runners and associated west commands listed below.

	flash	debug	rtt	debugserver	attach	reset
jlink	✅	✅ (default)	✅	✅	✅	✅
mplab_ipe	✅ (default)

Flash Using MPLAB IPE

For instructions on flashing using MPLAB IPE see Flashing with Microchip MPLAB IPE.

Flash Using J-Link

To flash the board using the J-Link debugger, follow the steps below:

Install J-Link Software
- Download and install the J-Link software tools from Segger.
- Make sure the installed J-Link executables (e.g., JLink, JLinkGDBServer) are available in your system’s PATH.
Connect the Board
- Connect the J32 Debug Probe to the board’s CORTEX DEBUG header.
- Connect the other end of the J32 Debug Probe to your host machine (PC) via USB.
- Connect the DEBUG USB port on the board to your host machine to power up the board.
Build the Application

You can build a sample Zephyr application, such as Blinky, using the west tool. Run the following commands from your Zephyr workspace:
```
west build -b pic32cm_gc00_cpro -p -s samples/basic/blinky
```
This will build the Blinky application for the pic32cm_gc00_cpro board.
Flash the Device

Once the build completes, flash the firmware using:
```
west flash
```
This uses the default jlink runner to flash the application to the board.
Observe the Result

After flashing, LED0 on the board should start blinking, indicating that the application is running successfully.

Debug Using J-Link: GDB Command-Line

To debug the board using the J-Link debugger, follow the steps below:

Build the Application

You can build a sample Zephyr application, such as Blinky, using the west tool. Run the following commands from your Zephyr workspace:
```
west build -b pic32cm_gc00_cpro -p -s samples/basic/blinky
```
This will build the Blinky application for the pic32cm_gc00_cpro board.

Debug the Application

To debug the application, run the following command from your Zephyr workspace:

west debug

Note

Debugging with J-Link GDB Server: Halting at `main` and Setting Breakpoints

(gdb) break main
(gdb) break main.c:42         # Optional: set breakpoint at line 42 in main.c
(gdb) continue                # Start execution, halts at first breakpoint
(gdb) info breakpoints        # List all breakpoints
(gdb) delete 1                # Delete breakpoint number 1
(gdb) delete                  # Delete all breakpoints
(gdb) clear main.c:42         # Clear breakpoint at specific location
(gdb) continue                # Resume execution

Debug Using J-Link: VSCode

To debug using VSCode, create or edit the .vscode/launch.json file in your project directory with the following configuration:

{
   "version": "0.2.0",
   "configurations": [
      {
            "name": "Debug (J-Link, PIC32CM5112GC00100)",
            "type": "cortex-debug",
            "request": "launch",
            "servertype": "jlink",
            "device": "PIC32CM5112GC00100",
            "interface": "swd",
            "runToEntryPoint": "main",
            "showDevDebugOutput": "none",
            "cwd": "${workspaceFolder}",
            "executable": "${workspaceFolder}/zephyr/build/zephyr/zephyr.elf",

            //J-Link settings
            "serverpath": "C:/Program Files/SEGGER/JLink_Vxxx/JLinkGDBServerCL.exe",
            "serverArgs": [
               "-singlerun",
               "-if", "swd",
               "-speed", "4000",
               "-device", "PIC32CM5112GC",
               "-port", "50000"
            ],

            //Zephyr SDK toolchain paths
            "gdbPath": "***/zephyr-sdk-x.xx.x/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb.exe",
            "objdumpPath": "***/zephyr-sdk-x.xx.x/arm-zephyr-eabi/bin/arm-zephyr-eabi-objdump.exe",
      }
   ]
}