Arm® CMSIS Solution - Running the Driver Example, Basic Debugging and Serial Monitor

Practical demonstration of loading and running the CMSIS Driver Example for the PIC32CM PL10 Curiosity Nano board in VS Code. We explore the code (GPIO UART driver usage, switch-triggered message), perform basic debugging with breakpoints, use the built-in CMSIS Serial Monitor to observe UART output, and show how to easily change the baud rate via config file (with live sync to code) — all within the CMSIS Solution environment. Engineer-focused: clean workflow, no fluff, highlighting code completion, config-driven changes, and simple debug/monitor integration. 00:00 – Recap: Blinky from previous video + Data Visualizer verification 00:33 – Closing Blinky → loading the Driver Example 00:49 – Browse folder, select project, Git init option 01:02 – Environment setup during solution creation 01:13 – README preview: GPIO + UART demo, LED toggle, switch monitor, UART message 01:33 – System clock 24 MHz, SysTick 1 ms ticks 01:45 – Code dive: UART driver instance pointer → API code completion 02:02 – Build → start debug session 02:26 – Set breakpoint at UART send 02:34 – Debug run → hit main start 02:48 – Resume → press button to hit breakpoint 02:59 – CMSIS Debugger extensions: Serial Monitor in new terminal 03:17 – Open Serial Monitor → auto-detects Curiosity Nano virtual COM 03:28 – Start monitoring → button presses send responsive "Switch pressed" messages 03:41 – Default baud rate 115200 confirmed 03:47 – Changing baud rate: UART config overview (async, no parity, 8N1) 03:59 – Edit config.uart → change to 9600 04:13 – Save → code syncs to 9600 04:22 – Rebuild & run (no debug needed) 04:35 – Serial Monitor at 9600 → messages still visible (after host-side match) 04:49 – Revert to 115200 directly in code → rebuild & run 05:11 – Back to normal output 05:18 – Summary: Basic debugging + serial in CMSIS flow