support for Launchpad EXP430GET #81
Comments
|
On Wed, Jan 09, 2019 at 08:53:08PM -0800, Doug LaRue wrote:
I was borrowing an EXP430G2 to prog some msp4302553 boards and went to get one from Ti only to find out Ti no longer sells them. They sell the EXP430G2ET in its place but mspdebug doesn't see it.
As a pointer that a Linux tool does work:
In my searches for a solution I found Energia IDE and found the latest version( 21/1.8.7E21 ) does work with the G2ET. Enabling verbose output showed it using DSLite to do the work. I don't know what Ti changed to the programmer interface between G2 and G2ET but maybe the differences can be gleaned from the dslite project.
Hi Doug,
Did you try the TI library with mspdebug's "tilib" driver, or something
else? I'd expect that libmsp430.so should work, since it's supposed to
be able to work with every debugger TI produces.
Cheers,
Daniel
…--
Daniel Beer <[email protected]> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
|
I can't get this to work either: This is the new MSP-EXP430G2ET Launchpad using the provided MSP430G2553 chip. I followed the instructions here to build I also tried Weirdly I had to use |
|
I found out that CCSv8 worked and there was even an installation of mspdebug there. |
|
@dlarue but doesn't CCS use DSLite for debug/programming the board? |
|
@dlbeer @chrissphinx using "mspdebug tilib" with the libmsp430.so worked! I got the libmsp430.so from: I compiled in CCSv8 and loaded Debug/Blink.out changing the blink rate each time and validating the FET430 device LED blinked faster or slower. |
|
@dlarue Are you using another device as opposed to simply plugging the G2ET board in via USB? I'm reading in the manpage that I'm using current master of |
|
@chrissphinx it is the EXP430G2ET from TI. Here my dmesg output: [ 3602.392666] usb 1-1: new full-speed USB device number 11 using xhci_hcd Here is my output from mspdebug tilib ( NOTE: I have disconnected the onboard chip so it does not find the device since I use the FET for custom board programming using same 2553 chip ) dlarue@Lenovo-Z70-80:~/Development/ti/uniflash_4.5.0$ mspdebug tilib Using new (SLAC460L+) API |
|
Here is my own: What version of linux are you using? The only difference I can see is that the |
|
I'm on Kubuntu 18.04 Also, what are your privileges on /dev/ACM* |
|
you know it's going to be one of those palm-smacks-forehead type of problems right? :-) |
|
chrissphinx <[email protected]> writes:
Weirdly I had to use `sudo` despite being in the `dialout` group (and
being able to successfully open the device using `minicom`). Any way
forward with these new boards?
Hi Chris,
When you say you tried sudo, do you mean that you tried it with the
tilib driver, or just the ezfet attempt?
Have you tried with the version of libmsp430.so that Doug suggested
(sorry if you have and I missed it, I'm following this via email).
Cheers,
Daniel
…--
Daniel Beer <[email protected]> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
|
UPDATE: I removed all my TI rules files and rebooted but mspdebug tilib is still able to see the G2ET FET. My two rules files I found which have TI parts( especially 2047/0013 ) are as follows. my udev rules file goes like this: But wait, there's more! I just realized I had another rule with the 2047/0013 ven/prod ids in it. TI USB EmulatorsATTRS{idVendor}=="2047", ATTRS{idProduct}=="0010", ENV{ID_MM_DEVICE_IGNORE}="1" LABEL="mm_usb_device_blacklist_end" |
|
@dlbeer Yes, I am using the I am using Ubuntu 18.04 as well, but through an emulator. I also cannot get CCS to see the board from inside the VM, but it works fine on my host machine (macOS). |
|
chrissphinx <[email protected]> writes:
@dlbeer Yes, I am using the `libmsp430.so` from CCS v9.0.1, so I'm not
sure if that's any different but the line `Chip info database from
MSP430.dll v3.13.0.601 Copyright (C) 2013 TI, Inc.` seems to suggest
we have the same `.so`. I only used `sudo` when I was trying out
`ezfet`.
That line is from information extracted separately and bundled with
mspdebug -- not the .so.
I'd suggest trying the tilib driver with sudo. The error may be due to
insufficient permissions, which the TI library will just report as the
lack of an available device.
Cheers,
Daniel
…--
Daniel Beer <[email protected]> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
|
@dlbeer the issue ended up being this: http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/713463?CCS-MSP-FET430UIF-MSP-FET430UIF-is-already-in-use-on-Ubuntu-18-04 But, @dlarue you are reporting that removing all the udev rules still allows you to make a connection? After installing the As an aside, does anyone know the legalities behind the |
|
@chrissphinx if you are teaching students I can't stress enough the benefits of making one bootable ISO with all the software, documentation, samples etc pre-configured on the bootable ISO. I've been down the road a few times dealing with so many different configuration and the time wasted on setup. Now I spend the time setting up a custom system using Customizer-gui and let students download the ISO, put it on a USB thumb drive and verify it boots before classes even start. And yes, I moved the ti specific udev rules files out of their location and rebooted before being surprised that mspdebug still recognized/found the FET. |
|
@dlarue yes, I'm exploring doing something to that effect, though in general I don't like serving .ISOs since they are quite large. Can I ask, although we're getting off topic here, are you using |
|
I serve the ISO files from a google drive so not bandwidth issues. For msp430 I have CCS v8 running and works fine. Finally full Linux support or at least functionality. |
|
chrissphinx <[email protected]> writes:
As an aside, does anyone know the legalities behind the `libmsp430.so`
library or even the supposedly "open source" `msp430-elf-gcc`? To
obtain them both you seem to need a TI account and that is a real
hassle for my students, am I allowed to distribute a package that will
install everything they need if this library and tool are included?
Hi Chris,
libmsp430.so is BSD-licenced (source code is available on the TI
website). GCC and derivatives including msp430-elf-gcc are GPL. You're
free to distribute both to your students.
Cheers,
Daniel
…--
Daniel Beer <[email protected]> http://dlbeer.co.nz/
PGP: BA6E 0B26 1F89 246C E3F3 C910 1E58 C43A 160A 553B
|
|
@dlbeer Thank you very much for this insight, Daniel! |
|
For what it's worth, I encountered a similar problem this week, that required a slightly different solution.
|
|
I will just comment here to echo @Brad-R 's approach is what we are currently doing, I am bundling |
|
Not Ubuntu; I'm using Debian 10 "Buster", 64-bit. |
|
That would mean Ubuntu 18.04 - 19.10 according to this list: |
I was borrowing an EXP430G2 to prog some msp4302553 boards and went to get one from Ti only to find out Ti no longer sells them. They sell the EXP430G2ET in its place but mspdebug doesn't see it.
As a pointer that a Linux tool does work:
In my searches for a solution I found Energia IDE and found the latest version( 21/1.8.7E21 ) does work with the G2ET. Enabling verbose output showed it using DSLite to do the work. I don't know what Ti changed to the programmer interface between G2 and G2ET but maybe the differences can be gleaned from the dslite project.
The text was updated successfully, but these errors were encountered: