MSP low-power microcontroller forum - Recent Threads

MSP430FR5969: Internal Temperature Sensor Always Reads 0x0FFF

John Sullivan — Fri, 26 Jun 2026 23:35:28 GMT

Part Number: MSP430FR5969

I am working on a program that requires reading the internal temperature sensor of the MSP430. Development was done on the MSP430FR5969 Launchpad, and now on a custom-built dev board, but I'm having issues reading the temperature sensor on the custom board.

Everything works as expected on the launchpad and on the custom board except for the temp sensor. This includes multiple other ADC readings that have no issues. After every reading, the temp sensor value obtained from ADC memory is 0xFFF. I've tried many different configurations, all with the same result. I tried using the TI temp sensor example program also, and it works OK on the launchpad but has the same issue on the custom board.

The only notable hardware differences on the custom board are:

An external 2.5V reference connected to P1.0 and P1.1
An external HFXT 16MHz oscillator

This is the example code I used to troubleshoot the issue: tlv_ex3_calibrateTempSensor.c

To try and resolve the issue, and to account for the hardware differences, I tried the following things:

Configured P1.0 and P1.1 for Vref input function
Tried with and without the MCLK configured for external HFXT oscillator
While debugging, I ensured ADC12TCMAP bit is 1, ADC12INCH is set to internal channel 30 (temp sensor channel), REFTCOFF & REFOUT bits are 0
Changed the ADC sampling timer to ensure sampling time is >30us
Tried using avcc, internal, internal buffered, and external for the ADC reference voltage source
Reworked the custom board with a new msp430fr5969 chip

Nothing that I tried had any effect on the temp sensor. The 'temp' variable in the example always had the value 0xFFF. Additionally, many of those exact same tests worked as expected on the launchpad.

I would love to hear if I am missing something in the software, or if there is some type of hardware configuration that would cause an issue like this.

RE: MSP430FR5969: Internal Temperature Sensor Always Reads 0x0FFF

David Schultz — Sat, 27 Jun 2026 10:40:32 GMT

You say "the only notable differences" but since the code works on the launchpad but fails on your board, it is likely that you missed something. What that is I can't say because I don't have your schematic

MSP-FET: MSP430-Flasher compatibility with Windows 11

Melissa Mitrevski — Wed, 24 Jun 2026 06:13:38 GMT

Part Number: MSP-FET

Hello,

I would like to confirm whether the MSP430-Flasher (MSP430-FLASHER command line tool) is officially supported on Windows 11. The latest user guide I am referencing is SLAU654E (Revised February 2019), which lists support up to Windows 10. I would like to know:

Is MSP430-Flasher compatible with Windows 11?
Are there any known limitations or required workarounds?

Is there an updated version of the tool or documentation that includes Windows 11 support?

Kind Regards,

MSP Flasher User Guide version E.pdf

RE: MSP-FET: MSP430-Flasher compatibility with Windows 11

zrno soli — Sat, 27 Jun 2026 08:30:24 GMT

All TI msp430 software tools are based on open source "msp430.dll" including open source MSP430-Flasher. If last official version of MSP430-Flasher as it is, working fine on your Win 11, try to replace "msp430.dll" from MSP430-Flasher with last available "msp430.dll" revision, and if it is working fine, in that case MSP430-Flasher is up to date.

MSP430F5342: Cold temp high power consumption issue

Ryuuichi machida — Tue, 23 Jun 2026 11:39:11 GMT

Part Number: MSP430F5342

Hi,

My customer have high power consuption issue with MSP430F5342 when only powering up.
When I brouse E2E, I found similar thread.

(+) MSP430F534x - current consumption LPM3 at -40°C - MSP low-power microcontroller forum - MSP low-power microcontrollers - TI E2E support forums

This thread was posted 13 years ago, however could you please tell me this is known issue ?
(I could not find related issue in latest errata..)

Best Regards,

RE: MSP430F5342: Cold temp high power consumption issue

Ryuuichi machida — Sat, 27 Jun 2026 06:05:26 GMT

Hi,

If it is better to talk this internally, since I sent "friendship request" to you, let's talk internally.
Please give your opinion about this.

Best Regards,

