MSP low-power microcontroller forum - Recent Threads

LP-MSPM33C321A: Flashing: Device connection error.

Clemens Kutz — Mon, 19 Oct 2026 09:57:34 GMT

I have a LP-MSPM33C321A and after unboxing I could flash and debug the device. But when my latest software was flashed, it stopped responding.

It says "Texas Instruments XDS110 USB Debug Probe/CORTEX_M33 Error connecting to the target: Device Connection Error. This could be casued by the device having gone into low power mode. Try forcing an external reset pressing the "Force Reset" button. If the error persists, try: 1) Invoking BSL, 2) Calling a DSSM Mass erase, or 3.) Calling a DSSM Factory Reset. Check device FAQ for more information."

I tried "Force Reset", I tried the hardware reset button, but I cannot reestablish connection.

When I select the button "Read boot diagnostics", I see an error code in the terminal:

CS_DAP_0: DAP Disconnect
CS_DAP_0: DAP Reconnect
CA_DAP_0: Reset don
CS_DAP_0: Device diagnostic read = 0x8000007

I have not found a description of the procedures how to 1) invoking BSL -> that should be done automatically through the XDS110, right?
2.) Calling a DSSM Mass Erase

What are the next steps I could take?

MSPM0G3519: Flash erase error issue with GHS compiled binaries

Lokesh Uppara — Thu, 15 Oct 2026 18:15:50 GMT

Part Number: MSPM0G3519

Issue Description

We could see Flash erase Error while flashing binaries using T32.

Workaround:

Problem 1:

It is observed that Lauterbach used for TI(MSPM0G351X) target shows "Erasing SD 0x00..0x7FFFF" continuously. This is causes flashing incomplete.

Solution :

Step 1 : Click 'STOP' option as shown below

Step 2 : Go to CPU → System Setting → CpuBreak : Change it to Enable from Denied (Default is Denied - This is required for UDS $11 01 service to make sure control not halts at start after reset) and break the execution.

Step 3 : Execute below command Flash.Erase ALL (After Step 1 or Step 2, do not perform any in-target or CPU reset.)

The above steps will enable to re-flash the .elf

Problem 2:

Step 1: If Flash.erase All does not work, execute Flash.UNSECUREerase. This will cause the target to power down.

Step 2: Perform an In-Target Reset, then flash the required Cmm file.

MSP430-GCC-OPENSOURCE: Code Composer Studio assembler comments

James Bunger — Thu, 15 Oct 2026 14:03:13 GMT

Part Number: MSP430-GCC-OPENSOURCE
Other Parts Discussed in Thread: MSP430F4152

I am converting to Code Composer Studio version 21.0.1.10__1.12.1 and targeting a MSP430F4152.

All the code is assembler and I have not been able to figure out why some comment lines are flagged as an error ad others are ok. Please see the screen shot below and any advice is appreciated.

Thanks!

MSPM0L2227: Program fails DSSM issue

Pritam Malusare — Thu, 15 Oct 2026 08:51:30 GMT

Part Number: MSPM0L2227

Hi,

My mspm0l2227 controller suddenly not programming and showing boot code like 0x0000036 and perform factory reset DSSM what's mean and how to solve this ?

MSPM0G3507: Clarification on MSPM0G3507 Unique Device Identifier

Anonymous — Wed, 14 Oct 2026 17:06:31 GMT

Part Number: MSPM0G3507

Hi Ti,

We need a unique identifier for each MSPM0G3507 MCU that does not repeat and is exclusive to that specific MCU. Could you kindly clarify which of the following identifiers we should use to uniquely identify an individual MCU?

TRACE ID
USER ID
A combination of both TRACE ID and USER ID

Thank you for your clarification.

MSP-EXP430FR5994: MSP-EXP430FR5994: eZ-FETs debuggers needs recovery

Minh Nguyen — Wed, 14 Oct 2026 09:04:23 GMT

Part Number: MSP-EXP430FR5994
Other Parts Discussed in Thread: MSP-FET

