MSP low-power microcontroller forum - Recent Threads

MSPM0L2117: CAD Symbol and Footprint Not Available in Ultra Librarian

Ibuki Endo — Mon, 05 Oct 2026 08:34:07 GMT

Part Number: MSPM0L2117

Hi expert,

I am looking for the CAD symbol and PCB footprint for MSPM0L2117SRGZR.

I accessed the Ultra Librarian page through the TI product page, but the Symbol and Footprint sections display "Preview is not available" and only a "Request" button is shown.

The 3D model appears to be available, but the symbol and footprint do not seem to be available for download.

Could you please help confirm the following?

1. Are the CAD symbol and PCB footprint for MSPM0L2117SRGZR currently available?

2. If they are not currently available, is there a plan to release them?

3. Is there an alternative source where I can obtain the symbol and footprint (for example, Altium Designer or KiCad)?

Best regards,

Ibuki Endo

MSP430F5326: MSP430F5326IZXHR marking

Jack Barret — Mon, 05 Oct 2026 07:37:46 GMT

Part Number: MSP430F5326

Hi!
The datasheet for part number MSP430F5326IZXHR lists the marking as "F5326",
but we found a component marked "MSP430F5326". Is this possible?


Best regards,
Jack Barret 
www.chiptronik.hk

MSP430FR6043: Noise is observed on the SPI communication signals.

Analogics Rnd Solar — Sun, 04 Oct 2026 07:52:40 GMT

Part Number: MSP430FR6043

Hi Ti teams,
i hope your doing well,

Currently I am working on interfacing the MSP430FR6043 with a LoRa module. but i am experiencing noise on the SPI SCK, MOSI, and MISO signals. I have configured the SPI communication at 5 MHz using the UCA0 module with the secondary-function pin configuration.

I previously worked with the MSP430FR6047 and did not get any issues with SPI communication. I have imported the same FR6047 code to the FR6043 and made the necessary changes to the SPI configuration and pin assignments.I am still not getting clean SPI waveforms on the FR6043.

The above image is SCK & MOSI pins waveforms

This is MISO waveform

And SPI configuration code as fallows

void SPI_Config()
{

WDTCTL = WDTPW | WDTHOLD;

PJSEL0 |= BIT2 | BIT3; //UART
PJSEL1 &= ~(BIT2 | BIT3);

PJSEL0 |= BIT4 | BIT5; // LFXT Crystal

P7DIR |= BIT0; // LoRa RESET (direction out)
P2DIR |= BIT3; // NSS (direction out)

P4DIR &= ~BIT0; //Busy Pin, input

P7OUT |= BIT0; //pin High
P2OUT |= BIT3; //pin High

//Set DCO frequency to max DCO setting
CS_setDCOFreq(CS_DCORSEL_0, CS_DCOFSEL_3);
//Select DCO as the clock source for SMCLK with no frequency divider
CS_initClockSignal(CS_SMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1);

CS_setExternalClockSource(32768,0);
CS_initClockSignal(CS_ACLK, CS_LFXTCLK_SELECT, CS_CLOCK_DIVIDER_1);
CS_turnOnLFXT(CS_LFXT_DRIVE_3);

GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2,GPIO_PIN2,GPIO_SECONDARY_MODULE_FUNCTION);

GPIO_setAsPeripheralModuleFunctionInputPin(GPIO_PORT_P2,GPIO_PIN6 + GPIO_PIN7,GPIO_SECONDARY_MODULE_FUNCTION);

PM5CTL0 &= ~LOCKLPM5;

//Initialize Master

EUSCI_A_SPI_initMasterParam param = {0};
param.selectClockSource = EUSCI_A_SPI_CLOCKSOURCE_SMCLK;
param.clockSourceFrequency = CS_getSMCLK();
param.desiredSpiClock = 5000000;
param.msbFirst = EUSCI_A_SPI_MSB_FIRST;

param.clockPhase = EUSCI_A_SPI_PHASE_DATA_CAPTURED_ONFIRST_CHANGED_ON_NEXT;
param.clockPolarity = EUSCI_A_SPI_CLOCKPOLARITY_INACTIVITY_HIGH;
param.spiMode = EUSCI_A_SPI_3PIN;
EUSCI_A_SPI_initMaster(EUSCI_A0_BASE, &param);

//Enable SPI module
EUSCI_A_SPI_enable(EUSCI_A0_BASE);