LP-MSPM0G3507: Unable to use EnergyTrace with onboard XDS110

Eching Cheung — Wed, 24 Jun 2026 07:00:22 GMT

Part Number: LP-MSPM0G3507

Hi, I got a brand new LP-MSPM0G3507 (Rev A) development board and tried to program and debug some example code. Worked fine.

However, I am facing some problems when trying to use the onboard EnergyTrace function.

When I test it with the CCS 12.8 standalone EnergyTrace tool, it shows

"Error communicating with XDS110"

Another question: Why EnergyTrace unavailable in debug mode on CCS 12.8?

When I test it with CCS 21, I am able to open the EnergyTrace tab and no error shows up.

However, I start the project, it shows "Collecting data -> Data capture complete" within a second, but nothing appears on the graph.

What I have done so far:

Changed the USB cable and USB port.
Updated the development board firmware using CCS.

RE: LP-MSPM0G3507: Unable to use EnergyTrace with onboard XDS110

Eching Cheung — Sat, 27 Jun 2026 04:21:18 GMT

Yes, it said server health if I pointed to the "tick icon" but data is empty.

RE: LP-MSPM0G3507: Unable to use EnergyTrace with onboard XDS110

Ki — Fri, 26 Jun 2026 20:55:23 GMT

Can you check that the Trace Server is running and active? You can check the Trace Server status by checking the icon for it:

https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-trace.html#trace-view

RE: MSP430F6779A: Flash write (segment erase+program with interrupts disabled) degrades EM Software Library energy accuracy — clean when the write is removed

Bill Tang — Fri, 26 Jun 2026 20:01:31 GMT

Hi Rahul,

Our expert still working on this request please give him some time to investigate.

Best regards,

Bill

MSP430F6779A: Flash write (segment erase+program with interrupts disabled) degrades EM Software Library energy accuracy — clean when the write is removed

Jitain Sangwan — Tue, 23 Jun 2026 12:12:39 GMT

Part Number: MSP430F6779A

Device / SW: MSP430F6736A, SD24_B front end, MSP430 Energy Measurement (EM) Software Library (EVM430-F6736 / Energy Measurement Design Center). EM_SAMPLING_FREQ_HZ = 4096, mainNomFreq = 60, 60 Hz mains. SD24 ISR calls EM_perSampleProc; foreground EM_foregroundProc updates activeEnergy.

What we're doing: Periodically we persist energy/calibration data to main flash. Our routine disables global interrupts, erases one flash segment, programs it, then re-enables interrupts:

uint16_t ui16GIE = __get_SR_register() & GIE;
__bic_SR_register(GIE);
__disable_interrupt();

FCTL3 = FWKEY;
FCTL1 = FWKEY | ERASE;
*(uint8_t *)addr = 0;          // dummy write -> segment erase
FCTL1 = FWKEY | WRT;
memcpy(addr, &data, sizeof(data));   // program
FCTL1 = FWKEY;
FCTL3 = FWKEY | LOCK;

__bis_SR_register(ui16GIE);
__enable_interrupt();

On top of this, the same save also writes a backup copy to a second flash segment (flash_copy_primary_to_backup()) — another interrupt-disabled erase+program of the same form, run back-to-back with the primary. So a single save does two segment erase/program cycles, each with interrupts off.

Each erase+program takes ~60–65 ms with interrupts disabled, and the backup roughly doubles the total interrupt-off time, so the SD24_B sampling ISR (and therefore EM_perSampleProc) cannot run for that entire window.

Symptom: When this flash write runs anywhere near an active/just-finished metering session, our per-session energy total becomes inaccurate and non-repeatable (intermittent ~1 Wh / ~1% errors on a ~100 Wh session at ~5 kW). As soon as we comment out this flash write (user_flash_update(1)), the energy results become accurate and reproducible (error tightens to roughly ±0.15%). So the flash operation itself is clearly disturbing the metering.

Questions for TI:

