GitHub

Fox Red Labs / Builds / Tools and languages

Blink an LED, then change the pattern in plain English

Plug in a LaunchPad, build TI's blink example, flash it and watch the LED. Then change the pattern: ask for it in plain English, or edit one number in a terminal.

EasyNo wiring3 min to blink, tools installed

The MSPM0 G3507 powered over its USB cable.

Parts and steps

Your board

You need

Software, free with a myTI login: CCStudio 21.0.1, MSPM0 SDK 2.11.00.07.

  1. Plug a micro-USB data cable into the debugger end of the MSPM0 G3507. No driver to install.

  2. In Chrome or Edge, open the browser bench and click Connect.

  3. Click Flash. The page writes the demo to the board.

    You should see: LED2 red (PB26) flashes twice, then pauses.

Or hand it to a coding assistant

Paste this in a terminal. It hands off to an AI assistant.

git clone --depth 1 --filter=blob:none https://github.com/Fox-Red-Labs/fox-red-labs.git && cd fox-red-labs ./start.sh mspm0g3507 blink --assistant claude

It runs the steps above and reports what it saw.

Not Claude Code? Copy this prompt instead.
Clone https://github.com/Fox-Red-Labs/fox-red-labs and read mspm0g3507/AGENTS.md first. Then run Blink an LED on my LP-MSPM0G3507, following docs/builds/blink.md. Tell me when to plug in a board and what you saw at each step.

Make it yours

With an AI assistant

Change the program so the RGB LED shows blue for 2 seconds, then red for 2 seconds, then green for 2 seconds.

You should see: The LED shows blue, then red, then green, two seconds each. You check the LED; the AI cannot.

By hand

Open gpio_toggle_output.c and change the delay constant (16000000 on this board) to 3200000, then build and flash again.

You should see: The LED blinks five times faster.

If something goes wrong

The Mac runs short during the CCStudio installThe installer file is probably still on disk; delete it.
TI shows a short export approval form before the downloadFill it in (about a minute).
CCStudio quits without a window on first launchOpen it yourself from Applications.
Nothing seems to downloadLook in your browser's downloads. The SDK downloads in the browser, not inside CCStudio.
CCStudio lists no SDK afterwardsQuit CCStudio and open it again.
More troubleshooting
Several chat panels openClose the extras; one is enough. Scope starts on Global; Workspace keeps the change out of every other Claude Code session on your Mac.
Claude Code says a server timed outCheck CCStudio is open with a workspace and that step 5's Apply was pressed.
CCStudio is not in /Applications/ti/ccs2101Change that path in all four lines.
The Mac sees nothingTry another micro-USB cable: a charge-only cable looks the same. A USB-C-only Mac needs an adapter.
The board blinked before you typed anythingThat was a program already on it; this step replaces it, so a faster blink is your proof.
The colors are wrongSay what you see in plain words and ask again. The AI edits the same file and flashes again.

Every fix for this board: the FAQ.

What to build next

Every build. The code for all of them is in the GitHub repository.

Evidence and limitsBlinking in 2 min 29 s on the MSPM0 G3507; the blink runs on all 10 boards listed here. Ran on 3 boards. Results, sources, timing and limits.

From a terminal, no AI step, on the LP-MSPM0L1306

Expected result: The board's RGB LED blinks after a flash that takes about a second, and the one-command run ends with an OK line. Whole run 13 to 14 s with the tools installed.

What this shows

  • TI's gpio_toggle_output example builds and flashes on the MSPM0 L1306 from one command, with no CCStudio window and no AI step.
  • The check reads the LED pin through the debugger and passes the pattern you asked for.
What this does not establish, and limits

What this does not establish

  • That an AI assistant can drive this route: no AI step was timed on this board for this route.
  • A person's first-hour time: the 13 to 14 s is a scripted run with the tools already installed.

Limits to keep in mind

  • The helper scripts hard-code the Mac paths in step 1.
  • Checked on an Intel Mac on macOS 15.7 only.
  • Nothing here ran through CCStudio on this board.

Sources

Versions, sizes and timing

Whole route13 to 14 s from the command to a checked pattern, tools installedfirst-use tool notes
Build and flash by handbuild 3.3 s, OpenOCD flash and verify 0.6 s; UniFlash's command line also works in 15.0 sREADME notes
ToolsMSPM0 SDK 2.11.00.07, TI Arm Clang 5.1.1.LTS, SysConfig 1.26.3, xPack OpenOCD 0.12.0-7, Intel Mac on macOS 15.7README notes

Evidence

  • MSPM0 L1306: the one-command route ran on hardware on 2026-10-14 (Intel Mac, tools installed): back up, build, flash and check in 13 to 14 s. first-use tool notes
  • MSPM0 L1306: TI's blink example built in 3.3 s and flashed in 0.6 s with OpenOCD, and the RGB LED cycled (2026-10-06). README notes

Other boards

What the status words mean

Works ran here and did what it shouldCould work some of it ran; real porting effort is left; hover for whatNot for this chip the chip or its vendor software cannot; hover for why

From a terminal, no AI step, on the LP-MSPM0C1104

Expected result: The board's red LED blinks the shipped pattern after a flash that takes under a second, then blinks at the rate you set after you change the delay and flash again. Build under 5 s, flash under 2 s.

What this shows

  • TI's gpio_toggle_output example builds with one make wrapper and flashes with OpenOCD on the MSPM0 C1104, with no CCStudio window and no AI step.
  • On the C1104 a changed delay changed the pin's toggle period from 496 ms to 124 ms, read from the pin.
What this does not establish, and limits