Hi, I am working with 2 MSP-EXP430FR5994 LaunchPad, and it broke down the same way.
First, I downloaded the latest version of CCS IDE and plugged in 1 of my LaunchPad, then the IDE request a firmwire update on my LaunchPad, after that it returned an error and now I keep getting "One of the connected MSP-FETs / eZ-FETs debuggers needs recovery" error whenever I tried to recover on the IDE.
I tried with a second one, at first, I tested it with the Out-of-the-box Demo GUI, and it worked properly, I can start/stop the temperature live mode. But when I went to the CCS IDE for a Blink LED project, it also requires me to hit update and the error was the same as last time.
Applications I tried to debug these:
MSPFlasher
CCS IDE (older versions)
MSP Debug Stack

Can the support team diagnose what is the problem here? Thank you very much.

MSPM0L1306: ssue where the battery monitoring/charging circuit is susceptible to breakdown (VCC-to-GND short) when the battery is unplugged and reinserted after being fully

Wilson Liang2 — Wed, 14 Oct 2026 07:04:15 GMT

Part Number: MSPM0L1306

Hi Sir

My customer is using the MSPM0L1306 in a battery charging module design. In a new project, they found that the MSPM0L1306 can easily malfunction or even become damaged (VCC-to-GND short) when the battery is unplugged and reinserted. Could you please help review the schematic (via email)? We would also appreciate any design recommendations or experience sharing regarding this issue.

Thank you.

UNIFLASH: Consult MCU Programming Method via Uni-Flash Bootloader Option

Rossy Lin — Wed, 14 Oct 2026 07:03:38 GMT

Part Number: UNIFLASH
Other Parts Discussed in Thread: MSPM0G3519, MSPM0G3507

Dear TI ,

Currently, I am using UniFlash and selecting the Bootloader option to program the MSPM0G3519 MCU via UART.

Therefore, I removed the SWD connection on the EVM, as shown in the attached picture.

In UniFlash, I selected MSPM0GX51X (Bootloader) and loaded a .bin file or .out file.
Then I selected the UART interface, such as COM10. I also tested COM9.

However, the programming always fails, as shown in the screenshot below.

The same procedure works successfully on the MSPM0G3507, so I would like to confirm whether there are any additional settings or differences when using the bootloader to program the MSPM0G3519 via UART.

Thank you.

MSPM0G1105: Question regarding FUNC description in MSPM0G Technical Reference Manual (SLAU846E)

Ibuki Endo — Wed, 14 Oct 2026 04:14:21 GMT

Part Number: MSPM0G1105

Hi experts,

Could you please confirm a possible documentation error in SLAU846E, page 795, Table 10-32?

The FUNC field currently shows:

8h = 64-bit multiply result
9h = 64-bit multiply result

Based on the surrounding FUNC definitions, the customer suspects that 9h should be:

9h = 64-bit square result

Could you please confirm whether this is correct?

Best regards,
Ibuki Endo

MSPM0L1117: Gang Programmer Issues with MSPM0L1117

Jacob Porter — Tue, 13 Oct 2026 21:11:17 GMT

Part Number: MSPM0L1117
Other Parts Discussed in Thread: C-GANG

I have been working on a project that incorporates the new MSPM0L1117, and we are rapidly approaching a trial build at our contract manufacturer.

However, as I have attempted to stand up my gang programmer, I have ran into some issues.

