Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/analogdevicesinc/codefusion-studio/llms.txt

Use this file to discover all available pages before exploring further.

CodeFusion Studio follows a semantic versioning scheme and ships updates through the Visual Studio Code Marketplace as well as standalone installers. Each entry below covers the key changes introduced in that release, including new features, platform expansions, bug fixes, and known issues at the time of publication. Releases are listed from most recent to oldest. Source tags for every release are available on the CodeFusion Studio GitHub repository.

Version 2.2.0 — May 25, 2026

Source tag: V2.2.0CodeFusion Studio 2.2.0 builds on the foundation established in previous releases, focusing on two key areas: expanded platform support and AI workflow enhancements.

AI Workflow Enhancements

  • cfsutil ai command group — The cfsai standalone tool has been migrated into cfsutil as the cfsutil ai command group, enabling a complete CLI-first AI model workflow:
    • cfsutil ai build — compile a model into deployable C/C++ source code.
    • cfsutil ai compat — check model compatibility with a target SoC and core.
    • cfsutil ai profile — profile model resource usage before deployment.
    • cfsutil ai model (new) — add, list, update, and remove AI models within a workspace without manually editing .cfsconfig files.
    • cfsutil ai workspace create (new) — generate a workspace directly from an AI model file with automatic compatibility checking and initial build.
    • cfsutil ai backends — list available AI backends and extension fields.
    • cfsai remains available as a compatibility wrapper for existing scripts.
  • Workspace from AI Model wizard — Create AI-ready workspaces directly from a model file. The new wizard guides you through model file selection, SoC/board selection, and per-core targeting. Generated workspaces include pre-configured AI applications with model integration and sample data handling.
  • AI Hardware Profiling view — Provides guided deployment to hardware with build status tracking and one-click model deployment.
  • Embedded AI Tools UX improvements — Redesigned Compatibility and Resource Profiling report outputs for easier visualization. A new Open Report option is available on the CFS Home page.
  • AI Debug Assistant — General bug fixes and stability improvements. The MCP server is recommended for production workflows.
  • Profiling — Zephelin trace capture — A new Trace Capture panel streamlines workflow with one-click start/stop. Enhanced Profiling Configuration in System Planner shows cores individually. Trace capture automatically generates both .ctf and .tef output files. The Zephelin Trace Viewer extension is now auto-installed as a CFS dependency. New profiling options include CPU Load, Memory Usage sampling, and Application Callgraph.
Deprecated flag: --json — The --json flag is deprecated across all cfsutil ai, cfsutil elf, and cfsutil socs commands. Use --format json (or --format text) instead. The --json flag continues to work but displays a deprecation warning and will be removed in a future release.

Expanded Platform Support

  • CLI-first workspace workflows — Full end-to-end workspace, build, and flash workflows are now possible entirely from the command line without opening the IDE: cfsutil socs listcfsutil socs infocfsutil workspace configurecfsutil workspace createcfsutil tasks list / cfsutil tasks run.
  • Memory Viewer — A new debug tool providing native multicore-aware memory inspection. Displays memory in a scrollable hex/ASCII grid with configurable byte grouping (1, 2, or 4 bytes), column count (4–64), endianness, and display format. Auto-refreshes on debugger halt; supports retrospective core dump sessions in read-only mode.
  • Core Dump Analysis — expanded SoC support — Added support for nine additional MAX devices: MAX32650, MAX32655, MAX32660, MAX32662, MAX32666, MAX32670, MAX32672, MAX78000, and MAX78002. Core dump analysis now supports a total of 12 SoCs.
  • System Planner improvements — Enhanced Pin Config search with categorized results and navigation. Automated version resolution when opening .cfsconfig files with missing data models. Full System Planner support (Memory Allocation, Peripheral Allocation, Pin Config, and Registers) added for MAX32660, MAX32662, MAX32666, MAX32672, and MAX32675C.
  • Zephyr 4.3.0 support — Added across all supported MAX32xxx and MAX78xxx microcontrollers.
  • New workspace templates:
    • MSDK: Library generation, Library usage, Watchdog
    • Zephyr: Basic threading, Button handling, POSIX philosophers, UART echo
    • Board support expanded for existing MSDK templates (DMA, Hello World C++, I2C scan, RTC, UART Loopback) to MAX78000; Zephyr templates (ADC sequence, I2C custom target, LittleFS, Watchdog) to MAX32666 and MAX78000.
  • Package Manager — License acceptance prompt for packages requiring agreement (interactive in Command Palette; y/n prompt in CLI; --acceptLicense flag for automated/CI workflows). New (CFS) Delete Package from Cache command to remove cached but uninstalled packages.
  • cfsutil socs list format change — The previous {name}-{package} format has been replaced with explicit SoC name and package fields. socs export now takes the SoC name as a positional argument with a separate -p, --package flag.