// EUSCI_A_SPI_clearInterrupt(EUSCI_A0_BASE, EUSCI_A_SPI_RECEIVE_INTERRUPT);

// EUSCI_A_SPI_enableInterrupt(EUSCI_A0_BASE, EUSCI_A_SPI_RECEIVE_INTERRUPT);
//

//Wait for slave to initialize
__delay_cycles(100);

}

Could you please suggest how to resolve this issue?

Best Regards,
veeranna,

RE: MSP430FR6043: Noise is observed on the SPI communication signals.

David Schultz — Sun, 04 Oct 2026 22:07:03 GMT

Looks like a hardware problem. Signal routing and such.

Also, you appear to leave most of the I/O pins in their default state as inputs. OK if they are connected to Vcc or Gnd. Otherwise a bad idea for CMOS since they can exhibit all sorts of bad behaviour. See guide on connection of unused pins.

RE: MSPM0L1117: LP-MSPM0L1117 : power consumption on FreeRTOS’s tickless idle mode.

Brian Lee — Fri, 02 Oct 2026 20:42:21 GMT

Hi Willie,

Apologies for this oversight. The example uses SysTick as its wake-up timer. SysTick is only available in RUN and SLEEP modes, which explains why the device is not able to wake up from STANDBY.

To fix this with FreeRTOS tickless idle, you will need to provide a custom vPortSuppressTicksAndSleep implementation that replaces the default SysTick-based timing with a TIMG configured to use LFCLK. Since LFCLK continues running in STANDBY0, the TIMG interrupt will wake the device and allow FreeRTOS to resume tick accounting correctly. The timx_timer_mode_periodic_standby example in the SDK shows how to configure TIMG with LFCLK for standby wakeup. Please let me know if you would like a reference implementation.

Best Regards,

Brian

MSPM0L1117: LP-MSPM0L1117 : power consumption on FreeRTOS’s tickless idle mode.

Willie Chang — Tue, 29 Sep 2026 09:09:18 GMT

Part Number: MSPM0L1117

Hi TI teams,

I am evaluating FreeRTOS Tickless Idle on LP-MSPM0L1117.

Using the official blink_led RTOS example:

Normal running current: ~3.3 mA

idle mode standby current: ~1.6 mA

According to the MSPM0L datasheet. The gap between the measured current (~1.6 mA) and the datasheet low-power figures appears quite large.

Could you help to provide:

1. The expected current consumption for the official blink_led example on LP-MSPM0L1117.

2. An explanation of why the measured current is much higher than the datasheet low-power numbers.

3. Which MSPM0 power mode does "FreeRTOS’s tickless idle mode" actually correspond to in the datasheet?

MSPM0G3107-Q1: Flash reading the hex file on the M0G3107QPTRQ1

George Lewis — Mon, 28 Sep 2026 13:31:46 GMT

Part Number: MSPM0G3107-Q1

Hi,

I am attempting to read the flash contents of the MSPM0G3107-Q1 (M0G3107QPTRQ1) device.

The setup has successfully connected once when an external resistor was added to the reset line outside of the board. However, based on the hardware design, an external resistor should not be required for normal operation.

When attempting to connect through the XDS110 debugger, I consistently receive the following error

[9/24/2026, 4:28:38 PM] [ERROR] CS_DAP_0: Error connecting to the target: DAP Connection Error. This could be caused by the device having gone to low power mode. Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information.[9/24/2026, 4:29:08 PM] [ERROR] CS_DAP_0: Error connecting to the target: DAP Connection Error. This could be caused by the device having gone to low power mode. Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information.

[9/24/2026, 4:28:29 PM] [ERROR] CS_DAP_0: Error connecting to the target: DAP Connection Error. This could be caused by the device having gone to low power mode. Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information.[9/24/2026, 4:28:31 PM] [INFO] CS_DAP_0: GEL Output: Initiating BOOTRST Board Reset[9/24/2026, 4:28:33 PM] [INFO] CS_DAP_0: GEL Output: Reset line asserted[9/24/2026, 4:28:36 PM] [INFO] CS_DAP_0: GEL Output: Reset line de-asserted[9/24/2026, 4:28:36 PM] [INFO] CS_DAP_0: GEL Output: Board Reset Complete[9/24/2026, 4:28:36 PM] [INFO] CS_DAP_0: GEL Output: Reset done

RE: MSPM0G3107-Q1: Flash reading the hex file on the M0G3107QPTRQ1

