This tutorial shows how an AI agent, together with S32 Design Studio AI Support, can run a complete S32 Design Studio workflow from one natural-language prompt. The workflow covers importing an NXP Application Code Hub example, generating configuration code, building the project, and running it on hardware.
Instead of clicking through wizards, configuration views, and debug settings, you describe the result you want in plain language. The agent then uses S32 Design Studio AI Support's MCP tools to carry out each step.
In this scenario, you ask the agent to complete an end-to-end task:
The agent breaks this request into a sequence of tool calls. It starts the IDE, searches the Application Code Hub, imports the demo, runs code generation, builds the project, and flashes the board.
Note: This tutorial uses these paths:
You can use any location. If you do, update the paths in the prompt to match.
You are a software developer that needs to use S32K312 FRDM board, start S32DS that is installed at C:\NXP\2026\K3_kit\S32DS_3.6.8, import the GPIO Blinking LED Demo for FRDM-A-S32K312 from the NXP Application Code Hub into S32 Design Studio IDE.
After importing, run S32 Configuration Tools to generate code (Pins, Clocks, Peripherals), build and run the project.
Use s32ds-agentic-ai MCP server and if the server disconnects, stop and notify the user.
| Symptom | Fix |
|---|---|
| Project not found in Application Code Hub | Confirm the search term is GPIO Blinking LED Demo for FRDM-A-S32K312. Check that the s32ds-agentic-ai is connected and the ACH tool is available. |
| Import fails or project does not appear in Project Explorer | Try File › Import › Existing Projects into Workspace manually. Confirm the workspace path is C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit. |
| S32 Configuration Tools does not open | Double-click the .mex file in the project root. Ensure the S32K3 SDK is installed and the project SDK is correctly configured. |
| Generate Code produces errors | Check the Pins, Clocks, and Peripherals tabs for validation errors (red markers). Resolve conflicts before regenerating. |
| Build errors after Generate Code | Ensure the generated src/ folder is included in the build path. Try Project › Clean then rebuild. |
| Flash / debug fails | Ensure the board is powered via USB and the J-Link / OpenSDA debugger is recognised. Try Run › Debug Configurations and re-select the correct debug probe. |
| LED does not blink after flashing | Confirm the correct binary was flashed. Check that the debug session started and the program counter advanced past main(). |
| s32ds-agentic-ai server disconnects | Stop immediately and restart the MCP server following the setup instructions. Do not continue until the server is confirmed connected. |
| File | Step | Description |
|---|---|---|
| src/main.c | 1 | Main firmware entry point — GPIO LED blinking loop |
| *.mex | 1 | S32 Configuration Tools project file (Pins, Clocks, Peripherals) |
| generate/src/ | 1 | Auto-generated peripheral initialization source files |
| generate/include/ | 1 | Auto-generated peripheral configuration headers |