Breaking change — socs list output format: The default text and JSON output of cfsutil socs list and the usage of cfsutil socs export have changed. Use the --legacy flag on socs list or the deprecated -n, --name flag on socs export while migrating existing scripts. Both flags will be removed in a future release.

Software Component Versions

ComponentVersionNotes
Bare-metal ARM toolchain14.3.Rel1GCC toolchain for 32-bit Arm® targets
Bare-metal RISC-V toolchain14.2.0GCC toolchain for RISC-V targets
MSDK2.2.0Part support and examples for MAX32xxx and MAX78xxx
SHARC-FX SDK3.0.3SDK for the Cortex-M33 core on SHARC-FX targets
Zephyr RTOS4.3.0Real-time OS for MAX32xxx and MAX78xxx
Zephyr SDK0.17.4GCC-based toolchain for Arm® development with Zephyr

Host Architecture Support

  • Windows 11 (64-bit)
  • macOS 15 and macOS 26 (ARM64)
  • Ubuntu 22.04 and 24.04 (64-bit)

Known Issues

  • MSDK Project Plugin incorrectly appears for MAX32657 — Do not select the MSDK Project Plugin in the Code Generation Plugin step for MAX32657; this processor does not support MSDK.
  • TrustZone manual configuration removed for MAX32657/MAX32658 — Use the TF-M Secure Partition template instead of manual TrustZone configuration for these devices.
  • Package version conflict with cfs_zephyr_max32657_plugins/1.1.0 — Install cfs_base_plugins/2.1.0 or cfs_base_plugins/2.0.1 before installing cfs_zephyr_max32657_plugins/1.1.0.
  • Build error when workspace is in OneDrive or path with spaces — Move the workspace to a local directory path without spaces.
  • cfsutil project create fails for template-based workspaces — Use the Manually configure the workspace option or cfsutil workspace configure followed by cfsutil workspace create -i instead.
  • Profiling may fail with memory overflow — Enabling multiple Zephelin profiling options can cause linker errors; disable some options to reduce memory usage.
  • J-Link Software V8.94 required for MAX32657/MAX32658 — Custom J-Link support files have been removed from the installer; official support is provided by Segger in V8.94 and later.
  • erase_JLink task may require cfs.jlink.path configuration — Set cfs.jlink.path in settings if the task fails with JLinkExe: No such file or directory.
  • J-Link flash erase may not clear full flash on MAX32657 — Use the Erase (OpenOCD) task instead.
  • Debugging Zephyr projects with J-Link may not halt at main — Update to Cortex-Debug v1.12.1 and J-Link V9.36 or later.
Source tag: V2.1.0CodeFusion Studio 2.1.0 introduces a preview of the AI Debug Assistant — an agentic AI system that actively participates in debug sessions — along with Package Manager improvements, workspace creation enhancements, and expanded SHARC-FX support.

AI Debug Assistant (Preview)

The AI Debug Assistant is an agentic debugging tool built on the Model Context Protocol (MCP) that connects compatible AI clients (such as GitHub Copilot and Claude Code) directly to live debug sessions. The assistant can:
  • Autonomously investigate hard faults: read fault registers, decode exception types, walk the call stack, and identify root causes.
  • Inspect live hardware state including registers, memory, variables, stack traces, and thread lists directly from the target.
  • Set and manage breakpoints and hardware watchpoints, including conditional breakpoints.
  • Execute GDB commands with built-in safety guards.
  • Coordinate multi-core debug sessions to surface shared-memory race conditions and DMA conflicts.
  • Follow pre-built diagnostic workflows for crash diagnosis, memory corruption, peripheral misconfiguration, and firmware size analysis.

Package Manager Improvements

  • Authentication — Authentication is now managed via cfsutil myanalog (login, logout, status) and cfsutil pkg auth-remote. The commands cfsutil pkg login, cfsutil pkg logout, and cfsutil auth are deprecated and display warnings.
  • Semantic version rangescfsutil pkg install now supports version range operators: caret (^), tilde (~), and comparison operators (>=, <=, >, <). CFS installs the newest version satisfying the constraint.
  • --local flag — Install packages from the local cache only (offline mode).
  • cfsutil pkg list-remotes — Now displays authentication status including inactive sessions.
  • Fixed an issue where adding a package remote could be accidentally cancelled by clicking outside the prompt.