Brian Lee — Fri, 02 Oct 2026 16:51:02 GMT

Hi George,

I do not have access to the linked SharePoint. Can you contact your TI representative to start an email thread for this topic?

Best Regards,
Brian

RE: MSPM0G3107-Q1: Flash reading the hex file on the M0G3107QPTRQ1

George Lewis — Fri, 02 Oct 2026 15:29:35 GMT

Hi Brian,

See document atteached.mbtrglobal-my.sharepoint.com/.../TI PROGRAMMING MICRO 2026.docx

RE: MSPM0L1117: LP-MSPM0L1117 : power consumption on FreeRTOS’s tickless idle mode.

Willie Chang — Fri, 02 Oct 2026 07:32:30 GMT

Hi Brain,

Thanks for your support.

I was able to enter Standby0 successfully and measured a power consumption about 1.7 µA.

However, the original example no longer wakes up correctly after entering Standby0.

Could you please advise what wake-up sources or conditions are required to wake up from Standby mode?

Thanks!

RE: MSP430F6779A: MSP430F6779A: Spy-Bi-Wire connect fails with "unknown device"

Kaushal Patel — Fri, 02 Oct 2026 07:07:16 GMT

I got it working few days back, forgot to reply back.

I had to replace the capacitor value with the one documented in the recommended designs i.e. 1nF. The pin connections are the same as above.

MSP430F6779A: MSP430F6779A: Spy-Bi-Wire connect fails with "unknown device"

Kaushal Patel — Tue, 22 Sep 2026 14:40:24 GMT

Part Number: MSP430F6779A

Device: MSP430F6779
Tool: MSP-FET
IDE: CCS

I have a custom board where only four signals are brought out to a programming header: VDD33, GND, TEST/SBWTCK and RST/NMI/SBWTDIO.

I'm trying to program over 2-wire Spy-Bi-Wire and every connection attempt (debugging/flashing) fails with an "unknown device" error.

Wiring to the MSP-FET 14-pin connector:

SBWTCK → pin 8 (TEST/VPP)
SBWTDIO → pin 11 (RST)
GND → pin 9
VDD → pin 4 (VCC_TARGET)

I had a 0.1uF cap on the SBWTDIO/RST. Which I then removed after reading that for SBW, max cap on this line is only 2.2nF. But even doing so results in "unknown device"

What might be the issue here?

Happy to answer any questions!

Thanks,
KRP

UNIFLASH: Consult UniFlash Using Method for Security Debug.

Rossy Lin — Fri, 02 Oct 2026 02:10:56 GMT

Part Number: UNIFLASH

Dear TI,

I’m using UniFlash to program an MSPM0G3519 MCU and want to configure its debug security settings.

After the firmware is programmed, I need to prevent anyone from reading it back or exporting it as a binary file for copying.

Ideally, the MCU should only be usable for further development or reprogramming after a mass erase.

CCS Setting as below :

As shown in the screenshot,

I currently have to select “Erase MAIN and NONMAIN memory (see warning above)”

before “Mass erase auto” will proceed and allow me to program the correct firmware.

After programming, the MCU works normally and the firmware functions as expected.

However, if I erase the device again, I can no longer program it.

I have to run “Factory reset auto” before I can use and program the MCU again.

I’m not sure when to use each of these buttons or how they differ.

Could you explain the correct procedure?

My goal is to prevent the programmed firmware from being read back or copied,

while still allowing the MCU to be erased and reprogrammed afterward.

What is the recommended way to achieve this?

MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

*** — Thu, 01 Oct 2026 14:23:53 GMT

Part Number: MSPM0L2228

I am trying to understand the event fabric routing and capabilities using the example project "adc12_triggered_by_timer_event".

Can I have TIMER_0 (TIMG0) Publish to ADC12_0 and GPIO_PIN_0 on the same channel 1?

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

Brian Lee — Thu, 01 Oct 2026 20:06:00 GMT

Hi Jerry,

The order of configuring the publisher and subscriber should be done after powering the peripherals, but before enabling/starting their functions. This might require redefining the generated SYSCONFIG_WEAK functions from SysConfig in your own source file — copy the function body as a starting point, remove the SYSCONFIG_WEAK attribute, and add the missing event API calls. The linker will use your version over the generated one.

And actually, I had left some necessary API calls out for your application:

