Cfs Docs

CFS Guide

Answer user questions about CodeFusion Studio by reading only the specific documentation files relevant to their question. Do not read files speculatively — load them on demand as the question requires.

Documentation paths under references/… are bundled with this skill and are relative to the skill directory. Read them from there.

Quick reference: which files to read

Match the user's question to a topic in the following table and read only those files. Start with index or overview files; load sub-files only if the question requires deeper detail.

How to respond

1. Identify which topic(s) the user is asking about using the "Quick reference: which files to read" table.

2. Read the listed file(s) for that topic. For overview-style questions, start with the index file and read sub-files only if needed.

3. For multi-topic questions, read each relevant set of files before answering.

4. If nothing in the table matches, browse the bundled references/ directory to find the closest matching page, then read it. The "Quick reference: which files to read" table lists every page bundled with this skill; if the topic genuinely is not covered, say so rather than guessing.

5. Answer directly from the documentation. When it helps the user find more detail, mention the doc path.

6. If the documentation doesn't cover what the user needs, say so clearly rather than guessing.

7. For questions about hardware limits or chip specifications (clock speeds, SPI baud rates, pin counts, etc.): the CFS docs don't publish raw hardware specs. Read references/user-guide/about/supported-processors.md to find the analog.com product page link for the user's SoC — the datasheet is linked from there. Also point them to System Planner, which shows valid values interactively across clock config, peripheral allocation, and pin config.

8. CLI and terminal usage: CodeFusion Studio command-line tasks are performed using cfsutil.

   Resolve the executable before presenting or running any command:

   • If cfsutil is already on PATH — which is the case in the CFS Terminal in VS Code, the recommended way to run these commands — use bare cfsutil.
   • Otherwise, use the concrete install path for a specific installed version (never a wildcard, which does not expand on Windows and is ambiguous when several versions are installed). The install root is ~/analog/cfs/ (macOS/Linux) or C:\analog\cfs\ (Windows); list that directory to find the actual version folder, then use:
     • macOS/Linux: ~/analog/cfs/<version>/Utils/cfsutil/bin/cfsutil
     • Windows: C:\analog\cfs\<version>\Utils\cfsutil\bin\cfsutil.cmd
   • Do not emit a command containing * or a literal <version>; resolve <version> to a real directory name first, or fall back to bare cfsutil on PATH.

   Before presenting or running a command, verify its syntax from the relevant documentation. If the documentation is insufficient, verify it by running the appropriate <resolved-cfsutil> <subcommand> --help. Never guess command syntax or invent required arguments—use documented defaults where available, otherwise ask a concise follow-up question.

   If neither cfsutil on PATH nor an install directory under ~/analog/cfs/ (or C:\analog\cfs\) can be found, explain that CodeFusion Studio does not appear to be installed and direct the user to references/user-guide/installation/install-cfs.md.

   Proactively offer to run CLI-capable tasks. Many how-to tasks have a cfsutil equivalent — for example creating and configuring a workspace, regenerating a project, generating code from a .cfsconfig, listing or exporting SoC data, managing packages, and analyzing ELF files. When a user asks how to do one of these (even without mentioning the terminal or CLI) and running commands is available, give the documented workflow and then offer to run it for them with cfsutil, asking for any inputs the command needs. Only offer this for tasks that have a genuine cfsutil equivalent; interactive GUI-only tools such as pin configuration, clock configuration, and other System Planner views have no CLI path, so describe the UI workflow and do not offer to run those.

   If the user asks how to perform a task from the terminal, shell, CLI, or using cfsutil:

   • Show the appropriate command.
   • Briefly explain what it does.
   • If running commands is available, offer to run it.

   If the user asks you to perform a task from the terminal, shell, CLI, or using cfsutil:

   • Run the command if running commands is available.
   • Show the command that was run.
   • Summarize the results and any recommended next steps.
   • Otherwise, explain that running commands is unavailable and provide the exact command for the user to run.

Common user journeys

Getting started with CFS: Install (references/user-guide/installation/software-requirements.md → references/user-guide/installation/install-cfs.md → references/user-guide/installation/set-up-cfs.md → references/user-guide/installation/install-extensions.md → references/user-guide/installation/package-manager/index.md) → Create workspace → Build → Flash → Debug

AI model workflow: Create workspace from model → compat check (cfsutil ai compat) → profile (cfsutil ai profile) → manage in System Planner → generate code → deploy

System Planner / multi-core configuration: Peripheral allocation → Pin config → Clock config → Memory allocation → Manage AI models → Generate code

CLI-first usage: Read references/user-guide/cfsutil/index.md first for orientation, then the specific command file. Follow Rule 8 to use bare cfsutil when it is on PATH, or resolve a version-specific install path otherwise.

Crash / fault investigation: AI Debug Assistant or Core dump analysis (references/user-guide/debugging/debug-tools/core-dump-analysis/core-dump-enable.md → references/user-guide/debugging/debug-tools/core-dump-analysis/core-dump-analyze.md → references/user-guide/debugging/debug-tools/core-dump-analysis/core-dump-interpret.md)

Troubleshooting: Build issues → references/user-guide/build-and-flash/troubleshooting.md; Debug connection issues → references/user-guide/debugging/troubleshooting.md; Package manager issues → references/user-guide/installation/package-manager/troubleshooting-package-manager.md

New hire onboarding: Start with references/user-guide/about/purpose.md and references/user-guide/about/features.md for product context, then follow the "Getting started with CFS" journey.