Search the Community
Showing results for tags 'Mac OS'.
Found 2 results
-
Mac OS 10.9.5; MSP-EXP430G2; just downloaded Energia 1.6.10E18; installed MSP430LCPDC 1.0.3b drivers. I installed the drivers and restarted my Mac. I was able to select the /dev/cu.art-XXXXX port, but running Blink gave me a long error, which ended in the selected serial port fet: identify failed does not exist or your board is not connected Power LED on the launchpad works. I've had the board sitting on a shelf for about 3 years, if that makes any difference. I could not locate these drivers on my Mac to verify they were the right ones, but other forum posts leads me to believe that is the right port. Can anyone help me? Thanks.
-
MSP-FET with Energia, mspdebug, or virtualized CCS6?
pjkim posted a topic in Programmers and Debuggers
I received my MSP-FET yesterday-- thank you TI! I was so excited to try out everything. I was deflated to find out that my package only contained the programmer-- hopefully the target board and MSP430FR6989s will arrive soon. It almost felt like Christmas morning-- only to find out the batteries were not included! I wanted to test out my new toy so I hooked up the MSP-FET to some MSP430 chips I hand nearby. I hooked up the MSP-FET to a MSP430G2231 and started Energia on Mac OS X 10.9.4. Although the MSP-FET is seen by the OS, I can't seem to connect to it. On System Info, the vendor/product ID are 0x2047/0x0014 with a description of "MSP Tools Driver." Here are my issues 1) Energia can't connect. If I use File -> Upload, or File -> Upload using programmer, I get "usbutil: unable to find a device matching 0451:f432" 2) If I use mspdebug, I can't connect using tilib or uif. $ mspdebug --usb-list Devices on bus 250: 250:006 2047:0014 [serial: EFF2blahblah] 250:005 05ac:0245 250:002 0424:2513 250:001 05ac:8006 Devices on bus 253: 253:001 05ac:8006 $ mspdebug tilib 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. MSP430_GetNumberOfUsbIfs No unused FET found. $mspdebug uif 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. usbutil: unable to find a device matching 0451:f430 I tried specifying the USB device by adding -U 250:006 but no improvement. Does mspdebug v 0.22 not work with the MSP-FET? Is this a libmsp430.so issue? I was using the one supplied with the latest version of Energia (E0013). 3) If I run CCS6 under VirtualBox, things sort of work. When I start a debug session, I get a message "Error initializing emulator: A firmware update is required for the MSP430 Debug Interface (MSP-FET430UIF / MSP-FET / eZ-FET). Click the "Update" button to update the firmware and launch your debug session (this may require several update steps). DO NOT UNPLUG THE INTERFACE DURING THE UPDATE." If I click UPDATE, the MSP-FET gets bjorked. Probably because of the way virtualbox hands off USB devices between host and guest OSs. I am thinking the USB VID and/or PID are being altered during the update. Regardless, things don't work afterwards and I can't seem to unbjork things without using a physical Windows computer running CCS6. The physical WIndows computer can update the MSP-FET firmware. Curious thing is that after updating the firmware, CCS6 running on virtualized Windows, still wants to upgrade the firmware with the same message above. If on the other hand, I choose the button to IGNORE the firmware update, things start OK and I can start a debug session. Problem is that sometimes I get a error message "MSP430: Trouble Halting Target CPU: Internal error." Things don't work so well afterwards but nothing that a unplug, replug won't fix. 4) I know the MSP-FET is working OK because if I use it on a physical Windows machine, I can program a device, set breakpoints, stop/resume, see energy usage, etc. It works flawlessly. It's a bit disappointing I can't seem to get it to work with mspdebug or virtualized Windows running CCS6.
