MSP low-power microcontroller forum - Recent Threads

MSP430F5528: Broken Link - USB PID

Jean-Philippe Verschueren — Fri, 07 Aug 2026 07:36:00 GMT

Part Number: MSP430F5528

Is the http://software-dl-1.ti.com/dsps/forms/vidtrackerMature.html still valid to obtain a USB PID from TI?

MSP430F5528: USB PID

Jean-Philippe Verschueren — Fri, 07 Aug 2026 07:24:38 GMT

Part Number: MSP430F5528

Is it possible to receive a USB PID from TI when using their USB vendor ID (VID)? How to proceed?

MSPM0G3107-Q1: The IAR workbench or Uniflash reports Target Busy issue while trying to flash the SW and while attaching the debugger

Chinmay Patil — Fri, 07 Aug 2026 07:11:16 GMT

Part Number: MSPM0G3107-Q1

Hello Team,

We are facing an issue with the MSPM0G3107-Q1 device during flashing and debugging.

When attempting to flash the software or attach the debugger to the target, the debugger reports a Target Busy condition, along with different connection/debug errors. The corresponding error screenshots are attached for reference.

The earlier behaviour was that the controller/hardware appeared to enter a low-power state after around 2 to 3 minutes. During that phase, flashing and debugging were possible until the hardware entered the low-power condition.

In the latest observation, the hardware appears to be awake, but flashing and debugger attach are still failing with Target Busy/debug access issues.

We need your support to identify the possible cause and recommended recovery steps for this condition.

Please let us know what additional details are needed to proceed with the analysis.

Best Regards,

Chinmay Patil

MSP430F1611: MSP430-GCC-OPENSOURCE: Linker failes with section .bss LMA wraps around address space

Sven Krauß — Fri, 07 Aug 2026 07:11:00 GMT

Part Number: MSP430F1611

I tried to compile an old project. Everthing compiles but the linker failes with

...msp430-elf/bin/ld: section .bss LMA wraps around address space
collect2: error: ld returned 1 exit status

The map file is created and the .bss section it looks fine. The .bss section is 0x2282 in size and end at 0x345e which is in the range of the MSP430F1611

.bss 0x00000000000011dc 0x2282 load address 0x000000000000f7a8
0x00000000000011dc . = ALIGN (0x2)
0x00000000000011dc PROVIDE (__bssstart = .)
*(.dynbss)
*(.sbss .sbss.*)
*(.bss .bss.* .gnu.linkonce.b.*)
.bss.FREQ_UD_BAND_DATA
0x00000000000011dc 0x4 /tmp/pt21.hrXFmT.ltrans0.ltrans.o

....

.bss.errno 0x000000000000345c 0x2 /home/sven/tools/msp430-gcc-9.3.1.11_linux64/bin/../lib/gcc/msp430-elf/9.3.1/../../../../msp430-elf/lib/430/libc.a(lib_a-reent.o)
0x000000000000345c errno
0x000000000000345e . = ALIGN (0x2)
*(COMMON)
[!provide] PROVIDE (__bssend = .)
0x0000000000002282 PROVIDE (__bsssize = SIZEOF (.bss))

.noinit 0x000000000000345e 0x0 load address 0x000000000000f7a8
...

The call of the linke is the following (obj files and linker paths are striped)

msp430-elf-gcc -ffunction-sections -fdata-sections -Wall -Wno-unused -mmcu=msp430f1611 -mhwmult=auto -msmall -mrelax -mtiny-printf -flto -fno-strict-aliasing -Os -Wl,--cref,--no-warn-mismatch,--gc-sections -static -Wl,-Map=pt21.map -Tmsp430f1611.ld ...{all object files} -o out.elf -lm

Any ideas whats wrong here?

MSPM0G3519: MSPM0G3519: How to enable application checksum check during BCR in SysConfig

Frédéric Fortier — Thu, 06 Aug 2026 15:36:19 GMT

Part Number: MSPM0G3519
Other Parts Discussed in Thread: SYSCONFIG