Workspace Creation Improvements

  • Plugin options are now filtered by core type during manual workspace creation (e.g., selecting a RISC-V core hides unsupported options like Zephyr).
  • Cores in the workspace creation wizard are ordered with the primary core listed first.

Development Platforms and Tools

  • Support for Zephyr RTOS 4.2.
  • SHARC-FX support — Build and debug support for the ADSP-2183x/SC83x family on Windows. ADI ICE drivers are required (selectable during installation or installable later). Requires the Xtensa SHARC-FX toolchain from the Package Manager. For multicore devices such as the ADSP-SC835W, start debugging on the SHARC-FX core first, then attach to the Cortex-M33 core. System Planner provides Pin Mux configuration only for SHARC-FX devices in this release.
  • Registers-only (bare-metal) — A reference plugin that generates low-level MMR initialization code for use in custom toolchains, available for MAX32xxx and MAX78xxx devices.

Software Component Versions

ComponentVersionNotes
Bare-metal ARM toolchain14.3.Rel1GCC toolchain for 32-bit Arm® targets
Bare-metal RISC-V toolchain14.2.0GCC toolchain for RISC-V targets
MSDK2.1.0Part support and examples for MAX32xxx and MAX78xxx
SHARC-FX SDK3.0.3SDK for the Cortex-M33 core on SHARC-FX targets
Zephyr RTOS4.2.0Real-time OS for MAX32xxx and MAX78xxx
Zephyr SDK0.17.4GCC-based toolchain for Arm® development with Zephyr

Known Issues

  • AI Debug Assistant (preview)clear all breakpoints returns help text instead of acting; x/16xw <address> returns help text instead of examining memory. Use a Claude model (e.g., Claude Sonnet 4.5) for best results.
  • Analyze Threads GDB Toolbox — Requires an OpenOCD debug configuration; fails with J-Link because JLinkGDBServer does not support Zephyr thread awareness.
  • See 2.0.1 known issues for additional issues.
Source tag: V2.0.2CodeFusion Studio 2.0.2 is a patch release that fixes a regression affecting CFS telemetry. In version 2.0.1, telemetry events — including workspace creation events and extension activation events — were not collected due to this regression.
CFS 2.0.2 is distributed only through the Visual Studio Code Marketplace. A standalone installer is not provided for this release, and manual installation using a VSIX file is not supported. If extension auto-updates are enabled, no action is required.

Bug Fixes

  • Fixed an issue where CFS telemetry events were not correctly emitted in version 2.0.1.
  • Updated release notes and CHANGELOG.md.

Known Issues

See 2.0.1 known issues for all applicable issues.
Source tag: V2.0.1CodeFusion Studio 2.0.1 delivers stability improvements, bug fixes, and an expanded set of workspace templates. This release adds support for the MAX32658 SoC and introduces Zephyr 4.3.0 support for MAX32657 and MAX32658.

New Workspace Templates

16 new MSDK and Zephyr workspace templates were added, expanding support for multicore development, AI workloads, and peripheral examples.MSDK templates added:
  • Single Core DMA, Single Core Hello World (C++), Single Core I2C Scan, Single Core ICC, Single Core RTC, Single Core UART Loopback, Dual Core Sync (ARM + RISC-V)
Zephyr templates added:
  • ADC Sequence, Basic Synchronization, Counter Alarm, C++ Synchronization, Dining Philosophers, Hello World (C++), I2C Custom Target, LittleFS, Watchdog

Expanded SoC and RTOS Support

  • MAX32658 — Full support added, including System Planner configuration, Zephyr development, and debug support.
  • Zephyr 4.3.0 — Added for MAX32657 and MAX32658 (MAX32657 also continues to support Zephyr 4.2.0). Install via cfsutil pkg install zephyr/4.3.0-b.1.

Bug Fixes

General stability and performance improvements across project setup, AI Tools, System Planner, and Package Manager workflows. Includes improved Package Manager error handling, System Planner UI fixes, and platform compatibility enhancements.

Software Component Versions

