Preparing firmware for debugging...
Processing lpmsp430fr5994 (platform: timsp430; board: lpmsp430fr5994)
--------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/timsp430/lpmsp430fr5994.html
PLATFORM: TI MSP430 (2.4.0) > TI LaunchPad MSP-EXP430FR5994LP
HARDWARE: MSP430FR5994 16MHz, 4KB RAM, 256KB Flash
DEBUG: Current (mspdebug) On-board (mspdebug)
PACKAGES:
- toolchain-timsp430 @ 1.40603.210219 (4.6.3)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in debug mode
Checking size .pio/build/lpmsp430fr5994/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [ ] 0.0% (used 2 bytes from 4096 bytes)
Flash: [ ] 0.2% (used 472 bytes from 262144 bytes)
========================= [SUCCESS] Took 0.25 seconds =========================
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 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.
undefinedUnknown driver: dslite. Try --help for a list.
Reading symbols from /home/edi/Dokumente/PlatformIO/Projects/Serial/.pio/build/lpmsp430fr5994/firmware.elf...
done.
PlatformIO Unified Debugger -> https://bit.ly/pio-debug
PlatformIO: debug_tool = mspdebug
PlatformIO: Initializing remote target...
.pioinit:11: Error in sourced command file:
:2000: Die Wartezeit für die Verbindung ist abgelaufen.
Terminal:
* Task wird im Ordner Serial ausgeführt: platformio debug
Processing lpmsp430fr5994 (platform: timsp430; board: lpmsp430fr5994)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/timsp430/lpmsp430fr5994.html
PLATFORM: TI MSP430 (2.4.0) > TI LaunchPad MSP-EXP430FR5994LP
HARDWARE: MSP430FR5994 16MHz, 4KB RAM, 256KB Flash
DEBUG: Current (mspdebug) On-board (mspdebug)
PACKAGES:
- toolchain-timsp430 @ 1.40603.210219 (4.6.3)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 0 compatible libraries
Scanning dependencies...
No dependencies
Building in debug mode
Compiling .pio/build/lpmsp430fr5994/src/main.o
Linking .pio/build/lpmsp430fr5994/firmware.elf
Checking size .pio/build/lpmsp430fr5994/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM: [ ] 0.0% (used 2 bytes from 4096 bytes)
Flash: [ ] 0.2% (used 472 bytes from 262144 bytes)
Building .pio/build/lpmsp430fr5994/firmware.hex
======================================================================== [SUCCESS] Took 0.34 seconds ========================================================================
@maxgerhardt unfortunately no one answered in github issues, so I wanted to ask if you might re-open this issue here? Or should all issues be discussed on github?
Thanks
pio pkg exec -p tool-mspdebug --call "mspdebug --help"
gives me following output:
Using tool-mspdebug@1.2400.190926 package
Usage: mspdebug [options] [command …]
-q
Start in quiet mode.
-d device
Connect via the given tty device, rather than USB.
-U bus:dev
Specify a particular USB device to connect to.
-s serial
Specify a particular device serial number to connect to.
-j
Use JTAG, rather than Spy-Bi-Wire (UIF devices only).
-v voltage
Set the supply voltage, in millivolts.
-n
Do not read a configuration file on startup.
-C <file>
Load an alternative configuration file.
--long-password
Send 32-byte IVT as BSL password (flash-bsl only)
--help
Show this help text.
--fet-list
Show a list of devices supported by the FET driver.
--fet-force-id string
Override the device ID returned by the FET.
--fet-skip-close
Skip the JTAG close procedure when using the FET driver.
--usb-list
Show a list of available USB devices.
--force-reset
Force target reset in initialization sequence.
--allow-fw-update
Update FET firmware (tilib only) if necessary.
--require-fw-update <image.txt>
Require FET firmware update. The required image format depends
on the driver.
--version
Show copyright and version information.
--embedded
Run in embedded mode.
--bsl-entry-sequence <seq>
Specify a BSL entry sequence. Each character specifies a modem
control line transition (R: RTS on, r: RTS off, D: DTR on,
d: DTR off).
--bsl-gpio-rts
On some host (say RaspberryPi) defines a GPIO pin# to be used as RTS
--bsl-gpio-dtr
On some host (say RaspberryPi) defines a GPIO pin# to be used as DTR
Most drivers connect by default via USB, unless told otherwise via the
-d option. By default, the first USB device found is opened.
If commands are given, they will be executed. Otherwise, an interactive
command reader is started.
Available drivers are:
rf2500
eZ430-RF2500 devices. Only USB connection is supported.
olimex
Olimex MSP-JTAG-TINY.
olimex-v1
Olimex MSP-JTAG-TINY (V1).
olimex-iso
Olimex MSP-JTAG-ISO.
olimex-iso-mk2
Olimex MSP430-JTAG-ISO-MK2.
sim
Simulation mode.
uif
TI FET430UIF and compatible devices (e.g. eZ430).
uif-bsl
TI FET430UIF bootloader.
flash-bsl
TI generic flash-based bootloader via RS-232
gdbc
GDB client mode
tilib
TI MSP430 library
goodfet
GoodFET MSP430 JTAG
pif
Parallel Port JTAG
gpio
/sys/class/gpio direct connect
load-bsl
Loadable USB BSL driver (USB 5xx/6xx).
ezfet
Texas Instruments eZ-FET
rom-bsl
ROM bootstrap loader
In addition I want to say that I use the MSP-EXP430FR2433 board, which is not listed above. So my device isn’nt supported by FET driver? What does this mean?
pio pkg exec -p tool-mspdebug --call "mspdebug gdb"
Using tool-mspdebug@1.2400.190926 package
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 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.
Unknown driver: gdb. Try --help for a list.
A more general question: Does the mspdebug work on my system? I use OSX 13.3.1 and according to the official documentation mspdebug is supported on following systems:
The MSP Debug Stack is officially supporting the following operating systems:
* Windows Vista, 32- and 64-bit
* Windows 7, 32- and 64-bit
* Windows 8, 32- and 64-bit
* Windows 10, 32- and 64-bit
* Linux Ubuntu 12.04, 32- and 64-bit
* Linux Ubuntu 14.04 32- and 64-bit
* Linux Ubuntu 16.04 32- and 64-bit
* Linux Suse 10.3
* OS X 10.9 (Mavericks) 64-bit
* OS X 10.09.5 (Yosemite) 64-bit
* OS X 10.11.4 (El Capitan) 64-bit
* OS X 10.12.x (Sierra) 64-bit
Thata’s weird because when I execute that, I get at least the attempt to startup up.
>pio pkg exec -p tool-mspdebug --call "mspdebug gdb"
Using tool-mspdebug@1.2400.190926 package
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 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.
----------------- NOTE ------------------
Modified version of mspdebug for Energia
Do not use standalone
-----------------------------------------
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.
Can you spin up a vritual Linux machine using VirtualBox or something and test the command inside a VM with the USB device for the dev boad forwarded?
I can try this later.
What is the difference between gdb and gdbc?
For me I get these results:
$ mspdebug gdbc
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.
gdbc: no remote target specified
$ mspdebug gdb
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.
Unknown driver: gdb. Try --help for a list.
$ pio pkg exec -p tool-mspdebug --call "mspdebug gdb"
Using tool-mspdebug@1.2400.190926 package
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 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.
Unknown driver: gdb. Try --help for a list.
$ pio pkg exec -p tool-mspdebug --call "mspdebug gdbc"
Using tool-mspdebug@1.2400.190926 package
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 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.
gdbc: no remote target specified
In addition I installed mspdebug via homebrew. I also have the binary under Users/jp/.platformio/packages/tool-mspdebug/mspdebug