This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: Linux
My issue is related to This Post. It seems that newer MSP-fet devices do not work under Linux. We ordered a new MSP-fet device (Serial number begins with 17 and ends with W).
In Linux (Lubuntu 15.10), using MSP430-Flasher v1.3.8 we get the error "Could not set device VCC" (same symptom as described in the referenced post).
Updated MSP430-Flasher to v1.3.15 and ran the msp430uif_install.sh script from the Driver folder but still receive the same error (Could not set device VCC).
Note that the Old MSP-Fet still works in Linux with MSP430-Flasher v1.3.15.
Interestingly, I found the following under Windows
New MSP-Fet: Using MSP430-Flasher v1.3.8: receive "Could not set device VCC" error (as expected)
New MSP-Fet: Using MSP430-Flasher v1.3.15 works properly (as expected)
Old MSP-Fet: Using MSP430-Flasher v1.3.8 works properly (as expected)
Old MSP-Fet: using MSP430-Flasher v1.3.15 Prompts for firmware upgrade (did not do this in Linux). I said no for fear that doing so would prevent it from working under Linux, then received "Could not set device VCC" error.
I would like to be able to use either device under either OS, but at the very least, the new MSP-fet should work with the new MSP430-Flasher under Linux.
Thanks.
Hi James, thanks for getting back to me. Below is what was returned.
_MSPDS_VERSION_ 3.10.1.000
Hello Mark,
Thanks for providing this information. I've relayed it to our Tools team, and they are wondering if the MSP-Flasher is using the correct 'libmsp430.so' file. It's possible that another file outside the MSP-Flasher folder is being used instead.
So, let's try the following steps.
1. In your shell, navigate to the MSP-Flasher folder and execute the following command. This should make the executable to look into the current folder first when it searches for the 'libmsp430.so' file.
$ export LD_LIBRARY_PATH=.
2. Then, run the MSP-Flasher executable.
Let me know if this resolves the issue.
Regards,
James
MSP Customer Applications
YES! This fixed it. Thank you.
It was using an old copy of libmsp430.so from /usr/lib/
Thanks Again,
Mark
**Attention** This is a public forum