MSP low-power microcontroller forum - Recent Threads

MSPM0L1105: The MCU system crashes abnormally

switch — Mon, 11 May 2026 13:02:28 GMT

Part Number: MSPM0L1105

Hi ti team,

We are developing a new project based on the MSPM0L1105 MCU. When using the UART peripheral for data reception, data reception abnormal error will occur once the received data length exceeds 32 bytes.

The on-chip Flash of MSPM0L1105 is 32KB in total, and we have partitioned it into three areas:

4KB for Bootloader area
14KB for APP application area
14KB for backup storage area

At present, the MCU system crashes abnormally when we perform Flash erase and program operations on the 14KB backup partition.

We would appreciate it if you could help analyze the possible root causes of the above two problems. Meanwhile, please kindly provide a reference sample code project for us to reproduce and verify the issu

MSP430FR5969-SP: MSP430FR5969-SP: Flight Heritage

Satomi Tanaka — Mon, 11 May 2026 08:47:52 GMT

Part Number: MSP430FR5969-SP

I'd like to follow up the questions asked about 3months ago, please kindly advise the result of your internal checking.

My last question was as below.

As to the flight heritage, can I confirm if there are flight heritage or not?

Also, it would be helpful if you could at least tell us what orbits or altitudes this part has heirtage with.

MSP430FR6047: MSP430FR6047 USS channels

Paolo Costantini — Wed, 06 May 2026 13:58:05 GMT

Part Number: MSP430FR6047

Good morning,

I have a question related to MSP430FR6047 ultrasonic front-end.

I see thath MSP430FR6047 provides 2 USS channels (CH0 and CH1) to connect piezoelectic sensors.

Ultrasonic sensor software library (ussSwLib) from TI provides the following different methods to use USS channels:

//! \brief This defines the capture sequence selection CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0 --> TX from CH0, RX on CH1

//! \brief This defines the capture sequence selection CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1 --> TX from CH1, RX on CH0

//! \brief This defines the capture sequence selection CH0_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH1 --> TX from CH0, RX on CH1, then TX from CH1, RX on CH0

and so on for the others:

//! \brief This defines the capture sequence selection CH1_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH0 3
//! \brief This defines the capture sequence selection CH0_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH0 4
//! \brief This defines the capture sequence selection CH1_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH1 5
//! \brief This defines the capture sequence selection CH0_CH1_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH1_CH0 6
//! \brief This defines the capture sequence selection CH1_CH0_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH0_CH1 7
//! \brief This defines the capture sequence selection CH0_CH0_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH0_CH0 8
//! \brief This defines the capture sequence selection CH1_CH1_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH1_CH1 9
//! \brief This defines the capture sequence selection CH0_CH1_CH0_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH1_CH0_CH1 10
//! \brief This defines the capture sequence selection CH1_CH0_CH1_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH0_CH1_CH0 11
//! \brief This defines the capture sequence selection CH0_CH0_CH0_CH0
#define USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH0_CH0_CH0 12
//! \brief This defines the capture sequence selection CH1_CH1_CH1_CH1
#define USS_CAPTURE_SEQUENCE_SELECTION_CH1_CH1_CH1_CH1 13

I want to transmit a signal from CH0 and receive an echo signal on the same CH0.

Is there a way to allow this scenario?

Thanks in advance, Paolo.

RE: MSP430FR6047: MSP430FR6047 USS channels

Paolo Costantini — Mon, 11 May 2026 07:59:53 GMT

Hi Peter, thanks for your support.

Unfortunately USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH0 configuration performs two sessions CH0 TX --> CH1 RX.

I need a single session CH0 TX --> CH0 RX

RE: MSP430FR2676: GANG with external power supply

Ryuuichi machida — Mon, 11 May 2026 04:12:43 GMT

Hi Brian-san,

