• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 79 subscribers
  • Views 2648 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

using MSP430Flasher to program my LaunchPad MSP430G2553

Taoufik Dachraoui
Prodigy 40 points
Other Parts Discussed in Thread: MSP430F149, MSP430G2553, ENERGIA, MSP-FET, MSP-EXP430FR6989

Dear,

I am trying without success to program LaunchPad MSP430G2 using MSP430Flasher

I could program MSP430F149 using MSP FET Emulator and MSP430Flasher, but when I connect

the LaunchPad MSP430G2 the MSP430Flasher does not find the connected device

I am using the following Makefile:

OBJECTS=blink.o

GCC_DIR =  ../../../bin

SUPPORT_FILE_DIRECTORY = ../../../include

DEVICE  = msp430g2553

CC      = $(GCC_DIR)/msp430-elf-gcc

GDB     = $(GCC_DIR)/msp430-elf-gdb

OBJCPY = $(GCC_DIR)/msp430-elf-objcopy

LOAD = MSP430Flasher -i /dev/tty.uart-D5FF5184AB90253B

CFLAGS = -I $(SUPPORT_FILE_DIRECTORY) -mmcu=$(DEVICE) -O2 -g

LFLAGS = -L $(SUPPORT_FILE_DIRECTORY)

all: ${OBJECTS}

$(CC) $(CFLAGS) $(LFLAGS) $? -o $(DEVICE).out

$(OBJCPY) -O ihex $(DEVICE).out $(DEVICE).hex

load: all

$(LOAD) -z [VCC,RESET] -w $(DEVICE).hex

debug: all

$(GDB) $(DEVICE).out

I get the following:

fetchoo:msp430g2553 mazeboard$ make load

../../../bin/msp430-elf-gcc -I ../../../include -mmcu=msp430g2553 -O2 -g -L ../../../include blink.o -o msp430g2553.out

../../../bin/msp430-elf-objcopy -O ihex msp430g2553.out msp430g2553.hex

MSP430Flasher -i /dev/tty.uart-D5FF5184AB90253B -z [VCC,RESET] -w msp430g2553.hex

* -----/|-------------------------------------------------------------------- *

*     / |__                                                                   *

*    /_   /   MSP430 Flasher v1.3.7                                           *

*      | /                                                                    *

* -----|/-------------------------------------------------------------------- *

*

* Evaluating triggers...

* Invalid argument for -i trigger. Default used (USB).

* Checking for available FET debuggers: 

* Couldn't find any connected USB FETs!

* Resetting device (RST/NMI)...done

* Starting target code execution...done

* Resetting device (RST/NMI)...done

* Starting target code execution...done

* Resetting device (RST/NMI)...done

* Starting target code execution...done

* Resetting device (RST/NMI)...done

* Starting target code execution...done

* Resetting device (RST/NMI)...done

PS: I can program LaunchPad MSP430G2 using Energia (so Energia finds the device,

but MSP430Flasher fails to do so)

Kind regards

Taoufik

  • 0
    Prodigy 40 points
    Just to mention that I am using MAC OS X and MSPGCC OPENSOURCE (from TI)
  • 0 in reply to Taoufik Dachraoui
    TI__Guru 56685 points
    Taoufik,

    Have you attempted to use -i DETECT to see if MSP430FLASHEr can find your FET?

    Regards,
    JH
  • 0 in reply to Jace H
    Prodigy 40 points

    Hi Jace

    Yes I tried with -i DECTECT but without success

    MSP430Flasher detects the MSP-EXP430FR6989 (eZ-FET emulatior onboard) and MSP-TS430PM64 (connected using an MSP-FET flash emulator)

    but does not detect the MSP-EXP430G2 (with MSP430G2553 mcu)

    Note that Energia could detect and program the MSP-EXP430G2

    I would like to use MSPGCC to program so it is important that the MSP430Flasher detects all the boards I am using

    Is there any configuration for the MSP-EXP430G2 so that MSP430Flasher detects it?

    Kind regards

    Taoufik

  • 0 in reply to Taoufik Dachraoui
    TI__Guru 56685 points
    Taoufik,

    I am unsure of the issue here. I have reached out to my contact on the Tools team that is more familiar with the MSP430Flasher SW than I am. Unfortunately, they are unavailable until next week. In the mean time, can you get CCS Cloud to find and program your device? ( www.dev.ti.com )
    This will make sure that the programming HW on the LP is up to date. From there we can try the MSP430Flasher again.

    Regards,
    JH
  • 0 in reply to Jace H
    Prodigy 40 points
    Hi

    I did use CCS Cloud and it installed MSP430 CDC/ACM Driver, and then it could find and program the device (MSP-EXP430G2, MSP430G2553)

    Then, after reboot of my PC, I tested MSP430Flasher and it still cannot find my device:

    fetchoo:MSP430Flasher_1.3.7 mazeboard$ MSP430Flasher -i DETECT
    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP430 Flasher v1.3.7 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Executing FET detection sweep:
    * Couldn't find any connected USB FETs!
    * Powering down...done
    * Disconnecting from device...done
    *
    * ----------------------------------------------------------------------------
    * Driver : closed (MSP DebugStack not initialized)
    * ----------------------------------------------------------------------------


    Kind regards
    Taoufik
  • 0 in reply to Taoufik Dachraoui
    TI__Guru 56685 points

    Jaoufik,

    I was able to speak with the Tools team on this and they have informed me that the G2 LaunchPad is not supported by our MSPDebugStack on OS X and Linux. The LP itself has the older ez430 on-board emulation (when compared to newer LPs), which is only supported in Windows. A newer version of the G2 LP is in the works that will include the newer ez-FET emulation HW. Unfortunately, I do not have a timeline for you  on this.

    The reason why Energia is working is because it is using mspdebug as back-end which is a community reverse engineered version of the TI MSPDebugStack.

    In order to use this particular board with OS X, I would suggest Energia, or CCS Cloud for your development. Alternatively, you can bypass the ez-430 emulation HW and directly connect your MSP-FET to the MSP430G2553. you can do this by removing the top-right jumpers and use jumper wires to connect the FET to the G2553 via SBW connections.

    Regards,

    JH

**Attention** This is a public forum