ComponentVersionNotes
Bare-metal ARM toolchain14.3.Rel1GCC toolchain for 32-bit Arm® targets
Bare-metal RISC-V toolchain14.2.0GCC toolchain for RISC-V targets
MSDK2.0.1Part support and examples for MAX32xxx and MAX78xxx
SHARC-FX SDK3.0.3SDK for the Cortex-M33 core on SHARC-FX targets
Zephyr RTOS4.2.0Real-time OS for MAX32xxx and MAX78xxx
Zephyr SDK0.17.4GCC-based toolchain for Arm® development with Zephyr

Known Issues

  • MSDK Single Core UART Loopback (AD-APARD32690-SL) — Results in Example failed due to UART0 TX conflict; resolved in the next release.
  • TrustZone workspace creation — Manually creating and enabling TrustZone can lead to build errors in the Non-Secure partition. Use the TF-M Secure Partition template instead.
  • TF-M template debugging (MAX32657/MAX32658) — Only debug configurations matching the project’s security build setting are supported. Switching between Secure and Non-Secure flows requires rebuilding.
  • Compatibility Analyzer/Resource Profiling — Clicking Open Compatibility Report or Open Profiling Report from an unedited System Planner session can cause System Planner to close unexpectedly.
  • Analyze Threads GDB Toolbox — Not supported on MAX32657/MAX32658.
  • Zephelin profiler — Not supported on Zephyr 4.3.0 in this release.
  • OpenOCD macOS No J-Link device found — Occurs on macOS when only the on-board J-Link (J-Link OB-MAX32690-ADI) is attached without an external probe.
  • Multiple J-Link devices detected — Disconnect unused probes or use the adapter serial (OpenOCD) or serialNumber (Cortex-Debug) settings in launch.json to target a specific probe.
  • J-Link v11 with OpenOCD LIBUSB_ERROR_NOT_SUPPORTED — Install Segger J-Link version 12.1 or later to resolve.
  • See 2.0.0 known issues for additional issues.
Source tag: V2.0.0CodeFusion Studio 2.0.0 is a major release introducing AI development tools, new debugging capabilities, a Package Manager for on-demand SDK and toolchain installation, and significant System Planner enhancements.

AI Tools

  • Embedded AI Tools — Available in System Planner for supported processors (MAX32657, MAX32690, MAX78002, and the ADSP-2183x/SC83x SHARC-FX family). Import model files, assign to cores, configure settings, run compatibility and profiling checks, and generate deployment source code.
  • CFSAI Command-Line Utility — Terminal-based access to the same AI capabilities: compile models, run compatibility and profiling reports, and integrate into automated workflows.
  • AI-enabled SoC support — MAX32657, MAX32690, MAX78002, and ADSP-2183x/SC83x SHARC-FX family.

Debugging Tools

  • Core Dump Analysis Tool — A dedicated debug panel for analyzing core dumps captured during system crashes.
  • GDB Toolbox — Run default or custom JSON-based GDB scripts to inspect program state and automate debugging during halted sessions.

Installation and Setup

  • Package Manager — Download SDKs, toolchains, and plugins on demand from a remote server. Simplifies initial setup and keeps your environment current without requiring a full reinstallation.
  • Telemetry — Opt-in dialog on first launch that collects anonymous diagnostics and usage data.

System Planner Enhancements

  • Memory Allocation — Interactive memory bar for creating or editing partitions directly from the visual layout.
  • Peripheral Allocation — Improved setup flow from peripheral allocation through pin assignment to final configuration, with visual cues throughout.
  • Profiling — Zephelin profiling support in Zephyr projects for runtime and AI inference-level performance capture, with CTF trace export for the Zephelin Trace Viewer.
  • New peripheral configuration support — Inter-IC Sound Interface (I2S), One-Wire (OWM), True Random Number Generator (TRNG), in addition to ADC, I2C, RTC, SPI, Timers, UART, and WDT.

Workspace Creation Wizard

  • Guided sidebar shows progress at every step.
  • Template selection is now built into the wizard alongside the manual configuration option.
  • TrustZone support for MAX32657 — via the TF-M Secure Partition template or manual configuration.

Development Platforms and Tools

  • Support for Zephyr RTOS 4.2 and the MSDK.
  • SHARC-FX (ADSP-2183x/SC83x) — Build and debug support on Windows; ADI ICE drivers required; Pin Mux configuration only in System Planner.
  • Registers-only (bare-metal) reference plugin for advanced custom toolchain workflows.

Software Component Versions