I'm trying to enable the application checksum check during BCR, as documented e.g. in "MSPM0 NONMAIN Flash Memory Configuration Guide" section 3.1.6 Application Digest Check, but I cannot find the fields to do this through SysConfig. It looks like the same question was asked a while ago https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1362846/mspm0l1306-how-to-enable-application-crc-check-during-bcr-in-sysconfig

Is there now a better recommended way of doing this than manually updating the
BCR_Config struct (including manually computing userCfgCRC)?
Is SysConfig support for this feature still on the roadmap?

Thank you!

MSP-EXP430FR2433: RFQ & Technical Recommendation: Ultra-Low Power MSP430 Development Board for 5-Year Battery-Operated Industrial Application (135 Units)

Ahamedafzal M — Thu, 06 Aug 2026 14:59:27 GMT

Part Number: MSP-EXP430FR2433
Other Parts Discussed in Thread: MSP430FR2433

Dear TI Sales / Technical Support Team,

We are evaluating microcontroller development boards for a commercial industrial monitoring system and would like to request a formal quotation along with your expert technical recommendation.

Application Overview:

The system monitors pressure levels via a mechanical transmitter and triggers a 24V latching solenoid valve through short MCU pulses when predefined thresholds are crossed.
The board must operate on ultra-low power to achieve a minimum 5-year standalone lifespan using Saft LSH20 D-size Li-SOCl₂ battery cells (configured to deliver ~24–28V DC input).
Maximum ambient operating temperature: 85°C.

MCU & Development Board Focus:
We are specifically interested in the MSP430FR2433 or any equivalent ultra-low-power FRAM/energy-efficient microcontroller from TI that best aligns with our power, performance, and environmental requirements. Please recommend a suitable evaluation/development board (e.g., MSP430 LaunchPad) if available for rapid prototyping and power validation.

Commercial Details:

Initial order quantity: 135 units
Anticipated significant repeat orders upon successful project implementation

Requested Information:

- Quotation & standard lead time for the recommended MCU + development board (and any necessary low-side MOSFET/driver components for the 24V solenoid load)
- Technical justification for your recommendation (deep-sleep current, wake-up sources, FRAM endurance, operating temperature range, and power optimization strategies)
- Availability of TI reference designs, battery life estimation tools (e.g., PowerWise/e²Pulse), or low-power firmware examples for industrial pressure/valve control applications
- Volume pricing tiers & long-term supply commitment options

Please share the details at your earliest convenience. We are prepared to proceed with procurement upon technical validation and commercial approval.

MSPM0C1104: Device seems to go into reset exactly 10s after power up every time

Parker Bondi — Thu, 06 Aug 2026 04:10:36 GMT

Part Number: MSPM0C1104

I’m using the MSPM0C1104S8YCJR. I had five boards assembled, and boards #1 and #2 have been working well—I developed firmware on #1 and have been able to repeatedly upload firmware to both boards as long as I run the MSPM0_Factory_Reset_Tool before each upload.

I just powered up board #3. First few attempts at running my program and demo and I got a lot of success, but I noticed that towards the end of my demo (maybe 30s) the device failed. I didn't think much of it, used the factory reset tool to reset it, and tried again. Well a similar thing happened at least another 5-6 times. Now I’m seeing behavior that doesn’t match the expected sequence anymore and I'm not able to factory reset the device anymore no matter what I do.

For context - normally, a blank firmware board draws about 2 mA, and if I power it up with RST held low, it draws about 1 mA. Boards #1 and #2 behave exactly like this. Board #3 is different: when I power it up normally, it draws ~2 mA for about 8–9 seconds, and then at exactly the 10‑second mark it drops to 1 mA and stays there permanently. I realize I’m close to the measurement limits of my bench supply, but the XDS110 debug probe also reports that the device appears to be stuck in reset.

However the problem it creates for me is that I cannot get the MSPM0_Factory_Reset_Tool to successfully reset this MCU. The exact sequence that works reliably for boards #1 and #2 is:

Power down the board and tie RST low while it’s off.
Power up the board.
Refresh/reset the Factory Reset Tool webpage.
Attach MSPM0C110x.
Run a manual reset (I’ve also tried automatic).

On board #3, no matter what I do, I never get the “device successfully reset” message from the tool.