I have both the C-gang and S-Gang programmers, which claim to be compatible with the M0 family. In addition the S-Gang programmer is listed on TI as being compatible. (https://www.ti.com/tool/C-GANG?keyMatch=m0%20gang&tisearch=universal_search#supported-products)

However, I cannot find the MSPM0L1117 while setting up the device on the windows program.

I have tried the C-Gang Program, the MSP Gang Program and the GangPro-X program. None of these list the MSPM0L1117, but do list a significant amount of other MSPM0 MCUs

Is there something that I am missing, or is this MCU not actually compatible with these programmers?

GangPro-X

C-Gang Program (GangPro-ARM)

TI MSP Gang Program

MSP430F5172: MSP430F5172: ~3 mA supply current and VCORE = 2.05 V when powered up with RST/NMI held low (DVCC above ~2.62 V), reproduced on 2 devices

Mario Monti — Tue, 13 Oct 2026 16:46:18 GMT

Part Number: MSP430F5172

Ecco il testo completo, pronto da incollare.

**Titolo:**
```
MSP430F5172: ~3 mA supply current and VCORE = 2.05 V when powered up with RST/NMI held low (DVCC above ~2.62 V), reproduced on 2 devices
```

**Descrizione:**
```
Hello,

I am observing an undocumented behavior of the MSP430F5172 related to the power-up sequence with RST/NMI held low. The behavior is reproducible on two different devices. I would like to confirm whether it is known and whether it has reliability implications.

Part number: MSP430F5172IYFF

SETUP
- DVCC, AVCC and DVIO connected together to the same supply.
- VCORE capacitor: 470 nF.
- Total capacitance on the DVCC rail: 10 uF (1 uF + 2 x 100 nF close to the device, plus the buffer capacitor on the same rail). DVCC/VCORE capacitor ratio is about 21.
- RST/NMI held directly to GND, with no external pull-up.
- TEST pin pulled down with 100 kOhm. Debugger disconnected.
- All used I/Os have pull-ups to the same supply rail; 15 unused pins are left floating.
- No other loads on the measured rail.

OBSERVATIONS
Case A - Power applied with RST already held low (device never booted):
- DVCC <= 2.60 V: supply current ~0 mA.
- DVCC >= 2.65 V (tested up to 3.3 V): VCORE = 2.05 V, supply current ~3 mA (roughly constant).

Case B - Power applied with RST released, firmware starts normally:
- VCORE = 1.41 V (PMMCOREV = 0, as set by default), supply current as expected.

Case C - Same as case B (firmware first starts normally), then RST is pulled low without removing power:
- VCORE = 1.4 V, supply current as expected (no 3 mA), even at DVCC = 3.3 V.

KEY POINTS
1. The transition is sharp: about 0 mA at 2.60 V and about 3 mA at 2.65 V. Above the threshold the current stays roughly constant, so it looks like an internal block being switched on rather than a clamp.
2. The anomalous state (case A) appears only if the device has never completed a boot since power-up. Once it has booted at least once (case C), asserting RST does not reproduce the issue.
3. VCORE at 2.05 V is above every documented VCORE level (the maximum typical value is 1.94 V for PMMCOREV = 3 in low-current mode).
4. The behavior was reproduced with identical results on a second device.

I checked the device errata sheet and found no matching entry.

APPLICATION CONTEXT
The supply is current-limited to about 1 mA. RST is held low while the buffer capacitor charges, so that the firmware starts only when enough energy is stored. Because of this behavior, the 3 mA drawn in reset prevents the capacitor from charging above about 2.6 V.

QUESTIONS
1. Is this behavior known? Is it caused by PMM/VCORE trimming or configuration that is loaded only during the first boot after power-up?
2. Does keeping VCORE at about 2.05 V for extended periods (seconds to minutes) have any reliability implications for the device?
3. Is there a recommended way to hold the device in reset from power-up at a low supply current, or should the reset state be avoided in this scenario? We are considering booting immediately and waiting in LPM3 instead.

Thank you.

Mario Monti

MSP430FR6043: Query about captured ADC Waveforms

Analogics Rnd Solar — Tue, 13 Oct 2026 12:03:15 GMT

Part Number: MSP430FR6043

Hi Ti Team,
i hope your doing well,

We have captured the ADC waveforms for the DN15 PVC-type pipe using two spools. Could you please confirm whether the waveforms are correct?

According to ti documentation whether we captured waveform are considerable?

parameters are fallows

Advanced parameters

spool_1

spool_2

MSP430FR2433: MSP430FR2433: energy of one wake-up from power-off with one internal temperature sensor reading

Ibon Zalbide — Mon, 12 Oct 2026 19:15:21 GMT

Part Number: MSP430FR2433

Hello,

We are evaluating the MSP430FR2433 for a low-duty-cycle logger in which the MCU is completely unpowered between samples and is powered up every few minutes by an external RTC.

1) What is the typical energy of one complete cycle: supply ramp and power-on, BOR and boot to main(), one ADC conversion of the internal temperature sensor, and power-off? Is there an application note or a measured figure for this?

2) What accuracy can be expected from the internal temperature sensor without per-unit calibration (using only the TLV calibration data), and is there any data on its long-term drift?

Thank you.

MSPM0L1106: Irrugular Standby Current

Selvam Krishnan — Mon, 12 Oct 2026 06:40:04 GMT

Part Number: MSPM0L1106
Other Parts Discussed in Thread: TPS8804, SYSCONFIG

Good day TI Team,

Summary: While doing current analysis test with TI devices – TPS8804 and MSPM0L1106 before production,
We are facing irregular standby current.

Details:
Used Application Circuit Block:

Enclosed the used Code:
main_standbyTest.txt– main.c filemain_standbyTest.txt
smoke_detector.txt -- sysconfig filesmoke_detector.txt
Note: Please update extension accordingly

Expected:
We are expecting always 70uA as standby current, for every 5sec it is wakeup and current become 1.4mA.

Actual:
Initially we are getting properly , but after few minutes, the 70uA becomes 320uA for few minutes to around 10 mins
Then again comes to 70uA.
This happens at irregular interval.

Please guide us regarding what might be root cause and solution for this irregular standby current .

Thanks
Selvam

MSP430FR5043: Accuracy issue of d-tof period deviation caused by cycle slips in abs-tof

martin day — Mon, 12 Oct 2026 00:59:43 GMT

Part Number: MSP430FR5043

Dear TI Support Team,

I have a question regarding the cycle slip issue when using the MSP430FR5043 for ultrasonic water meter design. The LOBE algorithm is being used.

The transducer excitation frequency I am currently using is 1 MHz. Theoretically, a cycle slip should result in a deviation of one complete period, e.g., 1 µs. However, this is not the case in practice. The actual deviation is related to the selected waveform, the type of transducer, and even the flow rate.

I would like to know how this deviation is calculated in TI's algorithm. Please kindly help clarify.

Regards,
Martin Day

MSP-FET: CANNOT FIND MSP-FET

peter mccormick — Mon, 12 Oct 2026 00:34:02 GMT

Part Number: MSP-FET
Other Parts Discussed in Thread: MSP430FG4619,

We have a large installation of the older MSP430FG4619. We cannot find the MSP-FET but need to support our large existing base. Does anybody sell them? I cannot find them on Mouser, Digikey, Newark, TI....? thanks, peter

MSP-EXP430G2ET: MSP-EXP430G2 (OLDER REV 1.4 )

Nikhil . — Sun, 11 Oct 2026 15:16:34 GMT

Part Number: MSP-EXP430G2ET
Other Parts Discussed in Thread: MSP430G2452

Subject: MSP-EXP430G2 Rev 1.4 Not Detected by MSP430Flasher on HP Laptop

Dear TI Support Team,

I am using an MSP-EXP430G2 LaunchPad Rev 1.4 with an MSP430G2452 target on an HP 14S laptop running Windows.

The LaunchPad appears to be detected as HID0001:COM4, but MSP430Flasher v1.3.20 fails to initialize the debugger.

Command executed:
MSP430Flasher.exe -i DETECT

Error received:

Found USB FET @ HID0001
Initializing interface @ HID0001
Exit: 19
ERROR: Could not find MSP-FET430UIF on specified COM port

I would appreciate your guidance on the following:

Is this issue related to USB 3.0 compatibility or the Intel xHCI controller?
Is MSP430Flasher v1.3.20 compatible with MSP-EXP430G2 Rev 1.4?
Which driver or MSP Debug Stack version should I install to resolve this issue?

The COM4 interface is detected, but the debugger initialization fails.

Thank you for your support.

MSPM0L1306-Q1: MSPM0L1306 max output current VREF

Remy HOFF — Sat, 10 Oct 2026 15:54:00 GMT

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

Hi all,

i am designing a board with a MSPM0L1306.

I need to supply a wheastone bridge sensor with the VREF pin to allow a ratiometric measurement with the embeded GPAMP and ADC of the MSPM0.

I did not find the max output current on this pin.

VCC=2V about, VREF defined as 1.4V.

Thank you !

MSPM0G3107: MSPM0G3107 Application Runs Only During Debug Session

swaleha mulani — Fri, 09 Oct 2026 10:51:07 GMT

Part Number: MSPM0G3107

Hi,

We are observing an issue where CAN data is received when the debugger is connected, but after removing the debugger and power cycling the board, CAN data is not received.

PA18 is not used in our current application code. Could you please suggest the required configuration or changes to resolve this issue?

can rx tx.zip

MSP430FR6043: SPI miso pin noise occur

Analogics Rnd Solar — Tue, 06 Oct 2026 05:35:35 GMT

Part Number: MSP430FR6043

Hi TI team,
I hope your doing well,
I am facing an issue regarding the SPI MISO pin when i am trying to send the data from FR6043 when i check in Scope i am finding noise around MISO pin

currently, im working communicate with Lora module, that is SPI communication, i didnt get any issues in fr6047, the same configuration imported to fr6043 only the gpio pins are changed im unable get data from spi communication

i changed DCO clock to ,External crystal OSC so im getting clear wavewform of SCLK
The scope results are attached below

The above waveform of SCLK pin, here clear waveform obtained

when come to around MOSI pin im getting Noise, and SPI pin configured as secondary multi pin functionality,but im getting clearly in fr6047.

above image is MISO pin ,it looks like data is received but im not getting data in to variable
The UCA0RXBUF shows zero.
UCA0RXBUF shows default value : 0x005CC in ccs watch expression.

the above schematic as fallows, spi lines UCA0 module
and also tried, removed 200E resistors from spi lines & directly connected to lora but still im unable to communicate with lora.

the spi read code shows below,

// the SPI read code are fallow...

modem_e_modem_hal_read( const uint8_t* command,const uint8_t command_length, uint8_t* data,const uint8_t data_length )
{
if( modem_e_modem_hal_wakeup( ) == MODEM_E_MODEM_HAL_STATUS_OK )
{
uint8_t i;
uint8_t crc = 0;
uint8_t crc_received = 0;
modem_e_modem_hal_status_t status;

/* NSS low */

P2OUT &= ~BIT3;

/* Send CMD */
for( i = 0; i < command_length; i++ )
{
hal_spi_in_out(command[i] );
}
/* Compute and send CRC */
crc = modem_e_modem_compute_crc( 0xFF, command, command_length );

/* Send CRC */
hal_spi_in_out(crc );

/* NSS high */

P2OUT |= BIT3;

/* Wait on busy pin up to 1000 ms */
if( modem_e_modem_hal_wait_on_busy( 1000 ) != MODEM_E_MODEM_HAL_STATUS_OK )
{
return MODEM_E_MODEM_HAL_STATUS_BUSY_TIMEOUT;
}

/* Send dummy byte to retrieve RC & CRC */

/* NSS low */

P2OUT &= ~BIT3;

/* read RC */
status = ( modem_e_modem_hal_status_t ) hal_spi_in_out(0x00 );

if( status == MODEM_E_MODEM_HAL_STATUS_OK )
{
for( i = 0; i < data_length; i++ )
{
data[i] = hal_spi_in_out(0x00 );

}
}

crc_received = hal_spi_in_out(0x00 );

/* NSS high */

P2OUT |= BIT3;

/* Wait on busy pin up to 1000 ms */
if( modem_e_modem_hal_wait_on_unbusy( 1000 ) != MODEM_E_MODEM_HAL_STATUS_OK )
{
return MODEM_E_MODEM_HAL_STATUS_BUSY_TIMEOUT;
}

/* Compute response crc */
crc = modem_e_modem_compute_crc( 0xFF, ( uint8_t* ) &status, 1 );
if( status == MODEM_E_MODEM_HAL_STATUS_OK )
{
crc = modem_e_modem_compute_crc( crc, data, data_length );
}

if( crc != crc_received )
{
/* change the response code */
status = MODEM_E_MODEM_HAL_STATUS_BAD_FRAME;
}
return status;
}

return MODEM_E_MODEM_HAL_STATUS_BUSY_TIMEOUT;
}

//transmit and receive byte
uint8_t hal_spi_in_out(uint8_t out_data)
{

while (!(UCA0IFG & UCTXIFG));
UCA0TXBUF = out_data;

while (!(UCA0IFG & UCRXIFG));
return UCA0RXBUF;
}

thank you in adwance , please support us.
Best regards,
veeranna.

MSPM0L2117: CAD Symbol and Footprint Not Available in Ultra Librarian

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

Part Number: MSPM0L2117
Other Parts Discussed in Thread: MSPM0L2227

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
Other Parts Discussed in Thread: MSP430FR6047

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,

UNIFLASH: Consult UniFlash Using Method for Security Debug.

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

Part Number: UNIFLASH
Other Parts Discussed in Thread: MSPM0G3519

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
Other Parts Discussed in Thread: SYSCONFIG

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?