DL_TimerG_enableEvent(TIMER_0_INST, DL_TIMERG_EVENT_ROUTE_1, DL_TIMERG_EVENT_x_EVENT);
DL_TimerG_setPublisherChanID(TIMER_0_INST, DL_TIMERG_PUBLISHER_INDEX_0, 13);

DL_ADC12_setSubscriberChanID(ADC12_0_INST, 13);

DL_GPIO_configSubscriber(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0,
DL_GPIO_SUBSCRIBER_OUT_POLICY_x, DL_GPIO_SUBSCRIBER0_PIN_x);
DL_GPIO_setSubscriberChanID(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0, 13);
DL_GPIO_enableSubscriber(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0);

The next release of SysConfig is scheduled for November.

Best Regards,

Brian

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

*** — Thu, 01 Oct 2026 17:31:05 GMT

Brian Lee

I reached the same conclusion in parallel.

[quote userid="667277" url="~/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1686573/mspm0l2228-event-fabric-routing-multiple-subscribers-on-one-publisher-channel/6499742"]
DL_GPIO_setSubscriberChanID(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0, 12);

DL_GPIO_enableSubscriber(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0);

DL_TimerA_enableEvent(TIMER_0_INST, DL_TIMERA_EVENT_ROUTE_1, (DL_TIMERA_EVENT_ZERO_EVENT));

DL_ADC12_setSubscriberChanID(ADC12_0_INST, 12);
[/quote]My code looks like this though. I see some differences with yours, any issues?
```
    SYSCFG_DL_init();

    NVIC_EnableIRQ(ADC12_0_INST_INT_IRQN);

    DL_TimerG_setPublisherChanID(TIMER_0_INST, DL_TIMERG_PUBLISHER_INDEX_0, 13);
    DL_GPIO_setSubscriberChanID(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0, 13);
    DL_ADC12_setSubscriberChanID(ADC12_0_INST, 13);
```
[quote userid="667277" url="~/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1686573/mspm0l2228-event-fabric-routing-multiple-subscribers-on-one-publisher-channel/6499742"]it will be included in the next release[/quote]Do you know when is the next release?

RE: MSPM0L1117: LP-MSPM0L1117 : power consumption on FreeRTOS’s tickless idle mode.

Brian Lee — Thu, 01 Oct 2026 16:28:56 GMT

Hi Willie,

The default blink_led RTOS example sets the CPU lpm to SLEEP0 in Tickless Idle, and the expected current consumption is expected to be approximately 1.5mA at room temperature:

You can change the low power Policy in SysConfig to Standby here:

Best Regards,
Brian

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

Brian Lee — Thu, 01 Oct 2026 16:11:26 GMT

Hi Jerry,

Sorry for the confusion surrounding this. The three configurable channels in SysConfig are actually the first three 1:1 channels shown in the data sheet:

Our software team is implementing the fix to make all channels configurable in SysConfig and it will be included in the next release. This would also explain why your ADC is no longer firing as the event channel 3 is only 1:1.

The driverlib APIs can still be used to configure the event channels properly:

DL_GPIO_setSubscriberChanID(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0, 12);

DL_GPIO_enableSubscriber(GPIO_GRP_0_PORT, DL_GPIO_SUBSCRIBER_INDEX_0);

DL_TimerA_enableEvent(TIMER_0_INST, DL_TIMERA_EVENT_ROUTE_1, (DL_TIMERA_EVENT_ZERO_EVENT));

DL_ADC12_setSubscriberChanID(ADC12_0_INST, 12);

Best Regards,
Brian

RE: MSPM0G3107-Q1: Flash reading the hex file on the M0G3107QPTRQ1

George Lewis — Thu, 01 Oct 2026 15:27:15 GMT

Hi Brian,

I will share a schematic and some values I am seeing while flashing. idle, and connected through the insert photo option later today as I have tried the to add cap but maybe placement is not correct.

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

*** — Thu, 01 Oct 2026 15:12:52 GMT

Brian Lee

Load of thank you for the confirmation with your screenshots!

I have SysConfig setup similar to you and posted my setup a minute before your last response.

1. How can I tell which of the Channels I am using from 12-15?

2. Also, now my ADC12 event is not firing. Can you advise on why that might be the case?

RE: MSPM33C321A-Q1: MSPM33C321 and MSPM0G3507 Debugger with OpenOCD support

JOJO ARTHUR — Thu, 01 Oct 2026 15:01:02 GMT