What is the recommended way to write MSP430 flash on this part without disrupting the EM library's continuous SD24 sampling? During a flash erase/program with interrupts disabled, samples are necessarily missed — is there a supported approach (run the flash routine and/or ISR from RAM, keep the SD24 ISR serviced, minimize the interrupt-off window, etc.)?
After an unavoidable sampling gap (interrupts off for ~60 ms, ~120 ms with the backup), does the EM library recover on its own, or is there state (DC estimators, per-sample/per-chunk accumulators, ping/pong buffers) that gets left inconsistent and needs to be handled? Is there a recommended re-sync that does not require a full EMLibGUIApp_Init() (which forces a settling transient)?
Is there a TI-recommended pattern for persisting energy counters to flash in a continuously-running metering application (e.g., only write when no sampling is in progress, double-buffered segments, write timing relative to the measurement window)?

MSP430F2013: Need assistance regarding selection of capacitor

Raghul A — Mon, 22 Jun 2026 07:56:53 GMT

Part Number: MSP430F2013

Hi. We are using MSP430F2013 in our project as MCU. We are using the Internal ADC in the MCU and communicate with I2C communication. We have connected the 3x RTD (10K each) circuit for monitoring temperature signal as shown in the below image. The RTDs are assembled in a separate board and the RTD inputs are given to the MCU (Differential inputs) through a connector assembly.

We need to know the approach on how to select the capacitors C52, C53 and C54 without affecting the rise time of the ADC.

We went through the User Guide in the product page and found a circuit for the internal ADC with two Rs (Source Resistance). In our case, we have one 10K RTD resistor for the differential input. Should we consider Rs as 5K or 10K with reference to the User Guide ADC circuit. Kindly help us with this I have added the User Guide circuit image too for your reference. Kindly help us with this. Thank you!

RE: MSP430F2013: Need assistance regarding selection of capacitor

Keith Barkley — Fri, 26 Jun 2026 19:54:26 GMT

Make sure that IN1 does not go above 3.6 V, while the inputs are differential, they are still limited by the ESD diodes.

RE: MSP430F6778A: After clearing the JTAG signature at 0x17FC via BSL, what is required to re-enable JTAG?

Brian Lee — Fri, 26 Jun 2026 18:31:18 GMT

Hi MF,

I believe it should be possible in the unlock direction using the JTAG Mailbox (JMB) System described in section 1.12 of the MSP430x5xx and MSP430x6xx Family User's Guide.

Best Regards,
Brian

MSP430F6778A: After clearing the JTAG signature at 0x17FC via BSL, what is required to re-enable JTAG?

MF — Sat, 20 Jun 2026 11:48:36 GMT

Part Number: MSP430F6778A

Hello,

I have an MSP430F6778A whose JTAG is locked by the electronic fuse (the JTAG signature at 0x17FC–0x17FF holds a non-zero, non-0xFFFFFFFF value). JTAG access is blocked, so I am using the BSL to recover the device.

Over BSL I clear the lock as follows:
1. Clear the BSL read/program protection (write 0x0003 to SYSBSLC @ 0x0182 to clear SYSBSLPE).
2. Write 0x00000000 to the JTAG signature @ 0x17FC (4 bytes).

My question is about what happens after that write. To make the cleared signature take effect and have JTAG become active again, what exactly is required?