>There has unfortunately been another stall in this. I do not have a firm date, but expect to have more updates on this matter later this week.
Today, I confirmed Elpro's newer GANGPRO-X(Ver3.02) is released. However, as I said previously, I could not request newer adapter's software due to difference digit of serial number (It seems that Elpro's adapter is 8 digit for SN, but TI's adapter is 9 digit for SN. I can only enter up to 8 digit to Elpro's software update page as shown below.

Could you continue to confirm how I can request newer adapter's software which user can use Elpro GUI with TI's C-GANG to Elpro ?

Best Regards,

MSP430FR2676: GANG with external power supply

Ryuuichi machida — Fri, 12 Dec 2025 08:26:24 GMT

Part Number: MSP430FR2676

Hi,

I would like you to confirm you have ever used C-GANG with external power supply use case.
According to datasheet of MSP430FR2676, there is following figure and information.

”In addition, the MSP-FET and MSPFET430UIF interface modules and MSP-GANG have a VCC sense feature that, if used, requires an alternate connection (pin 4 instead of pin 2). The VCC sense feature detects the local VCC present on the target board (that is, a battery or other local power supply) and adjusts the output signals accordingly”

I understand that user can choose both internal power supply (use pin2) and external power supply (use pin4) from above for MSP-GANG.
However, I'm not sure we can use same configuration for C-GANG which TI currently recommend.

Background of this question is below.
* In case of C-GANG, Customer have problem related to JTAG and SBW access on MSP430FR2676(
use "CAPTIVATE-FR2676") when they use external power supply use case.
(They do not observe same problem when they use MSP-GANG.)

Since we can not find similar figure/information to above, so could you comment whether you have ever evaluated "external power supply + C-GANG" use case or not ?

Best Regards,

MSPM0G3519: noinit section with Clang compiler and also with GHS compiler

Lokesh Uppara — Wed, 06 May 2026 01:23:41 GMT

Part Number: MSPM0G3519

I am trying to use a NOINIT section, but the structure variable is not retained after a reset.

Could you please provide a detailed example of the required linker configuration and C code/memmap file changes for both Clang and GHS compilers?

Test Environment :

Target : TI(MSPM0G3519)
Currently:
- Compiler : Clang (ticgt) (400_LTS)
- MCAL : MSPM0-MCAL_0.2.5.0
Planned:
- Compiler : GHS multi (202414)
- MCAL : MSPM0-MCAL_00_09.00.00

RE: MSPM0G3519: noinit section with Clang compiler and also with GHS compiler

Helic Chi — Mon, 11 May 2026 04:00:47 GMT

As my mentions above, MCU_PERFORM_RESET_MODE_BOOTRST will reset the SRAM.

Choose SYSRST which won't reset the SRAM.

RE: MSPM0G3519: noinit section with Clang compiler and also with GHS compiler

Lokesh Uppara — Sun, 10 May 2026 17:32:28 GMT

I tried using MCU_PERFORM_RESET_MODE_BOOTRST, but after reset the SRAM is still cleared and execution does not jump to the expected reset location.

Only MCU_PERFORM_RESET_UNDEFINED is working as expected; however, SRAM is also cleared when this reset is performed.

Could you please help me with examples demonstrating the correct usage of a no‑init section to retain SRAM contents across reset?

RE: MSP430FR6047: MSP430FR6047 USS channels

Peter Jiang — Sun, 10 May 2026 12:51:45 GMT

Hi Paolo,

I believe it is achievable, you can find below comments in the "USS_userConfig.h" of the demo code project, there are only 6 options that can be chosen, please try "USS_CAPTURE_SEQUENCE_SELECTION_CH0_CH0" to see if it can achieve your requirements.

Best Regards,
Peter

RE: MSP430F6775A: Does C-GANG come with a usage quota??

Nikolay Novakov — Sat, 09 May 2026 07:40:52 GMT

Is there some update when the updated version for C-GANG-TI will become available?

Best regards,

Nikolay

MSP430F6775A: Does C-GANG come with a usage quota??

MF — Tue, 07 Apr 2026 20:34:44 GMT

Part Number: MSP430F6775A

Hello,

We previously used MSP-GANG in our production process.

Since Texas Instruments introduced a new version of the gang programmer, we decided to purchase one from the following link:
https://www.ti.com/tool/C-GANG

After acquiring this programmer, we would like to clarify whether there is any limitation on its lifetime usage. For example, is there a maximum number of programming cycles (such as 500 uses)?

If such a limitation exists, it would be quite unfortunate for us because:

There is no clear indication of this restriction in the available documentation.
We purchase the hardware outright, as we did with MSP-GANG, so it is unclear why the number of uses should be restricted. This is not a printer that depends on consumables like toner. (here)

We would appreciate your clarification on this matter.

Thank you.

MSP-EXP430G2ET: SO#536488 / MSP-EXP430G2ET saying "MSP-FET / eZ-FET recovery failed" error

Manuel Rosario — Fri, 08 May 2026 08:31:06 GMT

Part Number: MSP-EXP430G2ET

Dear Technical Support,
Please verify for MSP-EXP430G2ET and provide guidance for proper operation.
Or confirm if can be considered as defective ?

      CUSTOMER INFORMED US THAT THE ITEM IS NOT WORKIN CORRECTLLY AND ITS DEFECT.
After purchasing it, I connected to PC to use it,but an error message
      saying "MSP-FET / eZ-FET recovery failed" appeared, and I was unable to
      get it to be recognized or work properly."

      [Connection Method] I am connecting the device directly to my PC using the
      USB cable that came with the product.
      [OS] Windows 11

      COULD YOU PLEASE ADVISE POSSIBLE CAUSE OF THIS? THANKS

Regards,
Manuel

RE: MSP-EXP430G2ET: SO#536488 / MSP-EXP430G2ET saying "MSP-FET / eZ-FET recovery failed" error

Helic Chi — Sat, 09 May 2026 05:17:50 GMT

Many reason that will cause FET update failed.

But still can try to run a cold boot of FET.

Try to debug it with https://www.ti.com/lit/ug/slau647o/slau647o.pdf

5.6.4 LED Signals

5.6.5.3 MSP-FET HID Cold Boot

RE: MSP430F6433: Power for oscillator

user5945607 — Sat, 09 May 2026 02:47:26 GMT

Dear Diego
Thank you for your reply.

In fact, the crystal’s GND is connected to the 26-pin DVss1, even though there is some physical distance between them.

I have one more question.

AVCC1-AVSS1 (pins 11-12) and AVSS2 (pin 15) are located next to Xin-Xout (pins 13-14).

Just to confirm, is it correct that the crystal’s GND connected to Xin-Xout must not be connected to AVSS (pin 12 or 15)?

Thanks and best regards.

Yu Takehara

MSP430F6433: Power for oscillator

Danilo A. — Mon, 04 May 2026 19:08:33 GMT

Part Number: MSP430F6433

Hi Team,

Posting on behalf of our customer.

I'll share this E2E post with our customer so he can reply when needed.

We assemble MSPF430F6433 to our product.

I would like to make sure whether our design is correct or not.

Where does the power for Xin come from? Vasys is correct?

In other words, since the MSP430F6433 treats the oscillator circuit as an analog circuit, I’d like to know if it’s correct to connect it to the analog power supply and analog GND.

The following is an excerpt from Section 2.1 on page 99 of the link below, which states as follows:

"The PMM uses an integrated low-dropout voltage regulator (LDO) to produce a secondary core voltage (VCORE) from the primary one applied to the device (DVCC). In general, VCORE supplies the CPU, memories (flash and RAM), and the digital modules, while DVCC supplies the I/Os and all analog modules (including the oscillators). "

The following is an excerpt from Section 4.2 on page 134 of the link below, which states as follows:

"The analog modules of the device are supplied by the internal analog system voltage VASYS. The AUX module switches VASYS among the AVCC, AUXVCC1, and AUXVCC2 inputs. VASYS is also output on the VASYS pin, which must be connected to an external capacitor as specified in the device-specific data sheet."

www.ti.com/.../slau208q.pdf

Regards,

Danilo

MSPM0-SDK: Sysconfig issue in switching the device

Yesol Lee — Thu, 30 Apr 2026 08:52:47 GMT

Part Number: MSPM0-SDK

Customer is using MSPM0L2228 EVM board before, and now they're trying to test with M0L1227-Q1 64pin sample on their board.

But this message poped up when they switch the device to M0L1227-Q1 (64pin) from M0L2228-Q1 (80pin) in CCS.

Could you please help to figure out why this is happened and how we could fix this?

RE: MSPM0-SDK: Sysconfig issue in switching the device

Ki — Fri, 08 May 2026 21:13:02 GMT

Yesol,

Is the customer machine off-line (not on the internet)? If so, then they may be running into this known issue:

https://sir.ext.ti.com/jira/browse/EXT_EP-13369

Thanks

RE: MSPM0-SDK: Sysconfig issue in switching the device

Owen Li — Fri, 08 May 2026 19:52:22 GMT

Hi Yesol,

Looping in software tools team to see if they can comment on the compatibility.

Best,

Owen

RE: MSP430F5438: General debug support for MSP-Based Microcontrollers.

zrno soli — Fri, 08 May 2026 19:17:59 GMT

For "debug interface" can be used SBW. I am not 100% sure about non A 5438 (don't remember right now), but 5438A is with JTAG mailbox system, where JTAG master (over 2 wire SBW) can exchange data with free running (JTAG released) slave (5438). If you are not thinking on source code break point debugging.

MSP430F5438: General debug support for MSP-Based Microcontrollers.

Francisco Becerra — Mon, 04 May 2026 16:21:39 GMT

Part Number: MSP430F5438

Hi TI team,

Today we're contacting you asking for general debug support to understand which debug interface would be more suitable for our specific projects.

We would like to connect and review the most appropiate solutions to perform debug and failure analysis for the different TI MCUs we use in our products. This include Software and the Hardware interface. (DRV91670 & DRV91690 MCUs)

Best regards,

Francisco.

MSPM0G3519: MSPM0G3519: Inconsistent Reset Behavior (Software POR and Watchdog)

DavidV — Wed, 22 Apr 2026 14:49:12 GMT

Part Number: MSPM0G3519

A software-triggered POR reset is required in my application to perform a firmware update, however when the software POR is triggered the board does not restart.

I also tested using the watchdog to force a reset, but the behavior is the same: the device remains locked and only recovers after a full power cycle.

When the board is in this locked state, connecting a debugger shows that the call stack points to an address in the 0x100000xx range.

The system is using a high‑frequency external clock. Could this clock configuration affect the watchdog or software POR reset behavior?

RE: MSPM0G3519: MSPM0G3519: Inconsistent Reset Behavior (Software POR and Watchdog)

DavidV — Fri, 08 May 2026 15:55:28 GMT

Hi,

thank you for your help and suggestions.

I investigated other possible causes and found that the debug issue appears to be related to the Free Run Mode option enabled in the watchdog configuration when the NONMAIN region is enabled. After disabling the watchdog Free Run Mode, while keeping NONMAIN enabled and BSL disabled, both POR and watchdog resets work correctly, and I am able to debug normally by loading the symbols.

Best regards,

David

MSPM0G3519: Dio write channel functionality is not working.

Veeresh Kariyappa — Fri, 08 May 2026 06:12:12 GMT

Part Number: MSPM0G3519

Issue Description:

While performing Dio_WriteChannel() using latest MCAL package from TI. Below are the observations

Used the Dio demo provided as input for code and configuration.

Invokded Dio_WriteChannel(39, STD_HIGH); for PortConf_PortPin_PortPin_7(41) and channel 39.

It is noticed that Dio is not setting DOUTSET31_0 for the bit value 1 passed for the DIO7. This will result in not setting DIO7 in DOUT31_0 FOR GPIOB. Please find the attached screen shot below.

Is MCAL verified with GHS compiler at TI for Dio write channel for GPIOB ? and

Can you please share the Dio write channel for GPIOB information performed at TI ?

Test Environment :

Target : TI(MSPM0G3519)
Compiler : GHS multi (202414)
MCAL : MSPM0-MCAL_00_09.00.00

RE: MSPM0G3519: Dio write channel functionality is not working.

Helic Chi — Fri, 08 May 2026 08:30:45 GMT

[quote userid="697922" url="~/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1643762/mspm0g3519-dio-write-channel-functionality-is-not-working"]It is noticed that Dio is not setting DOUTSET31_0 for the bit value 1 passed for the DIO7. This will result in not setting DIO7 in DOUT31_0 FOR GPIOB. Please find the attached screen shot below.[/quote]

DOUTSET31_0 is write only register, no read permission. You can't use this register to read the pin status.

[quote userid="697922" url="~/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1643762/mspm0g3519-dio-write-channel-functionality-is-not-working"]Is MCAL verified with GHS compiler at TI for Dio write channel for GPIOB ?[/quote]

Original plan is, pass all the example test code.

[quote userid="697922" url="~/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1643762/mspm0g3519-dio-write-channel-functionality-is-not-working"]Can you please share the Dio write channel for GPIOB information performed at TI ?[/quote]

Directly control the port should be OK, and if you can confirm the left side window in your screenshot that, you write bit 1 in DIO7 bit in DOUTSET31_0, and your port configuration is correct, there is no reason that PB7 is still 0.