MSP430FR6047: MSP430FR6047 erroneous results

Mary Frantz — Wed, 05 Aug 2026 15:48:10 GMT

Part Number: MSP430FR6047

I am developing a product using the MSP430FR6047, and am using the EVM for early testing. With the Design Center, it functions fine. I compiled and ran the FR6047_USSWLib_template_example, with a few modifications to change how the results are sent over the uart. The configuration header files were generated with the Design Center.

After a few minutes, the detaToF and volumeFlowRate suddenly change to unreasonable values. With no water flowing the VolumeFlowRate changes to ~5000 l/hr. Sometimes the temperature is also wrong (65 degrees when it should be 75). If I restart the processor the values return to normal. I set a breakpoint and confirmed the erroneous values are in the results (and not a communication issue). The return codes are normal.

(0 for USS_startUltrasonicMeasurement(), and 122 for USS_runAlgorithms() )

What can be wrong? What can I look at to debug this?

Configurtion page is below.

MSP-EXP430FR2355: MSP-EXP430FR2355 Meaningless UART Output

Ian Sanders — Wed, 05 Aug 2026 11:33:53 GMT

Part Number: MSP-EXP430FR2355

Hi All

I am doing a very simple project (so I thought) where I read the value in on P1.4 ADC from a 10k pot connected to 3.3V.

The ADC reads the value with no issues what so every. However, when I try to transmit the HEX value out on the UART I get meaningless characters which says to me it is a baud rate configuration issue. But I followed all the user guides and the formula and check it against several online AI tools and tey all come up with the same answer.

I suspect it is something to do with how I have set up my UART interrupts

I am using SMCLK = 1MHz ad the desired baud rate is 9600

The code is below and ay help would be much appreciated.

#include <msp430.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <math.h>

//Variables

volatile unsigned int ADC_value = 0;

void UART_init(void)
{

/* Configure UART pins (P4.2 = RXD, P4.3 = TXD) */
	
	P4SEL0 |= BIT2 | BIT3;                    			// Set P4.2 and P4.3 to UART mode
	P4SEL1 &= ~(BIT2 | BIT3);

	UCA1CTLW0	|= UCSWRST;					// Put eUSCI_A1 in reset
	UCA1CTLW0	|= UCSSEL__SMCLK;				// Choose SMCLK clock source

/*	Baud Rate Calculation for 9600 baud with 1,000,000 Hz SMCLK:
  	1000000 / 9600 = 104.166 -> UCBRx = 104, fractional portion = 0.166
  	Using Table 22-4 from User's Guide: UCBRSx = 0x11*/ 

	UCA1BR0		= 0x68;						// 1MHz 9600 baud
	UCA1BR1		= 0;
	UCA0MCTLW	= 0x1100;
	
	UCA1CTLW0	&= ~UCSWRST;					// Initialize eUSCI state machine
	UCA1IE		|= UCTXIE;				 	// Enable USCI_A1 TX interrupt
	
	__bis_SR_register(GIE);
	__no_operation();
}

int main(void)
{
	WDTCTL = WDTPW | WDTHOLD;	            			// stop watchdog timer
	
/* Disable the GPIO power-on default high-impedance mode to activate
 * previously configured port settings*/

	PM5CTL0 &= ~LOCKLPM5;

	UART_init();

/* Configure ADC Channel Pins*/

	P1SEL1 |= BIT4;                         			// Configure P1.4 for ADC
	P1SEL0 |= BIT4;

/* Configure ADC12 */

	ADCCTL0     =   ADCSHT_2 | ADCON;       			// ADCON, S&H=16 ADC clks
	ADCCTL1     =   ADCSHP;                 			// ADCCLK = MODOSC; sampling timer; ADC conversion start source is ADCSC bit
	ADCCTL2     =   ADCRES_2;               			// Set ADCRES_2 to binary 10 for 12 bit resolution
	ADCIE       |=  ADCIE0;                 			// Enable ADC conv complete interrupt
	ADCMCTL0    |=  ADCINCH_4 | ADCSREF_0;  			// ADC channel A4 selected as input and internal reference selected 000b = {VR+ = AVCC and VR- = AVSS}

/* Configure voltage reference for ADC conversion */
	PMMCTL0_H = PMMPW_H;                                      	// Unlock the PMM registers
	PMMCTL2 |= INTREFEN;                                      	// Enable internal reference 1.5V
	__delay_cycles(400);                                     	 // Delay for reference settling

	while(1)
	     {
	        ADCCTL0 |= ADCENC | ADCSC;                            	// Sampling and conversion start
	        __bis_SR_register(LPM0_bits | GIE);                  	// LPM0, ADC_ISR will force exit
	        __no_operation();
	     }
}