- A full power cycle (VCC off → on / BOR)?
- A hardware reset via the RST/NMI pin?
- Is the BSL "reset/reboot" command (the BSL's own software reset that exits BSL and starts the application) sufficient?
- Or does the device re-evaluate the JTAG fuse only on a specific reset class (POR vs BOR vs PUC)?

In other words: at which reset level does the F677x family re-read the 0x17FC signature to decide whether JTAG is enabled? I want to know the minimum, reliable action so I can re-enter JTAG immediately after the BSL unlock without an external power cycle if possible.

The device is self-powered in my setup (the programmer does not drive VCC), so I would prefer a method that does not require toggling the supply, if one is sufficient.

Thank you.

MSP-EXP432E401Y: DAC53608EVM programming for Waveform Generation with MSP-EXP432E401Y Launchpad

Chandan Thakur — Fri, 26 Jun 2026 05:00:47 GMT

Part Number: MSP-EXP432E401Y

I have the following modules: DAC53608EVM, BOOSTXL-DAC-PORT & MSP-EXP432E401Y Launchpad.
My aim is to generate a sine/distorted sine wave using DAC outputs. For the same I tried 2 methods:

1. Using TI GUI , there is a scripting feature where I wrote a block code first to write the 8 DAC outputs, however I received a prompt that for using scripting feature "SharedArrayBuffer" needed to be enabled in the Chrome browser. I tried although, I found in newer versions of chrome this feature is discarded, thus I am stuck with the same.
2. The other method I tried was using Code Composer Studio (CCS) to write the DAC outputs , however, I2C is seem to be non communicating. I checked through oscilloscope on the SCL & SDA pins, the pins are pulled high at 3.3V but no pulses, thus I am unable to write the DAC outputs.

Kindly help me with either way, so that I can program DAC outputs to generate a Sine or distorted Sine wave. Also, if there is a way to upload a csv or hex file to achieve the same, then let me know.

Thanks and regards
Chandan

RE: MSP-EXP432E401Y: DAC53608EVM programming for Waveform Generation with MSP-EXP432E401Y Launchpad

Eric Rentschler — Fri, 26 Jun 2026 14:08:58 GMT

Hi Chandan,

I am not sure why your TI GUI isn't working, but for the CCS solution, please ensure you are enabling the I2C interrupt using the IntEnable(INT_I2Cx) function.

Thanks,

-Eric Rentschler

RE: MSP-FET: MSP430-Flasher compatibility with Windows 11

Sal Ye — Fri, 26 Jun 2026 12:11:55 GMT

Hi,

We are not maintaining the MSP430-Flasher update anymore (last version is registered in 2019)

I suggest you can try whether it works in win11 OS with current released version.

B.R.

Sal

RE: MSPM0C1103-Q1: Shared pin for NRST

Keith Barkley — Fri, 26 Jun 2026 12:07:23 GMT

This is from the TRM:

MSPM0C1103-Q1: Shared pin for NRST

Yesol Lee — Fri, 26 Jun 2026 09:05:11 GMT

Part Number: MSPM0C1103-Q1

Hi team,

Customer is using 8-pin MSPM0C1103-Q1 for I2C.

And since the lack of pins, they're using NRST pin as SCL.

I guess it's going to be a problem due to not using reset, I would like to know if there's a workaround for pin multiplexing for reset and SCL.

Do you have any use-case for this?

RE: MSPM0C1106-Q1: Secure Boot Timing

Sal Ye — Fri, 26 Jun 2026 11:49:01 GMT

Hi Daviel,

You can idenrify the startup time in datasheet:

B.R.

Sal

MSPM0C1106-Q1: Secure Boot Timing

Daviel Almonte — Thu, 25 Jun 2026 20:12:08 GMT

Part Number: MSPM0C1106-Q1

Hello,

My customer needs to boot a camera using the MSPM0C1106 MCU under 2 seconds. I do beleave that we can achive this, but I couldn't find the bootiming for this device.

what is the typical boot time for this device using secure boot.

Regards,

Daviel

RE: MSP430F2013: Need assistance regarding selection of capacitor

Sal Ye — Fri, 26 Jun 2026 06:41:02 GMT

Hi Raghul,

From the circuit you shared, it looks like the input signa (SIGNAL1) are divided by (R34-RTD1-RTD2-RTD3-R35). So the effectively resistance is not the same as RTDx.

Additionally, we give the calculation formula on UG to make sure ADC can get idea input signal:

You have added the external C to reduce the Rs impact, while two things need to be taken into account:

1. capacitor should use low-voltage-factor one, which providing stable ability across the different voltages

2. Need analyze the impact of C for the signal input

B.R.

Sal

RE: MSP430F2013: Need assistance regarding selection of capacitor

Raghul A — Fri, 26 Jun 2026 05:56:20 GMT

Hi. Can you please give any available information regarding this query as it a critical component in our project.

RE: LP-MSPM0G3507: Unable to use EnergyTrace with onboard XDS110

Eching Cheung — Fri, 26 Jun 2026 01:53:30 GMT

I have tried cleaning workspace, setting up a new one, and even completely reinstalling CCS, but none of these solve problem.

Here is the screenshot of ccs 21.

For sure, I have run and reset the project many times and return same result.

it show : "Collecting data -> Data capture complete" instantly then a empty graph.