Using the MSP430 toolchain in Ubuntu 11.04 is very simple to set up but what about on Macintosh OS X? It turns out that the fink instructions on the MSPGCC wiki for Mac OS X are very good and work flawlessly, even easier than the Linux install. However, the MSP430 USB-Debug-Interface (MSP430UIF) didn’t work immediately, but here is the fix!
- Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Os
- Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Download
- Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Free
- Msp430 Usb
System
- Apr 29, 2017 69.100472 usb 1-4.1: new full speed USB device using ehcihcd and address 5 69.212591 usb 1-4.1: New USB device found, idVendor=0451, idProduct=f430 69.212595 usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 69.212599 usb 1-4.1: Product: MSP-FET430UIF JTAG Tool 69.212601 usb 1-4.1: Manufacturer: Texas.
- Jun 18, 2018 MSP FET430UIF USB DRIVER FOR MAC DOWNLOAD - You are covered by the eBay Money Back Guarantee if you receive an item that is not as described in the listing. See all condition definitions - opens in a new window or tab Tick the box to order the item with an extended warranty. Global Shipping 30 day money back guarantee Secure and flexible payments 24 month free.
- Mar 02, 2016 FET430UIF WIN10 Driver. Prodigy 185 points James6389 Replies: 3. Hello, I use MSP430UIF Debugger, and my OS is WIN10, but it seems that MSP430UIF can't install correct drive on WIN10, Does MSP430UIF support WIN10? MSP-FET430UIF support on Windows 10 definitely seems possible. The MSP-FET430 UIF should enumerate on your.
This procedure has been tested on a MacBook2,1 running Mac OS X 10.6.8 in conjunction with a MSP430 USB-Debug-Interface (MSP-FET430UIF).
Nov 27, 2018 MSP430-USB-Debug-Interface-MSP-FET430UIF-Programmer-Debugger. Back to home page. Learn More – opens fdt430uif a new window or tab Any international shipping is paid in part to Pitney Bowes Inc. Don’t see what you’re looking for? Amazon Inspire Digital Educational Resources. Please enter a number less than or equal to 0.
Attention TI LaunchPad and TI ez430 Users: Do not use these instructions, instead follow, “How do I get an RF2500/Launchpad working on OS/X?”
Obtain Driver
Download the TUSB3410 Mac OS X Virtual COM Port Driver Binaries from Texas Instruments’ (TI) website.
The extracted download includes two files: “TIVCPSerial.kext,” a Kernel EXTension (KEXT) package directory, and “TIVCPSerial Driver Documentation.rtf,” a real text formatted (RTF) document.
Read the TIVCPSerial Driver Documentation.rtf carefully and then follow the install instructions.
The remainder of this document details how to obtain the information needed to configure the TI kernel extension for Mac OS X.
Find bcdDevice, Product ID and Vendor ID
Before the KEXT will work right it needs the configuration file, Info.plist, updated with the specific bcdDevice, Product ID and Vendor ID of specific Universal Serial Device (USB).
The most comprehensive way to obtain the necessary information is to use Apple’s OS X USB Debug Kit (IOUSBFamily). This kit includes the IOUSBFamily KEXT, USB Prober. The USB Prober is a very handy tool to have around and even includes USB logging capabilities for most versions.
These utilities are included with the Apple Development Tools and thus do not require that any additional software be installed or downloaded.
Run the USB Prober application, locate the “MSP-FET430UIF JTAG Tool” device in the USB list.
TIVCPSerial.kext requires that the specific “bcdDevice, Product ID and Vendor ID” be obtained for configuration. Expanding the entry in USB Prober reveals a list of USB Descriptors including the required information. In USB Prober, the bcdDevice is called “Device Version Number.”
Before the TIVCPSerial.kext can be updated the obtained values need to be converted from hexadecimal (base 16) to decimal (base 10). The conversion can be done by any preferred method but sometimes a quick script or calculator can help reduce error. For example the following script could be used via Python 3.
[python]
#!/usr/local/bin/python3
#!/usr/local/bin/python3
bcdDevice = ‘0101’
vendorID = ‘0451’
productID = ‘F430’
vendorID = ‘0451’
productID = ‘F430’
hexValues = bcdDevice, vendorID, productID
decValues = [int(hedValue, 16) for hedValue in hexValues]
print(“bcdDevice: {0[0]}, Vendor ID: {0[1]}, Product ID: {0[2]}”.format(decValues))
[/python]
[/python]
Using the above screen shot as an example the converted decimal values would be 257 for the bcdDevice, 1105 for the Vendor ID and 62512 for the Product ID.
These three decimal values can now be used to configure TIVCPserial.kext.
Edit Info.plist
With these three values in hand, open /System/Library/Extensions/TIVCPSerial.kext/Contents/Info.plist for editing.
In the IOKitPersonalities section, find the three TIVCP3410 (TIVCP3410, TIVCP3410Boot, TIVCP3410Merge) entries and change bcdDevice, idProduct and idVendor appropriately.
Do not change anything else in the file, if the specific value doesn’t already exist for each of the entries do not add it.
Using the New Driver
Restarting the computer will likely be enough for the changes to take but it’s not necessary if the KEXT is unloaded and then reloaded.
[bash light=”true”]
$ sudo kextunload -b com.ti.driver.TIVCPSerial -v
$ sudo kextunload -b com.ti.driver.TIVCPSerial -v
$ sudo kextutil -b com.ti.driver.TIVCPSerial
[/bash]
[/bash]
Conclusion
In this document basic instructions were given for obtaining both the TI binary driver for OS X and Apple USB debugging tools, using the Apple debugging tools and then configuring the TI driver.
If everything worked right and mspdebug is installed a session can be started by executing the following.
Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Os
[bash light=”true”]$ mspdebug uif -j -d /dev/tty.TIVCP34103d10[/bash]
Troubleshooting
Check system profiler, make sure extension actually loaded.
Read the help documentation for kextutil and kextunload if there are problems. The man files on these are pretty short and are very helpful. But if too impatient, here are some commands that proved useful.
[bash light=”true”]
$ sudo kextutil -t /System/Library/Extensions/TIVCPSerial.kext
$ sudo kextunload -b com.ti.driver.TIVCPSerial -v
$ sudo kextload /System/Library/Extensions/TIVCPSerial.kext/
$ sudo kextutil -tnb com.ti.driver.TIVCPSerial
[/bash]
$ sudo kextutil -t /System/Library/Extensions/TIVCPSerial.kext
$ sudo kextunload -b com.ti.driver.TIVCPSerial -v
$ sudo kextload /System/Library/Extensions/TIVCPSerial.kext/
$ sudo kextutil -tnb com.ti.driver.TIVCPSerial
[/bash]
The MSP-FET430UIF Development Tool
The MSP-FET430UIF is a powerful flash emulation tool to quickly begin application development on the MSP430 MCU. It includes USB debugging interface used to program and debug the MSP430 in-system through the JTAG interface or the pin saving Spy Bi-Wire (2-wire JTAG) protocol. The flash memory can be erased and programmed in seconds with only a few keystrokes, and since the MSP430 flash is ultra-low power, no external power supply is required.
The debugging tool interfaces the MSP430 to the included integrated software environment and includes code to start your design immediately. The MSP-FET430UIF development tool supports all MSP430 flash devices.
see also:
Contents
|
Features
- USB debugging interface (MSP-FET430UIF) connects a flash-based MSP430 MCU to a PC for real-time, in-system programming and debugging
- Technical specifications:
- Software configurable supply voltage between 1.8 and 3.6 volts at 100mA
- Supports JTAG Security Fuse blow to protect code
- Supports all MSP430 boards with JTAG header
- Supports both JTAG and Spy-Bi-Wire (2-wire JTAG) debug protocols
Documentation
Software Version
What version of the software tool are you using?
It is recommended that only the latest version be installed for proper functionality.
Updating to the latest version fixes bugs in previous releases and provides support for the latest MSP430 devices. Using the latest version will eliminate software variables as a cause of your issue.
IAR EW430 5.40 has various problems with v3 FET protocol, such as getting message 'Could not find device (or device not supported)' during download. See this article for more information and a workaround.
IAR EW430 Firmware upgrade
If your MSP-FET430UIF is successfully recognized by your OS but within your IAR EW430 the only entry under 'FET Debugger->USB Selection' is 'Automatic',be sure to read the following article: FET-firmware upgrade and downgrade.
IAR EW430 is not recognizing the MSP-FET430UIF
- EW430 version 5.40+ and firmware downgrade
- 'After upgrading to EW430 version 5.40, there might be problems using the FET debugger with older EW430 releases. It is possible to replace the old msp430.dll with the new DLL from EW430 5.40, to get it working. If this does not work, you can use the downgrade utility, V32V2.bat, located in the 430/bin directory to do a firmware downgrade. See the 5.40 Release Notes for more info[..]'.
In other words: If you e.g. worked with IAR EW430 v5.10 and installed parallel an evaluation version >= 5.40 that requested a firmware upgrade, your v5.10 does not longer recognize your MSP-FET430UIF! In this case you have to copy the msp430.dll located in 430binmsp430.dll to your older IAR EW430 version and replace the old one as described above.
IAR EW430 asking for a firmware upgrade of your MSP-FET430UIF
Are you using a valid OS?
The USB FET (MSP-FET430UIF) drivers included with the latest IAR Kickstart and the TI Code Composer Studio IDEs support Windows XP, Vista, and Windows 7, both 32-bit and 64-bit versions. All drivers are Microsoft WHQL certified.
The linux version of CCS5 does not support auto-update (or manual update) of DLL V3 (CDC-based) driver. Without installing a CCS5 or IAR on Windows, the MSP430-Flasher tool can be used for a quick firmware update. See MSP430_Flasher_-_Command_Line_Programmer
Hardware Self Test
When your device is plugged in do the LEDs blink? The pattern should be RED-RED-RED-GREEN and then the green should stay on. This indicates that the device is receiving power.
If the above does not happen: Sometimes updating the firmware will fix this problem, but if not the hardware could be damaged.
Note: The blinking pattern only applies on FET firmware v2. Newer firmware just lights the GREEN led when connected to PC.
2nd PC Test
Have you tried to install the same questionable USB FET on other PCs (using the installation guide steps in appendix C) of the Hardware User's Guide
If your FET works on a second PC the issue probably is a PC driver conflict with your first PC.
Usage History
Was the tool in question ever recognized by any PC? If so were able to successfully program and debug with this tool at any time in the past?
Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Download
If the tool used to work but no longer responds it could be damaged, or the drivers could have a conflict with newly installed 3rd party software.
Custom Board Comparison
Are you using a TI target board or a custom board design?
Hardware considerations can be ruled out by using a TI target board, available for order at www.MSP430.com
JTAG Connections
If you are using your own board, does your JTAG connections differ in any way from the recommendations we give in the Hardware User's Guide, page 23 (4-wire) or page 24 (2-wire/Spy-Bi-Wire)?
If there are significant differences this could very well be the source of your problem. See the Custom Board Comparison topic above.
New Project Test
After the above steps have been performed please do the following: If you create a new project using the steps in the attached word document (IAR [1], CCE V3 [2], CCS V4) and attempt to load a simple TI code example[3], do you see the same issue? This should rule out software considerations.
Device Manager Comparison
You should have a virtual com port (VCP) entry like the image below under PORTS (COM & LPT) If it does not then right-click and reinstall.
EGISENCfile is an Egis Encrypted Data. Egis is bundled with Acer notebook and desktop computers under the name Acer eDataSecurity Management. It is a file encryption utility that protects files from being accessed by unauthorized users. For known file types, an 'ENX' will be appended to the original file extension. Feb 27, 2020 #4. VeraCrypt- Best File Encryption Software for Mac. VeraCrypt, an open-source disk encryption software for Mac, is used for on-the-fly encryption or OTFE. It can create a virtual encrypted disk within a file or encrypt a partition or the entire storage device. MEO File Encryption Software Encrypt and decrypt files and keep your data secure. MEO is easy file encryption software for Mac or Windows that will encrypt or decrypt files of any type. Protect sensitive data against unauthorized viewers with the latest data encryption technologies to keep your important documents safe and secure. Software that open egisenc file - Egis encrypted data Programs supporting the exension egisenc on the main platforms Windows, Mac, Linux or mobile. Click on the link to get more information about Egis for open egisenc file action. The filename extension.egisenc represents the generic Egis Encrypted File (.egisenc) file type associated with the use of data protection utilities developed by Egis Technology Inc. (formerly, HiTRUST Inc.). Such utilities include Acer eDataSecurity Management, MyWinLocker, BioExcess, and come preinstalled on new Acer notebook PC's. Egisenc encrypted file converter software for mac free.
Device Manager
Update: the VCP-stuff is related to DLL V2. For DLL V3 (which add features), the CDC driver must be notified instead of VCP. Both types of drivers create a virtual COM port.
Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Free
Still having problems?
Please open a new request at TI Support & reply to the Service Request bounce-back email with:
- Comments/Answers to the above questions
- Screen image of the device manager & error message
- the newly created workspace and files using the steps above, back to us in a zip file so we may take a look at it. Please also send the answers to the above questions.
Once the above questions are answered we can identify and rule out any issues regarding:
- Driver Errors
- Operating System Incompatibilities
- Software Tool Updates
- Software Setup/Project Option Issues
References
Msp430 Usb
- SLAU138