#pragma vector = ADC_VECTOR
__interrupt void ADC_ISR(void)

{
    switch (__even_in_range(ADCIV, ADCIV_ADCIFG))
    {
        case    ADCIV_ADCIFG: 						// ADC12MEM1 Interrupt
                ADC_value = ADCMEM0; 					// Save MEM0
                __bic_SR_register_on_exit(LPM0_bits | GIE);		// Exit CPU, clear interrupts
                break;
               default:
                break;
    }
}

#pragma vector = USCI_A1_VECTOR 					// Vector depends on specific MSP430 family variant
__interrupt void USCI_A1_ISR(void)
{
    switch(__even_in_range(UCA1IV, USCI_UART_UCTXCPTIFG))
    {
        case USCI_NONE: 
            break;
            
        case USCI_UART_UCRXIFG:
            break;
            
        case USCI_UART_UCTXIFG:
        	
            UCA1TXBUF = (ADC_value);
            break;
            
        case USCI_UART_UCSTTIFG:
            break;
            
        case USCI_UART_UCTXCPTIFG:
            break;
        default:
        	break;
    }
}

UART Issue.txt

MSPM0G1519: MSPM0-DIAGNOSTIC-LIB : Build for MSP0G1519

Ruediger — Wed, 05 Aug 2026 06:42:20 GMT

Part Number: MSPM0G1519

Hi,
we want to integrate the Diagnostic Lib into our CI and our goal is to build it for our special device MSPM0G1519 and not for the superset devices. The only precompiled versions available are the libraries for the Superset controllers of the respective family. Our approach was therefore to include the source code and build it ourselves for the device family DeviceFamily_ID_MSPM0G151X and __MSPM0G1519__ (DeviceFamily.h”). However, we receive an error stating that the family is not supported caused by the if else statement in “sl_cpu.h“. There is only DeviceFamily_ID_MSPM0G350X, DeviceFamily_ID_MSPM0L222X and DeviceFamily_ID_MSPM0G351X supported.

Could you please help us with this problem and explain how to use the library for the MSP1519 correctly? We'd prefer not to use a define from another derivative, since we'd otherwise have to explain this again our certification body.

Thanks and best regards
Ruediger

MSPM0L1117: Schematic Check

Ke Quan Tok — Wed, 05 Aug 2026 01:55:32 GMT

Part Number: MSPM0L1117

Hello BU,

My customer is developing 24V BMS and need help for the schematic check. Can you help to check if there are any issues for MSPM0L1117 portion before they proceed to PCB printing?

SCH_24VBQ76492_2026-07-30 (1).pdf

Regards,
John

MSP430F1232: Information Memory contents changing between read operations

Ibuki Endo — Wed, 05 Aug 2026 00:55:37 GMT

Part Number: MSP430F1232

Hi expert,

We observed an issue on MSP430F1232IPWR where the Information Memory area (0x1000-0x10FF) changes every time the device is read.

The programming house only programs Main Memory and does not write anything to Information Memory. Therefore, Information Memory is expected to remain in its TI factory default state.

Main Memory contents remain stable, but Information Memory contents vary between read operations on the failed units.

Could you please help clarify the following?

What is the expected factory default content of the Information Memory area (0x1000-0x10FF) on MSP430F1232 devices? Does TI program any calibration or manufacturing data into this region?
Is there any known condition or failure mechanism that could cause Information Memory contents to appear different each time they are read, while Main Memory remains unaffected?

Best regard,

Ibuki Endo

