MSP430G2452: MSP430G2452 PROGRAMING ISSUE

Part Number: MSP430G2452
Other Parts Discussed in Thread: UNIFLASH

Subject: MSP430G2452 – MSP-EXP430G2 Rev 1.4 detected by Windows but not detected by MSP430 Flasher/UniFlash

Hello TI Support Team,

I am trying to program an MSP430G2452IRSA16 on my custom PCB using an MSP-EXP430G2 LaunchPad Rev 1.4 as the programmer/debugger.

I am using Windows 11 and CCS 21.0.1.

1. VS Code + MSP430 GCC

I installed the TI MSP430 GCC toolchain at:

C:\ti\msp430-gcc

The compiler is detected correctly using:

& "C:\ti\msp430-gcc\bin\msp430-elf-gcc.exe" --version

I also verified:

Test-Path "C:\ti\msp430-gcc\include\msp430.h"

Result:

TRUE

The MSP430G2452 linker script is also present:

C:\ti\msp430-gcc\include\msp430g2452.ld

My test program is:

#include <msp430.h>

int main(void)
{
    WDTCTL = WDTPW | WDTHOLD;

    while (1)
    {
    }

    return 0;
}

I successfully compiled it in VS Code using:

& "C:\ti\msp430-gcc\bin\msp430-elf-gcc.exe" -mmcu=msp430g2452 -Os -Wall -I"C:\ti\msp430-gcc\include" -L"C:\ti\msp430-gcc\include" -o build\G2452_Test.elf main.c

The ELF file is generated successfully:

build\G2452_Test.elf

So the VS Code/GCC build process is working correctly.

2. MSP430 Flasher

I installed MSP430 Flasher 1.3.20 at:

C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe

I ran:

& "C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe" -i DETECT

The result is:

Evaluating triggers...done
Executing FET detection sweep:
Exit: 19
ERROR: Could not find MSP-FET430UIF on specified COM port
Driver : closed (No error)

3. Windows Device Manager

Windows detects the LaunchPad USB device.

The LaunchPad appears as:

MSP430 Application UART (COM4)

I also checked the USB device IDs.

When the LaunchPad is connected, Windows reports:

VID_0451&PID_F432

The related devices include:

HID-compliant vendor-defined device
USB Composite Device
MSP430 Application UART (COM4)
USB Input Device

All of them show status:

OK

So Windows appears to enumerate the LaunchPad/eZ430 USB interface correctly.

4. CCS

In CCS, I created a target configuration:

Connection: TI MSP430 USB1
Device: MSP430G2452
Debug interface: SBW

When attempting to connect to the target, CCS reports:

Error connecting to the target:
Could not find device (or device not supported)

5. UniFlash

I also tested the same setup in UniFlash.

I selected:

Device: MSP430G2452
Connection: TI MSP430 USB1

UniFlash initially reports:

No debug probes/devices detected

I manually configured the device and connection.

I loaded:

G2452_Test.elf

The ELF file is accepted by UniFlash, but when I click Load Image, UniFlash reports:

Error initializing emulator:
Could not find MSP-FET430UIF on specified COM port

6. Hardware

Target MCU:

MSP430G2452IRSA16

I am using Spy-Bi-Wire:

RST/NMI/SBWTDIO -> MSP430G2452 pin 9
TEST/SBWTCK -> MSP430G2452 pin 10

Target supply is approximately 3.3 V.

The target has:

RST pull-up = 30 kOhm to +3V0
AVCC/DVCC powered
AVSS/DVSS connected to GND

My main question:

Since Windows detects the MSP-EXP430G2 Rev 1.4 / eZ430 interface with:

VID_0451&PID_F432

but MSP430 Flasher, CCS and UniFlash cannot communicate with the debugger, could you please advise:

1. Is the MSP-EXP430G2 Rev 1.4 eZ430 debugger supported with the current MSP430 Flasher/UniFlash/CCS versions?

2. Is there a specific legacy eZ430 driver/MSP Debug Stack version required?

3. Why does MSP430 Flasher report "Could not find MSP-FET430UIF on specified COM port" when the eZ430 interface is enumerated by Windows?

4. Is there any known compatibility issue between the legacy eZ430 interface and modern Windows 11 / USB 3.x?

5. Is there a recommended driver or software version for programming an MSP430G2452 using the MSP-EXP430G2 Rev 1.4?

I can provide screenshots, Device Manager information, CCS configuration, and the complete Flasher/UniFlash logs if required.
Please provide me step by step guide !IMG_29B2D044-F0D5-40A8-B473-29B6F104F753.jpeg

Thank you.

Best regards,
NIKHILScreenshot 2026-09-29 091632.png

  • I am seeing the same thing with the Linux version of MSPFlasher. On the other hand, mspdebug works:

    $mspdebug rf2500
    MSPDebug version 0.25 - debugging tool for MSP430 MCUs
    Copyright (C) 2009-2017 Daniel Beer <dlbeer@gmail.com>
    This is free software; see the source for copying conditions.  There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    Chip info database from MSP430.dll v3.13.0.601 Copyright (C) 2013 TI, Inc.
    
    Trying to open interface 1 on 005
    Initializing FET...
    FET protocol version is 30066536
    Set Vcc: 3000 mV
    Configured for Spy-Bi-Wire
    Device ID: 0x2553
      Code start address: 0xc000
      Code size         : 16384 byte = 16 kb
      RAM  start address: 0x200
      RAM  end   address: 0x3ff
      RAM  size         : 512 byte = 0 kb
    Device: MSP430G2xx3
    Number of breakpoints: 2
    fet: FET returned NAK
    warning: device does not support power profiling
    Chip ID data:
      ver_id:         5325
      ver_sub_id:     0000
      revision:       00
      fab:            60
      self:           0000
      config:         00
      fuses:          00
    Device: MSP430G2xx3
    
    

  • Hi David,

    Thank you for your reply.

    I am also facing a similar issue with MSP430Flasher on Windows 11 using an MSP-EXP430G2 LaunchPad Rev 1.4.

    Windows detects the LaunchPad/eZ430 interface as VID_0451&PID_F432, and the MSP430 Application UART appears as COM4. However, MSP430Flasher and UniFlash both give the following error:

    "Could not find MSP-FET430UIF on specified COM port"

    I noticed that you were able to successfully detect and initialize the FET using mspdebug:

    Initializing FET...
    FET protocol version 30066536
    Set Vcc: 3000 mV
    Configured for Spy-Bi-Wire
    Device ID: 0x2553
    Device: MSP430G2xx3

    Could you please explain how you detected the target using mspdebug?

    Specifically:

    1. Which exact mspdebug version did you use?
    2. What command did you run to detect/connect to the target?
    3. How did mspdebug find the FET/interface (for example, USB/HID or a specific port)?
    4. Did you use the MSP-EXP430G2 LaunchPad Rev 1.4/eZ430 interface?
    5. Were any additional drivers required?
    6. Is it possible to use the same mspdebug method on Windows 11?
    7. Does mspdebug support programming an MSP430G2452 through the MSP-EXP430G2 Rev 1.4?

    I am trying to determine whether my issue is with the MSP430Flasher/UniFlash software or with the debugger/interface connection.

    If possible, please share the exact command sequence you used to get the target detected.

    Thank you for your help.

  • The command I used is shown and mspdebug includes its version number in the output. I have an older version (1.3) of the G2 Launchpad.

    The problem with MSPFlasher is that it isn't finding the debugger. I tried it with a FR5969 Launchpad and it was happy with that.

    The mspdebug README says it works with Windows. I can't say if ir will work with Windows 11 as the last version I used was Win98.

**Attention** This is a public forum