I work for some time with msp430fr57xx family of FRAM MCUs. My OS is Linux Mint.
Hardware programmer is eZ430 board. For programming of a target MCU I use MSPDEBUG (v.0.22) with a simple command line:
mspdebug rf2500 "prog <file>.elf"
The command works well either from Terminal window or as a Tool of Code::Blocks and Code Compose Studio.
Then I tried to launch hardware GDB debug and had to make MSPDEBUG v.0.23 from source. After some amount of experiments I switched to a msp430g2231 as a target MCU (to make all things easier)...
But now I returned to FRAM MCU and as it seems - MSPDEBUG refuses to program my chips!
How it is looked:
1) The connect is OK, I try
mspdebug rf2500
... here I get the messages about the connection - and the MCU type is shown right...
(mspdebug)
2) At this point I can put mspdebug commands, such as run, md and so on. As you see, connect is good.
3) But the command prog or just erase cannot be executed. I get various messages, such as
rf2500: can't receive data: Resource temporarily unavailable
fet: erase command failed
fet: FET returned error code 14 (Could not erase device memory)
What can it be? I searched in Google for such messages, but all cases mostly about the connection problems. At StackOverflow there is a close topic, but it is old and the answer is "to get latest mspdebug" :)
Checked another ez430 programmer, changed tardet chips - the same result.
I can return to v.0.22 of MSPDEBUG, but maybe there's another solution.