MSP430FR5994: MSP430FR5994: ADC Temperture Sensor Sampling time

Mike52327 — Tue, 04 Aug 2026 22:25:33 GMT

Part Number: MSP430FR5994

Hello,

Looking into usign the internal temperature sensor of the MSP430FR5994 in our project, but I noticed that the minimum sampling time for the internal temp sensor is specified as 30 micro seconds in the data sheet. It also specifies that this includes a t_sensor_on time.

Is there a way to leave the sensor on so we can reduce the runtime sampling time of the temperature sensor? And if so, does anyone know where this t_sensor_on time is documented? Could not find in the data sheet...

We have a timer->DMA->ADC->DMA sequnce that runs at a rate that will not work with a 30 microsecond sample time. Our Conversion sequence is 10 or so channels, and that one channel would force all to be sampled with the same sampling time...

If not, will look to see if we can maybe interleave ADC sequences to minimize how often we sample the sensor... I realize temp will not change often... just looking for the least complex way to code such...

Thanks,

-mike

MSPM33C321A-Q1: Maximum On-Off Cycles

Til Schoengarth — Tue, 04 Aug 2026 08:52:57 GMT

Part Number: MSPM33C321A-Q1
Other Parts Discussed in Thread: MSPM33C321A

Hi team,

how many On-Off cycles can the MSPM33C321A handle?

From a mission profile perspective there are no issues.

BR,

Til

MSPM0C1106: Are peripheral register values maintained when PWREN bit is set back to 0?

Oliver Suchanek — Tue, 04 Aug 2026 08:20:31 GMT

Part Number: MSPM0C1106

Are peripheral register values maintained when PWREN bit is set back to 0?

The datasheet/refernce manual only states that they are not accessible while PWREN is 0. I cannot find any information if the values are maintained while PWREN is set to 0 and then back to 1 again.

TLV803E: TLV803EA26DBZR RESET pin is pulled LOW.

Kevin Huang8 — Mon, 03 Aug 2026 16:40:56 GMT

Part Number: TLV803E
Other Parts Discussed in Thread: TLV803

The circuit uses the TLV803EA26DBZR (U14) with its RESET pin pulled up to 1V8_LDO through resistor R29.
(1)When R30 is populated (0ohm): The POR_B voltage is pulled down to 0.23V, which matches the chip's typical low-level output voltage (V_OL).

(2)When R30 is unpopulated (NC), The POR_B voltage returns to 1.8V.

MSP430FR50431: USS blowing - suspected Hot Plugging issue (ESD?)

Blake Carpenter — Sun, 02 Aug 2026 22:40:51 GMT

MSPM0-SDK: SYSCONFIG does not allow VCO more than 160 MHz

Mesut KILIÇ — Fri, 31 Jul 2026 15:35:13 GMT

Part Number: MSPM0-SDK
Other Parts Discussed in Thread: MSPM0G3519, SYSCONFIG

Hello ,

I am using MSPM0G3519 MCU and MSPM0 SDK. I have 24 MHz crystal on my board. I cannot set VCO to more than 160 MHz with MSPM0 SDK 2.10 and after. I am able to set with MSPM0 SDK 2.9.

I checked datasheet. fVCO max is 400 MHz.

How do I solve this problem?

Thanks

2.9

2.10

MSPM0G3218-Q1: Unexpected ADC MEMRESIFG interrupt delay after Timer Trigger Event

Caspar Bean — Fri, 31 Jul 2026 09:28:20 GMT

Part Number: MSPM0G3218-Q1

Hello TI,

I am using a timer to trigger an ADC, which has two channel config and a repeat Sequence config, my current problem is, that the time between timer EVENT Trigger and actual MEMRESIFG interrupt is much longer than expected. So far I use SCOMP0=0x30 (32MHz) for my first MEMRESIFG and the corresponding conversion time. I should have around 1.7µs but get ~9µs.

In between the Timer trigger (yellow) and Memres interrupt (red) I do nothing but wait for the ADC interrupt and set GPIO in ISR. So far I think I made the right config for ADC and timer because I had it already running fine on another MSP.

Thanks in advance

