Linux/MSP430FR2433: Launchpad behaves not as expected, cannot communicate

Of course I tried to load different programs, self-compiled and shipped with the examples, in ELF and TXT form, including a self-compiled `blink` example with modified delay value. Even after `erase`, LED continues to blink the same way.

As I said, my main problem is that mspdebug does not work (but pretends to). So I cannot load anything.

I get behavior described in my original post with mspdebug 0.22. Since then I tried the current mspdebug (0.25), with the same libmsp430.so built from slac460w.zip. The new version of mspdebug insisted on updating the FET firmware, failed, and now the board does not blink, shows as USB type 2047:0203 and I still cannot load any programs (bricked? I still have another board).

Bruce, you seem to get the board working, which version of mspdebug and which version of slac460 source did you use?

I cannot run CSS (TI says "does not work with this version of glibc, we are looking into this issue"), and I would rather not use GUI tools if I can help it.
I found "native TI" command-line tool www.ti.com/.../MSP430-FLASHER, that comes with its own (binary) copy of libmsp430.so. If I run it with it's included libmsp430, I have some better results:

- On the "fresh" board, MSPFlasher suggests to upgrade FET firmware, I do *not* agree, and then it works and can successfully load programs. Yay?
- I am reluctant to let it upgrade FET firmware lest my second board gets borked.
- When I run MSPFlasher with the slac460w copy of libmsp430, it cannot upgrade FET FW and cannot load programs.
- On the board that the slac460w copy of libmsp430 unsuccessfully tried to upgrade, MSPFlasher (with own libmsp430) tries to upgrade firmware, but fails. The board still does not work:

* -----/|-------------------------------------------------------------------- *
* / |__ *
* /_ / MSP Flasher v1.3.16 *
* | / *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Corrupted USB FET firmware detected. Starting recovery.
# Exit: 49
# ERROR: MSP-FET / eZ-FET recovery failed
*
* ----------------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------------
*/

UPDATE:

MSPFlasher_1.3.16 borked my second board (I accidentally allowed it to upgrade the FET firmware).

I installed MSPFlasher-1.3.16-linux-x64 downloaded from the TI site on a new Linux box (Ubuntu 16.04.3 LTS) without any pre-existing msp430 related software. I was able to load a few example programs to the launchpad, answering 'N' to MSPFlasher's prompt to upgrade the firmware. They worked. Then, I accidentally ran it with `-s` flag, it tried to upgrade the firmware, failed, and now fails to recover it.

First run:

* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.16                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ ttyACM0 <- Selected
* Initializing interface @ ttyACM0...done
* Checking firmware compatibility:
* The firmware of your FET is outdated.
* Skipped firmware update prompt.


*********************************************************
*                                                        
*  Initializing Update Bootloader.                       
*  Programming new firmware:                             
*  |||||||||||||||||||||||||||||||||||||||||||||||||| 100%# Exit: 49
# ERROR: MSP-FET / eZ-FET core(communication layer) update failed
* * ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

Subsequent attempts:

* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.16                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers: 
* Corrupted USB FET firmware detected. Starting recovery.
# Exit: 49
# ERROR: MSP-FET / eZ-FET recovery failed
* 
* ----------------------------------------------------------------------------
* Driver      : closed (No error)
* ----------------------------------------------------------------------------
*/

I even installed CCS on this box (it's an old distro so it did install), it also tries to recover the firmware, and also fails.

This time no self-compiled or third-party software was involved, only tools downloaded directly from ti.com.

TI support, please help!!!

FYI, there is a beta of CCS 7.4 which does work with newer distros:

http://processors.wiki.ti.com/index.php/Code_Composer_Studio_Beta_Downloads

I also ran into the corrupted FET firmware when I was going back and forth between Energia, CCS, and CCS Cloud.  One of them was able to recover it, but I honestly can't remember which.  So hopefully that means your board is not permanently bricked.