Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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.

MSP-EXP430G2ET: cannot connect with mspdebug

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

Using mspdebug under 64-bit Debian Linux 10, I am unable to connect to the MSP-EXP430G2ET Launchpad with mspdebug version 0.25.  I have had no problems connecting to the older MSP-EXP430G2 Launchpad. 

I read that the MSP-EXP430G2ET uses a different debug interface (eZ-FET).  Trying "mspdebug ezfet" fails:

brad@bradsphenom:~$ mspdebug ezfet
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.3.1.4 Copyright (C) 2013 TI, Inc.

Reset communications...
Version: 2.11.0.1, HW: 0xaaadaaad
Reset firmware...
hal_proto_execute: HAL exception: 0xffff
hal_proto_execute: fid: 0x51

I also read that if 'ezfet' fails, it might be necessary to install libmsp430.so and use 'tilib'.  This also fails:

brad@bradsphenom:~$ mspdebug tilib
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.3.1.4 Copyright (C) 2013 TI, Inc.

Using new (SLAC460L+) API
MSP430_GetNumberOfUsbIfs
No unused FET found.

On the off chance that it was a permissions issue, I tried the same with 'sudo', and got the same results both times.

I have read other posts on the e2e forum but have not seen a solution to this issue.

  • I may have accidentally fixed this.  While trying to get Uniflash to work (subject of another thread), I installed the MSP FET Drivers from http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_FET_Drivers/latest/index_FDS.html  .  After doing that, I decided to try mspdebug again, and it recognized the board:

    brad@bradsphenom:~$ mspdebug tilib
    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.3.1.4 Copyright (C) 2013 TI, Inc.

    Using new (SLAC460L+) API
    MSP430_GetNumberOfUsbIfs
    MSP430_GetNameOfUsbIf
    Found FET: ttyACM0
    MSP430_Initialize: ttyACM0
    FET firmware update is required.
    Re-run with --allow-fw-update to perform a firmware update.
    tilib: device initialization failed

    Running  mspdebug tilib --allow-fw-update was successful, and then mspdebug would allow me to program the board.  I now need to verify that it is programming my application correctly.

  • Yes, my application is running correctly.  So I believe this issue is solved.

**Attention** This is a public forum