Hello Til,

I reviewed the OpenOCD debug probe options for both the MSPM0G3507 and MSPM33C321A.
The following are the main compatible options:
• XDS110 : Supported with OpenOCD for both devices. TI’s OpenOCD configuration files for the MSPM0 and MSPM33 LaunchPads use the XDS110 interface directly, so this is the most straightforward TI-supported option.
• SEGGER J-Link :Supported by OpenOCD over SWD, and both the MSPM0G3507 and MSPM33C321A are supported by J-Link.
• CMSIS-DAP v1/v2 probes : OpenOCD supports CMSIS-DAP over SWD, so these should also work with both devices. However, specific CMSIS-DAP probes may need to be validated if features beyond normal debug/programming, such as device recovery, are required.

I would not consider Black Magic Probe a standard OpenOCD option. Black Magic normally implements its own GDB server within the probe and communicates directly with GDB rather than operating through OpenOCD.

One additional note for the MSPM33C321A: MSPM33 support currently requires TI’s OpenOCD distribution/fork rather than a generic upstream OpenOCD installation. I recommend using TI OpenOCD v1.5.0 or newer for MSPM33C321A support.
Therefore, for a single probe that can be used with OpenOCD across both MSPM0G3507 and MSPM33C321A, the primary options I would recommend evaluating are XDS110, J-Link, and CMSIS-DAP.

Regards,

Benedict Jojo

MSPM33C321A-Q1: MSPM33C321 and MSPM0G3507 Debugger with OpenOCD support

Til Schoengarth — Thu, 01 Oct 2026 12:07:19 GMT

Part Number: MSPM33C321A-Q1

Hi team,

which OpenOCD Debuggers are supported by both M0G3507 as well as M33C321A?

E.g. J-Link, BlackMagic OCD

I know J-Link is supported. A web search also returns results for TI's XDS110 with OpenOCD, but please confirm.

Please confirm all compatible debuggers with OpenOCD support.

Thanks

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

Brian Lee — Thu, 01 Oct 2026 14:54:47 GMT

Hi Jerry,

This can be done with channel 3 in SysConfig:

Best Regards,
Brian

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

*** — Thu, 01 Oct 2026 14:53:59 GMT

Brian Lee ,

I think I found the way to set up 1:2 using SysConfig.

1. How can I tell which of the Channels I am using from 12-15?

2. Also, now my ADC12 event is not firing. Can you advise on why that might be the case?

/*
 * Copyright (c) 2020, Texas Instruments Incorporated
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * *  Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * *  Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 *
 * *  Neither the name of Texas Instruments Incorporated nor the names of
 *    its contributors may be used to endorse or promote products derived
 *    from this software without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
 * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
 * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
 * OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
 * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
 * OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
 * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

#include "ti_msp_dl_config.h"

volatile bool gCheckADC;
volatile uint16_t gADCResult[4];

int main(void)
{
    SYSCFG_DL_init();

    NVIC_EnableIRQ(ADC12_0_INST_INT_IRQN);

    gCheckADC = false;

    DL_TimerG_startCounter(TIMER_0_INST);

    while (false == gCheckADC) {
        __WFE();
    }

    gADCResult[0] = DL_ADC12_getMemResult(ADC12_0_INST, DL_ADC12_MEM_IDX_0);
    gADCResult[1] = DL_ADC12_getMemResult(ADC12_0_INST, DL_ADC12_MEM_IDX_1);
    gADCResult[2] = DL_ADC12_getMemResult(ADC12_0_INST, DL_ADC12_MEM_IDX_2);
    gADCResult[3] = DL_ADC12_getMemResult(ADC12_0_INST, DL_ADC12_MEM_IDX_3);

    __BKPT(0);

    while (1) {
        __WFI();
    }
}

void ADC12_0_INST_IRQHandler(void)
{
    switch (DL_ADC12_getPendingInterrupt(ADC12_0_INST)) {
        case DL_ADC12_IIDX_MEM3_RESULT_LOADED:
            gCheckADC = true;
            break;
        default:
            break;
    }
}

RE: MSPM0L2228: Event Fabric Routing: Multiple subscribers on one publisher channel

*** — Thu, 01 Oct 2026 14:42:23 GMT

Brian Lee ,

Can this be configured in SysConfig or does it have to coded manually?

I was playing around and I think I have it working using 2 channels but want to try and use just 1 channel.