Blog - All Comments

RE: Connecting AI to the Physical World with MCP and a Pi Pico W

BigG — Tue, 22 Sep 2026 08:22:19 GMT

Wow! Awesome work. This is a great use case.

RE: Connecting AI to the Physical World with MCP and a Pi Pico W

Fred27 — Tue, 22 Sep 2026 08:21:52 GMT

"Connecting AI to the Physical World"

Don't do it! It won't end well. Haven't you seen Terminator?

RE: MSPM0 project with VS Code, CMake and GCC - part 7a: middleware example stepper motor control

DAB — Sat, 19 Sep 2026 18:57:09 GMT

Another nice update Jan.

It is too bad they do not have these tools for the older MSP430.

RE: MSPM0 project with VS Code, CMake and GCC - part 7a: middleware example stepper motor control

Qbit — Sat, 19 Sep 2026 15:32:36 GMT

Nice update on the series! Great write up on the cmake setup and VS Code project files.

RE: MSPM0 project with VS Code, CMake and GCC - part 7a: middleware example stepper motor control

Jan Cumps — Sat, 19 Sep 2026 15:05:58 GMT

I learned that the conversation between GUI and firmware is over debug protocol, not via UART. The GUI knows firmware variable addresses (by inspecting hte binary). And uses the debug instructions to directly set and read those variables.

So there is no UART to reuse as interface. I tested the VS Code generated firmware by doing the same as TI. Change variable values in a debug session.
That works, and I now know how to start from this code and build my own.

RE: PWM example for the EasyL1105 MSPM0 board

Jan Cumps — Thu, 17 Sep 2026 16:42:01 GMT

I'm starting development of a stepper motor project. TI has a library for that. Unfortunately, the API documentation link, both in the offline, and downladed Resource Explorer, are not pointing to the correct resource. Online: 404 error, offline: doxygen generated empty documentation.

Google's AI to the rescue: it found a working version: https://software-dl.ti.com/msp430/esd/MSPM0-SDK/2_00_01_00/docs/chinese/middleware/motor_control_stepper/doxygen/api_guide/html/index.html

(it also put a rant:

That is a known, frustrating issue with certain releases of the MSPM0 SDK. TI sometimes packages the Doxygen folder structure with the raw HTML/CSS framework, but misses embedding the actual compiled C-source documentation or links them to an empty index file.

)

RE: MSPM0 interrupt messaging system

Jan Cumps — Mon, 14 Sep 2026 09:26:56 GMT

a few useful examples that TI released in their SDK:

timer notifies ADC
UART notifies DMA
COMPARATOR notifies timer

RE: MSPM0 interrupt messaging system

BigG — Mon, 14 Sep 2026 08:55:12 GMT

Oh wow, that's interesting. In event driven architectures this makes like so much easier.

I'm fully into Zephyr RTOS at the moment and they have something similar, or at least I think it's similar, called zbus: docs.zephyrproject.org/.../index.html

RE: MSPM0 interrupt messaging system

shabaz — Sun, 13 Sep 2026 23:14:18 GMT

Very interesting.. not too often one sees microcontroller projects that can do all the work in the hardware message-passing and nothing needed in the main code : )

RE: MSPM0 project with VS Code, CMake and GCC - part 6: empty "template" project

Jan Cumps — Sat, 12 Sep 2026 17:16:13 GMT

A bit of AI help.

The SDK uses a construct that throws a lot of warnings in GCC 15. Because I'm not changing the SDK source, I tried to suppress it with:

target_compile_options(${CMAKE_PROJECT_NAME} PRIVATE -Wno-volatile)

I got 1 remaining warning: command-line option '-Wno-volatile' is valid for C++/ObjC++ but not for C

Here's Google's AI reply. It solved it.

Question: command-line option '-Wno-volatile' is valid for C++/ObjC++ but not for C

Answer:

This warning or error occurs because the compiler flag -Wno-volatile is being passed to the C compiler (like gcc), but this specific flag only exists for the C++ compiler (like g++).

This usually happens when the flag is added to a global variable (such as CFLAGS or a shared build_flags configuration), forcing it onto all source files regardless of language.

How to Fix It

You need to ensure this flag is only passed to C++ compilations. Here is how to fix it depending on your build tool:

1. In CMake

Instead of using a global compiler definition, restrict the flag using a language-specific generator expression with target_compile_options:

cmake

target_compile_options(your_target_name PRIVATE
    $<$<COMPILE_LANGUAGE:CXX>:-Wno-volatile>
)

RE: MSPM0 project with VS Code, CMake and GCC - part 5: Open .syscfg file in SysConfig GUI

Qbit — Fri, 11 Sep 2026 10:44:00 GMT

Nice trick using the "Open in External App" extension to bridge that gap!

RE: C++ library for ST Teseo GPS - pt. 1: Pico and I2C support

Jan Cumps — Fri, 11 Sep 2026 10:18:56 GMT

I tried to port the examples to a tiny TI MSPM0, but that was too optimistic. The code compiles, but there's not enough memory:

mspm0_gps_teseo_nmea_with_data_processing_i2c section `.text' will not fit in region `FLASH'
mspm0_gps_teseo_nmea_with_data_processing_i2c section `.bss' will not fit in region `SRAM'
`FLASH' overflowed by 187192 bytes
`SRAM' overflowed by 624 bytes

RE: MSPM0 project with VS Code, CMake and GCC - part 5: Open .syscfg file in SysConfig GUI

DAB — Fri, 11 Sep 2026 01:09:13 GMT

Another great update Jan.

RE: MSPM0 project with VS Code, CMake and GCC - part 5: Open .syscfg file in SysConfig GUI

Jan Cumps — Thu, 10 Sep 2026 18:49:59 GMT

I hadn't seen this LaunchPad view before:

RE: MSPM0 C++ project: service handler considerations

Qbit — Mon, 07 Sep 2026 13:28:53 GMT

Useful information, but if I had know it before it could have save my days.