ComponentVersionNotes
Bare-metal ARM toolchain14.3.Rel1GCC toolchain for 32-bit Arm® targets
Bare-metal RISC-V toolchain14.2.0GCC toolchain for RISC-V targets
MSDK2.0.0Part support and examples for MAX32xxx and MAX78xxx
SHARC-FX SDK3.0.3SDK for the Cortex-M33 core on SHARC-FX targets
Zephyr RTOS4.2.0Real-time OS for MAX32xxx and MAX78xxx
Zephyr SDK0.17.4GCC-based toolchain for Arm® development with Zephyr

Host Architecture Support

  • Windows 11 (64-bit)
  • macOS 15 and macOS 26 (ARM64)
  • Ubuntu 22.04 and 24.04 (64-bit)

Known Issues

  • SHARC-FX templates — Windows only — Workspace templates for ADSP-2183x/SC83x are not supported on macOS or Linux in this release.
  • Zephyr plugin rename — Legacy .cfsconfig files referencing com.analog.project.zephyr41.plugin must be updated to com.analog.project.zephyr.plugin.
  • Windows installer symlink failure — Ensure Developer Mode is enabled before running the installer if you encounter Installer Error: Error during installation process.
  • Uninstall does not remove package data — Manually remove locally installed packages before reinstalling. See the Uninstall documentation for details.
  • Visual C++ Redistributable required on Windows — AI Tools require the Visual C++ Redistributable for Visual Studio 2015.
  • Spaces in AI tool file paths — Compatibility Checking and Profiling Report utilities do not support paths with spaces.
  • Prepare CTF trace not supported on Windows (outside WSL2) — Run from a WSL2 environment on Windows to prepare and visualize CTF traces.
  • GDB binary not Python-enabled on macOS — Install Python 3.10 via Homebrew and point gdbPath to arm-none-eabi-gdb-py in launch.json to enable GDB Toolbox Python scripts.
  • RISC-V restart fails with OpenOCD protocol error — Clicking Restart during a RISC-V debug session produces Protocol error with Rcmd: FC; this is expected behavior due to JTAG port re-enabling requirements.
Source tag: V1.1.0CodeFusion Studio 1.1.0 is a major feature release focused on multi-core development, introducing the System Planner, heterogeneous multi-core debugging, resource partitioning tools, and a plugin-based project architecture.

New Tools and Features

  • System Planner — A new centralized interface for accessing configuration tools and managing workspace resources across cores, peripherals, clocks, pins, and memory partitions.
  • Memory Allocation — Define and manage memory partitions per core to optimize resource distribution across multi-core SoCs.
  • Peripheral Allocation — Assign and configure peripheral blocks per core directly within the System Planner.
  • Heterogeneous Multi-Core Debugging — Debug multiple cores in a single IDE environment without requiring multiple instances.
  • Device Tree View — Hardware component review for Zephyr-based projects, improving visibility and configuration management.
  • Multi-Core Workspaces — Projects are upgraded to workspaces with one project per core, providing better organization and streamlined management across cores.
  • Catalog Manager — A background service that automatically syncs the SoC data model, ensuring up-to-date information on cores, boards, and hardware configurations.
  • Plugin-based project creation — A flexible, extensible plugin architecture separating configuration from code generation, allowing developers to create plugins aligned with internal standards.
  • UX upgrades — Improved accessibility and usability for the Registers and Pin Config pages.
  • Context menu enhancements — Clicking on a project in the Context panel dynamically updates the Actions panel to show only relevant actions.
  • Registers-only (bare-metal) — Reference plugin for advanced workflows generating MMR-based code for custom toolchains.

Development Platforms and Tools

  • Support for Zephyr RTOS 4.1 and the MSDK.
  • Compiler and debug support for Zephyr (ARM Cortex-M only) and MSDK (ARM Cortex-M and RISC-V).

Software Component Versions

ComponentVersion
Arm GNU Toolchain14.2.Rel1
xPack GNU RISC-V Toolchain14.2.0-3
Zephyr RTOS4.1.0
Zephyr SDK0.17.0

New Processor Support

ProcessorMSDKZephyrConfig ToolsTESA
MAX32650YesYesNoYes
MAX32660YesYesNoNo
MAX32666NoYesNoNo
MAX32675CYesYesNoNo

Host Architecture Support

  • Windows 10 or 11 (64-bit)
  • macOS (ARM64)
  • Ubuntu 22.04 and later (64-bit)