MSPM0-SDK: Error Message during install CCS

Logan Kim — Fri, 31 Jul 2026 04:00:52 GMT

Part Number: MSPM0-SDK

Hello Team,

I got inquriy from customer as below.

When they install the CCS, the error below is appearing. could you let me know how can we proceed the next step?

Thank you.

MSP430FR2433: MSP Debug Stack Unsupported

David Austin — Fri, 31 Jul 2026 00:58:44 GMT

Part Number: MSP430FR2433

The open-source MSP Debug Stack no longer compiles with reasonably recent versions of the Boost libraries.

The MSPDS-USB-DRIVERS Linux64 installer no longer installs anything.

Note of these have been updated for over 6 years, despite this being the preferred TI development tool.

MSPM0G5117: MSPM0G5117SPMR CAD files

Alejandro Perez — Thu, 30 Jul 2026 15:48:23 GMT

Part Number: MSPM0G5117

Hello I am currently working on a reference design that uses the MSPM0G5117SPMR, but that package has no design files, would it be possible to get that made into the TI vault?

Best regards,

Alejandro Perez

MSPM0L2228: CIO impact on RTC_A

*** — Thu, 30 Jul 2026 12:25:37 GMT

Part Number: MSPM0L2228
Other Parts Discussed in Thread: SYSCONFIG

I am temporarily using CIO for inital development before developing a dedicated UART debug peripheral. The CIO features I am using are: printf() and fprintf(). I am capturing log records that are about 218 bytes tagged with a RTC_A timestamp.

Based on my current understanding the RTC_A that is clocked by LFCLK: LFOSC, any CIO process should not impact the RTC_A operation.

Over the course of 30 minutes of logging, I am experiencing over 15 minutes of RTC_A timestamp lag. I am trying to understand why?

Any information or technical details regarding the CIO impact on RTC_A would be appreciated.

MSP430FR6045: Code Sonar CWE-25 / MISRA Warnings in TI UltrasonicWaterFR604x_02_40_00_00 Source Code

Anup Kumar — Thu, 30 Jul 2026 09:26:41 GMT

Part Number: MSP430FR6045
Other Parts Discussed in Thread: MSP430FR6047

Dear TI Support Team,

We are using the UltrasonicWaterFR604x_02_40_00_00 software package provided by TI as the base firmware for our ultrasonic water meter based on the MSP430FR6047.

As part of our software quality process, we are performing Code Sonar static code analysis on the complete project. During the analysis, we observed a significant number of warnings originating from the TI source code itself.

Most of the reported issues are related to:

Cast Alters Value
Coercion Alters Value
Inappropriate Assignment Type
MISRA C/C++ rule violations
CERT C recommendations
CWE-related issues (SonarQube classifications)

For example, several warnings are reported in the following TI source files:

USS_computeAbsTOF_lobe.c
USS_Lib_HAL.c
ussSwLibISR.c
Other source files included in the TI library

The attached screenshots show examples of these warnings.

Our questions are:

Has TI already analyzed these static analysis findings?
Are these warnings expected and considered acceptable in the reference implementation?
Is there an updated version or patch of UltrasonicWaterFR604x_02_40_00_00 that addresses these issues?
For safety and compliance purposes, should these warnings be ignored, or does TI recommend resolving them before product release?

Since our product must comply with internal coding standards and static analysis requirements, we would appreciate TI's guidance on how these warnings should be handled.

If you require then I can share the PDF report which includes all the related warnings.

Thank you for your support.

Best Regards,

Anup Kumar

MSPM0G3507-Q1: MCU does not boot up 2 out of 10 times

DEV_DUKE — Thu, 30 Jul 2026 09:08:02 GMT

Part Number: MSPM0G3507-Q1

Hi E2E support,
I am facing a peculiar problem, that the MCU fails to boot up / run the firmware in it, for 2 or 3 times out of 10. I am using G3507 mcu with 24MHz external crystal. As soon as the code starts running, there is an led(blink at 500ms) and a seven segment display which immediately spring to life if the MCU boots up correctly. On failure, neither glow. Attached the MCU pinout, LDO, external crystal schematics. Please help.