Bad mspdebug command "No such file or directory"

[AlexusBlack]

Upload action calls wrong mspdebug command

• LaunchPad board name and version: MSP430G2 with MSP430G2553
• Energia IDE version (found in Energia > About Energia menu): 1.8.7E20
• Board package version (found in Tools > Boards > Boards Manager menu): 1.0.4
• OS name and version: Mac OS X 10.13.6

Describe the expected results.

Upload action calls
/Applications/Energia.app/Contents/Java/hardware/tools/mspdebug/mspdebug rf2500 --force-reset 'prog /var/folders/b_/7vlctxfj04nd4g_z2r7y3vx40000gn/T/arduino_build_59286/sketch_oct03a.ino.hex'
(prog and file path enclosed with quotes together)
that uploads to MC without errors

Describe the actual results.

Upload action calls mspdebug with "prog" outside of quotes what results in error in Energia and when command copied in terminal

Energia: 1.8.7E20 (Mac OS X), Board: "MSP-EXP430G2 w/ MSP430G2553"

Build options changed, rebuilding all
Sketch uses 816 bytes (4%) of program storage space. Maximum is 16384 bytes.
Global variables use 20 bytes (3%) of dynamic memory, leaving 492 bytes for local variables. Maximum is 512 bytes.
/Applications/Energia.app/Contents/Java/hardware/tools/mspdebug/mspdebug rf2500 --force-reset prog '/var/folders/b_/7vlctxfj04nd4g_z2r7y3vx40000gn/T/arduino_build_59286/sketch_oct03a.ino.hex' 
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 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.
Trying to open interface 1 on 013
Initializing FET...
FET protocol version is 30394216
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Sending reset...
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: 25 53
prog: '/var/folders/b_/7vlctxfj04nd4g_z2r7y3vx40000gn/T/arduino_build_59286/sketch_oct03a.ino.hex': No such file or directory
An error occurred while uploading the sketch

List the steps to reproduce the problem.

Press upload button.

Problem can be easily fixed by moving singular quote before file name to be before "prog" command.

[AlexusBlack]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

[ponyatov]

I use mspdebug directly (Debian Linux) it requires single right-down quotes to run 'prog file.hex' but the programming speed is very very low (EXP-MSP430G2 Launchpad + MSP430F5418A).

dpon@dpon:~$ mspdebug rf2500 'prog /home/dpon/mips220/mipsIAR/Debug/Exe/mipsIAR.hex '
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2013 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.

Trying to open interface 1 on 008
rf2500: warning: can't detach kernel driver: No data available
Initializing FET...
FET protocol version is 30394216
Set Vcc: 3000 mV
Configured for Spy-Bi-Wire
Device ID: 0x0080
fet: unknown device
msg28_data: [0x1a bytes]
    00 80 17 17 08 0a 91 82 84 6e 25 00 16 00 f8 fe 
    57 95 91 03 01 00 1a 00 04 05 
Using Olimex identification procedure
Device ID: 0x0080
  Code start address: 0x5c00
  Code size         : 131072 byte = 128 kb
  RAM  start address: 0x1c00
  RAM  end   address: 0x5bff
  RAM  size         : 16384 byte = 16 kb
Device: MSP430F5418A
Number of breakpoints: 8
fet: FET returned NAK
warning: device does not support power profiling
Chip ID data: 00 80 17
Erasing...
Programming...
Writing 4096 bytes at 5c00...
Writing 4096 bytes at 6c00...
Writing 3079 bytes at 7c00...
Writing  103 bytes at 8808...
Writing    2 bytes at fff2...
Writing    2 bytes at fff8...
Writing    2 bytes at fffe...
Done, 11380 bytes total
dpon@dpon:~$ 

[ajitjadhav28]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

Worked! :)

energia-1.8.10E23
MSP430G2553
Ubuntu 18.04

[RamonTav]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

It Works!!!
/energia-1.8.10E23-linux64/energia-1.8.10E23/hardware/energia/msp430/platform.txt
MSP-EXP430G2
Fedora 32
Muchas gracias!

[mhunsberger56]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

DUDE!!

You rock. I knew it had to be something simple. Thank you for saving me some digging.

[foxxmotor]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

It's also work for me. Thank you so much!

[fatimaaijaz1212]

The problem seems to be in the Java/hardware/energia/msp430/platform.txt file on lines 112 and 117. There are single quotes around file name and they break the command (no sure if on MacOSX only).
Removing single quotes from around the .hex file makes in-energia program\upload possible again.

It's also work for me. Thank you so much!

heyy, how exactly did you implement it that it works? Need help ASAP please do let me know