Known Issues

  • VS Code 1.99 incompatibility — CFS is not compatible with VS Code 1.99. VS Code 1.98 is known to be compatible.
  • Zephyr supported for single-core configurations only — Do not allocate Zephyr to a RISC-V core; use Zephyr only on ARM Cortex-M cores in standalone configurations.
  • Build failure with conflicting timer modes — Zephyr projects using multiple TMR peripherals in different modes fail with multiple definition of 'Wrap_MXC_TMR_*'; prefix affected functions with static inline in wrap_max32_tmr.h.
  • MSDK Board_Init() interference — Override the SDK’s Board_Init() with an empty implementation in main.c to ensure .cfsconfig peripheral settings take full effect.
  • Registers-only plugin limitations — Clock enable for non-primary cores, oscillator initialization, and 32-bit timer TMRb clock configuration are not fully generated; manual setup required.
  • Maintenance Tool not supported on macOS 15 Sequoia — Manually delete the CFS directory from the filesystem to uninstall.
Source tag: V1.0.2CodeFusion Studio 1.0.2 is a patch release fixing a critical compatibility issue with VS Code 1.98 (February 2025). A change in Node.js introduced in VS Code 1.98 broke webview-based features in CFS 1.0.0, affecting the ELF File Explorer and Config Tools (Pin Mux, Clock Config).
Upgrade to CFS 1.0.2 to restore full compatibility with VS Code 1.98 and later. If upgrading immediately is not possible, use VS Code 1.97.2 as a temporary workaround.

Bug Fixes

  • Fixed incompatibility with VS Code 1.98 (February 2025) caused by a breaking Node.js change.
  • Fixed an issue with README.md.

Known Issues

See 1.0.0 known issues for all applicable issues.
Source tag: V1.0.0CodeFusion Studio 1.0.0 is the first public release. It provides integrated firmware development for MAX32xxx and MAX78xxx parts via the MSDK and Zephyr RTOS, with graphical Pin Config and Clock Config tools and an ELF File Explorer.

Tools

  • Pin Config Tool — Manage pin multiplexing and pin config choices graphically, then generate code for your SoC.
  • Clock Config Tool — Enable or disable peripheral clocks and configure dividers, muxes, and intermediate steps in the clock tree.
  • ELF File Explorer — Perform detailed analysis and inspection of ELF file contents (currently limited to GCC-derived ELF files).
  • Quick Action Panel — Quick links for common tasks: build, clean, flash, and debug.
  • CFS Build Task Icons — Execute selected tasks for the active project from the VS Code status bar.
  • CFS Terminal — A CFS-aware terminal variant that is pre-configured with CFS settings and paths, enabling use of cfsutil, Zephyr’s west, and other tools without manual configuration.

SDK and Software

  • Zephyr 3.7 support.
  • MSDK (Micro SDK) support.

Host Architecture Support

  • Windows 10 or 11 (64-bit)
  • macOS (ARM64)
  • Ubuntu 22.04 and later (64-bit)

Initial Processor Support

ProcessorMSDKZephyrPin ConfigClock Config
MAX32655Yes
MAX32662Yes
MAX32670Yes
MAX32672Yes
MAX32675Yes
MAX32690YesYesYesYes
MAX78000Yes
MAX78002YesYes

Known Issues

  • No launch.json in imported Zephyr samples — Zephyr samples imported without a launch.json will prompt you to create one on first debug; modify it as needed.
  • Clock Config display — Clock speeds shown on the canvas represent the input clock to the peripheral and may not reflect internal peripheral dividers.
  • Pin Config MAX78002MISC.SWDIO and MISC.SWCLK SWD pin configuration may not work as expected. Leave SWDIO, SWCLK, and GPIO pins P0.28/P0.29 disabled.
  • Pin Config MAX32690P0.18, P3.8, and P3.9 cannot be assigned or configured on the MAX32690 WLP package.
  • Spurious IntelliSense errors — Incomplete IntelliSense configuration may produce false entries in the Problems tab; these can be ignored if the application builds successfully.
  • GPIO pull strength inverted under Zephyr 3.7 — The MXC_GPIO_Config() function sets pull strength inverted in Zephyr 3.7. Set the Select Pull-up/Pull-down field to the opposite strength of what you require. (MSDK projects are unaffected.)
  • ELF File Explorer does not auto-refresh — Close and reopen the file to see changes after modifying an ELF file.
  • M4 core breakpoints are also set on RISC-V core — In dual-core applications, a breakpoint set on the M4 that resolves to the same file/line on the RISC-V core will also be applied to the RISC-V core. Use unique file or symbol names per core, or set breakpoints from the disassembly view to avoid this.

Build docs developers (and LLMs) love