What this does not establish

  • That an AI assistant can drive this route: no AI step was timed on either board.
  • A person's first-hour time: the C1104 number is a scripted run's, with tools installed and hands-on time zero.
  • That the C1104's change was seen by a person; it was read from the pin.

Limits to keep in mind

  • The helper scripts hard-code the Mac paths in step 1.
  • Nothing here ran through CCStudio on these two boards.

Sources

Versions, sizes and timing

C1104 build and flashbuilds 3.1, 3.5 and 4.3 s; OpenOCD flash 0.58 to 0.67 s at a 2.5 MHz adapter speed, 1.3 s at the default 100 kHz; first command to proof 77 s
ToolsMSPM0 SDK 2.11.00.07, TI Arm Clang 5.1.1.LTS, SysConfig 1.26.3, xPack OpenOCD 0.12.0-7, Intel Mac on macOS 15.7.9README notes

Evidence

  • MSPM0 C1104: first command to a changed blink in 77 s on 2026-10-08, proven by reading the LED pin. The box was opened off camera and nobody watched the LED.

Other boards

What the status words mean

Works ran here and did what it shouldCould work some of it ran; real porting effort is left; hover for whatNot for this chip the chip or its vendor software cannot; hover for why

CCStudio and Claude Code, on the LP-MSPM0G3507

Expected result: The RGB LED blinks about five times a second within about 3 minutes of plugging in, once the tools are installed, then shows blue, red and green two seconds each when you ask for that.

What this shows

  • TI's gpio_toggle_output example imports, builds, flashes and runs on the MSPM0 G3507 from one typed sentence to Claude Code, through CCStudio's tool servers.
  • A change you ask for in plain English reaches the board: the delay went from 0.5 s to 0.1 s and a person saw the LED change.
What this does not establish, and limits

What this does not establish

  • A clean-machine setup time: the Mac already had git, Claude Code and Node, and was logged in to Claude and myTI. About 30 minutes of clearing disk space was not counted.
  • That CCStudio's own chat panel does the same: it answers, but no blink has been run through it.
  • That step 6 works as written on a fresh Mac: saving the file by hand was not timed.
  • Any result on Apple Silicon, Windows or Linux, or with an assistant other than Claude Code.

Limits to keep in mind

  • The board was already programmed, so this is not a first-flash-from-new run.
  • CCStudio must stay open: its build and flash servers only run while it is.

Sources

Why this board

It has its own USB debugger, so there is no probe to buy. Its 32 kB of RAM leaves room for a screen or a small AI model.

Versions, sizes and timing

Time, plug-in to a changed blink2 min 29 s on the wall clock, 09:13:32 to 09:16:01 on 2026-10-05, with the tools already installed: import 2 s, build 6 s, flash and start 38 s, about a minute before any prompt was typed
Time, first-time setupabout 29 min on 2026-10-04 (11 of your time, 18 waiting); the Mac already had git, Claude Code and Node and was logged in to Claude and myTI, so this is not a clean-machine number
SoftwareCCStudio 21.0.1 (/Applications/ti/ccs2101), MSPM0 SDK 2.11.00.07, Intel MacBook, macOS 15.7.9
DiskCCStudio and the SDK take 10.3 GB once installed (CCStudio 1.9 GB download, SDK 0.4 GB download becoming 2.2 GB)

Evidence

  • Ran on an MSPM0 G3507 on 2026-10-05 with Claude Code in VS Code calling CCStudio's build and flash servers; a person watched the LED. 2 min 29 s from plugging in to a changed blink, tools installed. This was not a sealed box.
  • Setup steps 1 to 5 were timed on 2026-10-04. Step 5 (CCStudio's own chat panel) answered, but no blink was run through that panel on any board.

Other boards

What the status words mean

Works ran here and did what it shouldCould work some of it ran; real porting effort is left; hover for whatNot for this chip the chip or its vendor software cannot; hover for why

Result grid

Project
LP-MSPM0G3507MSPM0G3507 chip
LP-MSPM0L1306MSPM0L1306 chip
LP-EM-CC2340R5CC2340R52 chip
LAUNCHXL-F2800137TMS320F2800137 chip
Blink an LED
LP-MSPM0G3507Works2 min 29 s, board in hand to blinking (tools already installed)
LP-MSPM0L1306WorksTI's example builds in 3.3 s, flashes in 0.6 s README
LP-EM-CC2340R5WorksAbout 9 min from board in hand to blinking, 8 of them a half-seated probe;
Details82 s with Zephyr. The build takes 22 s and the flash 7 s
LAUNCHXL-F2800137WorksTI's example built in 4.6 s from a terminal and ran from RAM;
Detailsfrl writes it to flash in 9.4 s through CCStudio scripting and times LED4
README

Works ran here and did what it shouldShould work it builds; only naming, packaging or build glue is in the way; hover for whichCould work some of it ran; real porting effort is left; hover for whatNot for this chip the chip or its vendor software cannot; hover for why

Source files

  • README (MSPM0 L1306): setup and build steps
  • README (LAUNCHXL-F2800137): setup and build steps
Get the code and tell us how it wentThe clone command, the board folder with its AGENTS.md, reports from others, and the three report forms.

Get the code

Clone the repository and open the board's folder below. AGENTS.md is a plain text file of notes for AI coding assistants, and llms.txt at the root indexes the site for one.

git clone https://github.com/Fox-Red-Labs/fox-red-labs.git

Code is BSD-3-Clause, writing is CC BY 4.0; third-party folders keep their own licenses.

Built it? Tell us

Built this, or got stuck? Report it on GitHub with a few short answers. Your report shows here in your words, marked as yours. A failure that repeats on the bench gets its fix here.