Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac

Posted on by

Msp430 Msp-fet430uif Lsd-fet430uif USB JTAG Emulator Programmer Debugger TI. Please enter a valid ZIP Code. Refer to eBay Return policy for more details. Seller information sunwenjun Will usually ship within 1 business day of receiving cleared payment – opens in a new window or tab. The following tools contain the USB debug interface (MSP-FET430UIF) and the respective target-socket module:.MSP-FET430U14 (for MSP430 devices in 14-pin PW packages).MSP-FET430U28 (for MSP430 devices in 20- and 28-in DW or PW packages).MSP-FET430U38 (for MSP430 devices in 38-pin DA packages).

USB Debugging Interface, Real-Time, In-System Programming and Debugging Some Part number from the same manufacture Texas Instruments, Inc. MSP-TS430PZ100USB Specifications: Silicon Family Name: MSP430F5xx; Core Architecture: MSP430; Core Sub-Architecture: MSP430; IC Product Type: Debugger / Programmer; Kit Contents: JTAG Header Cable, Two. Low-Level USB CDC or VCP Drivers These drivers provide an interface between the high-level debugger drivers (MSP430.DLL & HIL.DLL) and the MSP-FET430UIF's USB interface. This is accomplished by using a Communication Device Class (CDC) or Virtual COM Port (VCP) protocol. My old MSP-FET430UIF MSP430 USB-Debug-Interface works fine with CrossWorks. The drivers are installed and the Flash Emulation Tool shows up in Windows Device Manager. It also works with the Texas Instruments MSP430Flasher program version 1.3.7. The following tools contain the USB debug interface (MSP-FET430UIF) and the respective target socket module:.MSP-FET430U14 (for MSP430 devices in 14-pin PW packages).MSP-FET430U28 (for MSP430 devices in 20- and 28-in DW or PW packages).MSP-FET430U38 (for MSP430 devices in 38-pin DA packages). . MSP-FET430UIF(debug interface with USB connection, for all MSP430 flash-baseddevices). eZ430-F2013(USB stick form factor interface with attached MSP430F2013 target, for all MSP430F20xx, MSP430G2x01, MSP430G2x11, MSP430G2x21, and MSP430G2x31 devices).

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

  • 3MSP-FET430UIF Troubleshooting

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?

/freebsd-92-download.html. 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?

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.

Device Manager
Msp430

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.

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

  • SLAU138
  • 3Downloads
  • 4Low-Level USB CDC or VCP Drivers
  • 5Releases

Overview

The MSP debug stack (MSPDS) for all MSP430 devices is called MSP430.DLL. It consists of a dynamic link library as well as embedded firmware that runs on the MSP-FET430UIF or the eZ430 emulators. It is the bridging element between all PC software and all MSP430 microcontroller derivatives and handles tasks such as code download, stepping through code, break point handling and so forth. Examples that use the DLLv3 are IDEs such as Code Composer Studio (CCS), IAR's Embedded Workbench or others. Also other TI tools like Smart RF Studio or Elprotronic's FlashPro430 are using the MSP430.DLL.

The MSP debug stack is officially supporting the following Operating Systems:

  • Windows XP SP3, 32- and 64-bit
  • Windows Vista, 32- and 64-bit
  • Windows 7, 32- and 64-bit
  • Windows 8, 32- and 64-bit
  • Linux Ubuntu 10.04
  • Linux Suse 10.3


What's new in the MSP430.DLLv3

We're glad to announce that we've released MSP430.DLLv3 end of 2011! It is an all new version of the previous MSP430.DLLv2, which has been used in all tools until October 2011. The DLLv3 was created from scratch and was written in an object oriented way, which allows for simpler modifications.

Furthermore, we're introducing a new USB protocol (CDC) for the MSP-FET430UIF debuggers, which will improve stability significantly and doesn't require any drivers except for an .inf file.

One of the most important aspects of the MSP430.DLLv3 is that it is available as open source software. See the MSPDS Open Source DLL package.

The DLLv3 supports all features of the previous DLLv2 (see release notes for limitations). In addition it features:

  • Open source package
  • Host OS independent design
  • Linux support (Open Source Release available - see below and in CCSv5.2 and newer)
  • Faster operation, especially when stepping through code
  • Improved stability - CDC driver for the MSP-FET430UIF debugger
  • Improved usability
  • Extended LPMx.5 support

Backward compatibility:The new MSP430.DLLv3 provides full backward compatibility once the MSP-FET430UIF debugger has been updated and the CDC driver has been installed on the target system. The automated update from MSP430.DLLv2 to MSP430.DLLv3 for the MSP-FET430UIF debuggers is a new feature however, and not compatible with previous IDE releases.


IMPORTANT NOTE
The DLLv3 requires a significant firmware-update of the MSP-FET430UIF debugger. This update is different from the usual DLLv2 update, as the USB protocol stack will be updated as well. Once an update was done, the updated MSP-FET430UIF debugger won't work with older IDE or other MSP430.DLL based software anymore, unless a downgrade will be performed. For details see MSPDS Debugger Up- and Downgrade.
IMPORTANT NOTE
Do not unplug the JTAG cable during an active debug session! This might cause unknown device behavior!


Downloads

There are numerous ways of obtaining the MSP430.DLL.

  • If you intend to program your MSP430 device out of an IDE, simply download the latest CCS or IAR Embedded Workbench release. The latest MSP430.dll will be included.
  • Download the MSP430 Flasher to be able to access the basic functionality of the MSP430.DLL on the command line.
  • Download the DLL Developers Package if you plan to create your own project based on the MSP430.DLL.
  • Download the MSP430.DLL open source package to take a look at the low-level functionality (includes the MSP-FET430UIF firmware!)

IDEs

Each new IDE release with support for new MSP430 derivatives will include the latest version of the MSP430.DLL.

The first IDE versions that contain the new MSP430.DLLv3 are:

  • Code Composer Studio (CCS) v5.1 and newer - available on web, see CCSv5 Wiki
  • IAR EW430 5.40.2 and newer - Available from IAR and the TI IAR EW430 Wiki.


Default MSP430/HIL.dll locations:
  • CCSv5: C:ticcsv5ccs_baseDebugServerdrivers
  • CCSv4: C:Program FilesTexas Instrumentsccsv4DebugServerdrivers
  • CCE: C:Program FilesTexas InstrumentsCC Essentials v3DebugServerdrivers
  • IAR: C:Program FilesIAR SystemsEmbedded Workbench 5.0430bin
NOTE
The DLL version is aligned with the IDE release it's part of. Since different versions might include API changes it is not recommended to exchange these files. If a DLL exchange is absolutely necessary, make sure the IDE is shut down while doing this. Also it is strongly recommended to make a backup copy of the original files.


MSP430 Flasher

The MSP430 Flasher is a command line tool which provides easy access to the most common functions of the MSP430.dll

(programming & reading device memory, setting hardware breakpoints or blowing the security fuse).

Get the MSP430 Flasher here.

Msp430 Usb Debug Interface Msp Fet430uif Drivers For Mac Download


DLL Developers Package

The DLL Developers Package contains everything to give your DLL-based MSP430 project a head start:
  • DLL binaries
  • DLL developers guide
  • Documentation material
  • Low-Level USB drivers
  • Application examples


Download DLL Developers Package v3.3.1.4 Released 09/27/2013
Older versions:
  • DLL Developers Package v3.3.1.3 - Released 06/28/2013
  • DLL Developers Package v3.3.0.6 - Released 01/31/2013
  • DLL Developers Package v3.2.5.4 - Released 09/27/2012
  • DLL Developers Package v3.2.4.5 - Released 06/26/2012
  • DLL Developers Package v3.2.3.15 - Released 04/04/2012
  • DLL Developers Package v3.2.1.9 - Released 11/08/2011
  • DLL Developers Package v2.4.9.1 - Released 05/08/2011


Open Source Release

The MSP430.DLLv3 is available as open source software.

It has been tested on Windows and Linux [see distributions above]

Get the Open Source package here.


Documentation

Download the MSP430.DLL documentation directly without any additional software.


Low-Level USB CDC or VCP Drivers

These drivers provide an interface between the high-level debugger drivers (MSP430.DLL & HIL.DLL) and the MSP-FET430UIF's USB interface. This is accomplished by using a Communication Device Class (CDC) or Virtual COM Port (VCP) protocol.Please note that all necessary low-level drivers are included in each IDE release (Code Composer Studio & IAR Embedded Workbench) and get installed automatically. Download these drivers only if you are solely using the Open Source DLL or the MSP430 Flasher.

Windows

Please use our new and easy-to-use stand-alone driver package. It does not only include the CDC drivers for the latest MSP Debug Stack releases but also legacy VCP drivers for DLLv2 support.

Supported operating systems: WinXP-32/64, WinVista-32/64, Win7-32/64, Win8-32/64

Download driver package - these drivers are Microsoft WHQL certified.

The USB CDC drivers to use the back-channel UART on the LaunchPad or on the eZ430 Emulator can be downloaded and installed from this link: Download

Linux: Native CDC support - no driver installation required - Download installation script to set the required udev rules

Msp430 Usb Driver

Linux

Native CDC support - no driver installation required - Download installation script to set the required udev rules

VCP (for legacy DLLv2 support only):

Download from Brimson Labs Kernel 2.4: Release notesKernel 2.6: Release notes

MAC OS X (experimental)


Releases

Msp430 Usb

ReleaseDateCCS versionIAR versionUSB DriverNotes
DLLv3
3.3.1.4 September 20, 2013 CCSv5.5.0.00077 + MSP430 emulation p2 update package (5.5.0.18) 5.60.2 CDC 1.04

New device support:

  • MSP430F5259 Full device series

New features:

  • N/A

Bug Fixes:

  • Added support for remaining MSP430F5259 spins

Known Limitations:

  • On devices with FLL, clock control does not allow to keep clocks running, while the device is halted and the clock is sourced by the FLL
    Workaround: None
  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
    Workaround: None


3.3.1.3 June 28, 2013 CCSv5.5.0.00077 5.60.1 CDC 1.04

New device support:

  • MSP430FR5969 Rev. E - ULP debug feature support
  • MSP430FR5969 Rev. D - Basic debug support only
  • MSP430G2xx4 - eZ430 emulator series support update (e.g. for onboard LaunchPad emulation)
  • MSP430F5259 (single device only)
  • MSP430F5249 Family
  • MSP430i2040 Family

New features:

  • Enhanced support for new eZ-FET debuggers
  • 64 bit Jstate readout for MSP430FR5969
  • Added eZ-FET & eZ-FET lite BSL firmware project
  • Added new easy to use software breakpoint API
  • Added DCDC MCU firmware project to eZ-FET firmware project

Bug Fixes:

  • Fixed: Magic pattern is not fully functional
  • Fixed: 0x3FFF when reading upper 16 byte from RAM on MSP430FR5969
  • After calling the status = MSP430_Reset(.); TST line high
  • Fixed some preprocessor defines
  • Improved UART communication stability in no-handshake mode on eZ-FET
  • Fixed: Could not set device Vcc - COM port blocked by OS
  • Fixed Cycle Counter reset
  • Clarified error message for communication error (previously 'Could not set VCC')
  • Fixed potential timeout of data verification (MSP430F6659 in SBW2)
  • DLL now returns correct architecture for MSP430F5969 in DEVICE_T
  • Added main flash segment size to DEVICE_T

Known Limitations:

  • Only support for MSP430F5259, but not the full series
  • On devices with FLL, clock control does not allow to keep clocks running, while the device is halted and the clock is sourced by the FLL
    Workaround: None
  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
    Workaround: None
3.3.0.6 January 31, 2013 5.4.0.00091 5.51.6 CDC 1.04

New device support:
MSP430G2xx5, MSP430G2xx4, MSP430TCH5E

New features:

  • Added support for new eZ-FET & eZ-FET light debuggers
  • Added new firmware project for eZ-FET & eZ-FET light debuggers
  • Implementéd HID recovery mechanism for eZ-FET & eZ-FET light debuggers
  • Linked HID-BSL library into DLLv3 to handle HID communication
  • Added unique Tool ID for eZ-FET and MSP-FET430UIF
  • Createed function to scan for multiple debuggers with different PID & VID
  • Added Hil_Configure API function to configure protocol on low level

Changes:

  • Changed update mechanism to handle different debuggers by adding different update managers
  • Removed polling handling from DebugManager by creating new PollingManager
  • Changed overcurrent detecion on MSP-FET430UIF to shut down power after 60ms in overcurrent case not after 10ms
  • Separated all FW projects into hardware specific parts
  • Deprecated old Reset function commands/states
  • Fixed thread race conditions in CDC IO channel class
  • Removed CDC & FLOW Control for new eZ-FET & eZ-FET Lite debuggers

Bug Fixes:

  • Improved error message if MSP-FET430UIF FW doesn't match
  • Removed C++ headers from include directory
  • Clear LPMx.5 debug settings when calling MSP430_Close
  • Fixed funclet offset addresses, which could cause RAM corruption

Known Problems:

  • On devices with FLL, clock control does not allow to keep clocks running, while the device is halted and the clock is sourced by the FLL
    Workaround: None
  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
    Workaround: None
3.2.5.4 September 27, 2012 5.3.0.000090 5.51.3 CDC 1.04

New device support:
MSP430F535x, MSP430F565x, MSP430F635x, MSP430F665x

Changes:
Removed deprecated functions

  • MSP430_Identify
  • MSP430_Breakpoint
  • MSP430_EEM_Open
  • MSP430_EEM_Read_Register
  • MSP430_EEM_Read_Register_Test
  • MSP430_EEM_Write_Register
  • MSP430_EEM_Close

Bug Fixes:

  • Improved update stability and behavior in case of a failed update
  • Fixed occasional errors after firmware update without power cycle
  • Fixed wrong RAM sizes for MSP430FR57xx devices
  • Fixed bug where 0x00 was written behind a FRAM write
  • Fixed issue where EDI parity could be invalidated on writing

Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
3.2.4.5 June 26, 2012 5.2.1.00018 5.50.1 - FET613 CDC 1.04

New device support:
MSP430SL5438A, MSP430F6779(1), CC430F5123, CC430F5125, CC430F5143, CC430F5145, CC430F5147, CC430F6143, CC430F6145, CC430F6147, MSP430FR5969, MSP430FR5949 (Wolverine)
New features:

  • MPU and IP protection are handled by the DLL on all MSP430FRxx devices -> Access violations will be suppressed by the debugger
  • Implemented WriteMemoryQuick() function to write directly into the FRAM memory using JTAG
  • Removed write and erase funclets for MSP430FR59xx devices - erase is now handled using the JTAG mailbox, write is done using WriteMemoryQuick()
  • Implemented erase mechanism to erase IP protected memory areas without accessing it
  • Enhanced USB-FET VCC startup behavior to match the V2 DLL (VCC will be activated when the USB connector of the USB-FET is plugged in)
  • Enhanced EEM support (state storage implementation fully functional; implemented cycle counter for counting cycles during a single run)

Bug Fixes:

  • Corrected DLL database entry for min. flash voltage on 471x devices
  • Fixed single stepping issues on L092
  • Fixed DCO calibration bug, where the original DCO setting was not restored after debug break (device running slower after read)
  • Fixed DLL database entry for the EEM level of the MSP430F5228
  • Fixed disassembly window issues on MSP430FR59xx devices
  • Fixed issues with fast port close/open

Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
3.2.3.15 March 16, 2012 5.2.0.00069 5.40.6 - FET611 CDC 1.04

New Features:

  • Added calibration of clock frequency to ensure exact flash timings, before Flash erasing or writing
  • The UIF now starts up supplying 3V to target

Bug Fixes:

  • Writing to BSL is now working when an erase or erase check, followed by a reset, was performed before
  • Writing to memory with enabled MPU on FRAM devices not possible anymore
  • Fixed a bug causing flash erase and write errors on MSP430F413
  • Size of DEVICE_T struct has been increased to match embedded v2 DLL
  • Port handling has been changed to prevent a port can't be reopened after closing
  • Added fix to prevent possible RAM corruption when reading CPU registers on 5xx/6xx devices

Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
3.2.3.2 December 30, 2011 5.1.1.00031 5.40.3 - FET610 CDC 1.04

Bug Fixes:

  • All 2xx Special Function Registers are not longer read as 0x3FFF
  • Step over certain instructions is now working
  • Flash programming at VCC < 2.7V for F1xx/F4xx now works
  • FLL Debug Error, RST after GO is fixed
  • C092: Connection to ROM device generates no errors anymore
  • Write File API call no longer fails with ERROR_OPERATION_ABORTED
  • Fixed FE427A / T103 Problems with FLL clock frequency while debugging
  • Debugger operation sets VMAIFG on MSP430F5438A
  • DLL now returns when USB FET is disconnected during FW update

Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
3.2.2.0 December 23, 2011 - 5.40.1 - FET608 CDC 1.04

New device support:
CC430F5123, CC430F5125, CC430F5143, CC430F5145, CC430F5147, CC430F6143, CC430F6145, MSP430G2210, MSP430G2230 Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
3.2.1.9 November 8, 2011 5.1.0.09000 - CDC 1.04

The DLL version 3.2.1.9 is an all new DLL design compared to the last DLL version 2.4.9.1. This new DLL includes also a new UIF-Firmware. Furthermore the USB driver has been changed to a certified CDC driver. The DLL is implemented in C++ and follows an object based design, which is host operating system independent. The API of the new DLL is the same as for the old one. DLL functionality keeps the same as in the old V2 DLL. The new DLL V3 also includes a compiled version of the DLL v2.Known Problems:

  • This MSP430.dll version might not be compatible with revision 1.3 of the MSP-FET430UIF if a capacitor is connected to the RST pin.
DLLv2
2.4.9.1 May 8, 2011 CCSv4.2.4 5.30.1 - FET607 VCP 6.5.9017.0

New device support:
L092 Rev. E, F5229, F5224, F5219, F5214, F5228, F5223, F5218, F5213, F5227, F5222, F5217, F5212, F6730, F6720, F6700, F6731, F6721, F6701, F6732, F6722, F6702, F6733, F6723, F6703,F6438, F6436, F6435, F6433, F5338, F5336, F5335, F5333, FR5737, FR5736, FR5727, FR5726, FR5734, FR5733, FR5732, FR5724, FR5723, FR5722, FR5731, FR5721, CC430F6147
Bug Fixes:

  • Fixed magic pattern mechanism
  • Corrected RAM definition of CC430F6137
  • Fixed wrong SR content (0xE1) after wakeup from LPM3.5
  • Improved reliability of connect if device is in LPMx.5
  • Software handshake needs to be configured for UIF only, not for eZ430
  • Fixed download with USB tool and REV D

Known Problems:

  • To prevent problems when multiple USB FET's are connected to your system: Please use different USB HUB's in your computer. If you unplug an USB FET during an active debug session, the session could be interrupted and the IDE could stop working.
  • MSP430_EEM_SetBreakpoint() does not set range breakpoints correctly on all 5xx devices with small emulation logic. Workaround: None.
2.4.8.2 March 10, 2011 CCSv4.2.3 5.20.4 - FET604 VCP 6.5.9017.0

New device support:
MSP430FR57xx, MSP430AFE253, MSP430AFE233, MSP430AFE223,MSP430AFE252, MSP430AFE232, MSP430AFE222, MSP430AFE251,MSP430AFE231, MSP430AFE221, MSP430AFE250, MSP430AFE250,MSP430AFE220, MSP430G2552

New Features:

  • Enhanced MSP430.DLL to support LPMx.5 debugging for the MSP430FR5739. The MSP430F5739 can enter LPMx.5. The DLL will detect this device state change and send a notification to the IDE via a callback. LPMx.5 debug is just available on the USB-FET and on the FRAM ez430.

Bug Fixes:

  • i_ReadMemQuick fixed: MOVA is now correctly calculated when resetting the PC after read out is done.
  • The thread handling and synchronization of the MSP430.DLL threads has been improved. The Critical Section mechanism has been replaced by a MUTEX which handles the USB communication with the USB-FET.
  • The erase problem, which was found on the new G2xx devices, has been fixed too. The DLL did not provide enough TCLK strobes when erasing the main memory. This fix is a DLL only fix; no new ez430-Launchpad firmware is required.
  • Fixed an FR5739 bug where the Disassembly window and memory window content is read wrong after code download
  • Fixed the password flow for FR5739 where the IDE would crash whenever a password was provided for a device that wasn't password protected
  • Fixed FRAM Memory corruption on memory write
  • Fixed a bug where the INFO memory wasn't 100% erased while download

Known Problems:

  • To prevent problems when multiple USB FET's are connected to your system: Please use different USB HUB's in your computer. If you unplug an USB FET during an active debug session, the session could be interrupted and the IDE could stop working.
  • MSP430_EEM_SetBreakpoint() does not set range breakpoints correctly on all 5xx devices with small emulation logic. Workaround: None.
2.4.7.1 November 30, 2010 CCSv4.2.1 5.20.1 - FET603 VCP 6.5.9017.0

New device support:
MSP430AFE253, MSP430F5329, MSP430F5328 MSP430F5327 MSP430F5326, MSP430F5325, MSP430F5324, MSP430G2452, MSP430F5342, MSP430F5341, MSP430F5340, FW428, FW429

New Features:

Enhanced MSP430.DLL to support LPMx.5 debugging for the MSP430FR5739. The MSP430F5739 can enter LPMx.5 when Release JTAG on Go is selected.

Bug Fixes:

  • MSP430_EEM_SetBreakpoint() fixed: Breakpoints are working correctly above the 64k boundary.
  • Fixed L092 SingleStepping Problems
  • Fixed 'FLL Debug Error, RST after GO'
  • Fixed 'handshake is switched on automatically after Fast Flasher'
  • Fixed 'Step over certain instructions do not work'

Known Problems:

  • To prevent problems when multiple USB FET's are connected to your system: Please use different USB HUB's in your computer. If you unplug an USB FET during an active debug session, the session could be interrupted and the IDE could stop working.
  • MSP430_EEM_SetBreakpoint() does not set range breakpoints correctly on all 5xx devices with small emulation logic. Workaround: None.
2.4.6.1 November 5, 2010 CCSv4.2.0 5.10.6 - FET602 VCP 6.5.9017.0New device support:

MSP430F6733, MSP430F11x2 & MSP430F12x2 new revisions, MSP430F5510, MSP430F5509, MSP430F5508, MSP430F5507, MSP430F5506, MSP430F5505, MSP430F5505, MSP430F5504, MSP430F5503, MSP430F5502, MSP430F5501, MSP430F5500, MSP430F5310, MSP430F5309, MSP430F5308, MSP430F5304

New Features:

  • Enhanced MSP430.DLL to support LPMx.5 debugging for the MSP430FR5739. The MSP430F5739 can enter LPMx.5 when Release JTAG on Go is selected.
  • Implemented a special handling for the Fast-eZ in the MSP430.DLL. MSP430.DLL can now handle the Fast-eZ430(3kb/s download speed) and all old version of the eZ430.
  • A software and hardware handshake has been implemented in the MSP430.DLL and USB-UIF firmware to increase stability of the USB communication.

Bug Fixes:

  • Fixed MSP430_EEM_SetBreakpoint(): Register breakpoints are now working correctly on all 5xx devices with small emulation logic.
  • Fixed 'UIF gets stuck, both LEDs stay on'
  • Fixed 'Retry upon debugger launch doesn't work'
  • Fixed 'CCS hang upon debugger launch occasionally'
  • Fixed 'Device gets Reset when BootData is displayed in memory window'
  • Fixed 'Device generates POR during Single Stepping'
  • Fixed 'Set PC to Cursor' function from CCS deletes SP'
  • Fixed 'EDI: single stepping over EDI PUC event returns wrong program counter'

Known Problems:

  • To prevent problems when multiple USB FETs are connected to your system, please use different USB HUBs in your computer. If you unplug a USB FET during an active debug session, the session could be interrupted and the IDE could stop working.
  • MSP430_EEM_SetBreakpoint() does not set range breakpoints correctly, on all 5xx devices with small emulation logic Workaround: None.
2.4.5.3 July 1, 2010 CCSv4.1.3 5.10.4 - FET601 VCP 6.5.9017.0New device support:

MSP430F438, F439, full support for L092 and C092 devices.

New Features:

  • Implemented function to download application code to an external SPI memory, which is connected to the L092.
  • Added password support for the C092. Configured it to start in the correct mode.
  • Added automatic interface scan to DLL: Now it's possible that the DLL scans automatically for connected interfaces. The DLL detects the first unused FET on an interface and initialize it. First HID devices are initialized. If the first interface is in use, the next unused interface will be initialized.

Bug Fixes:

  • Corrected issues in the struct sDebugInfo[]. Now the number of Register Triggers is valid.
  • Corrected RAM size definition for MSP430F5132.
  • Fixed read DATA QUICK MEMORY function.
  • Implemented different DATA QUICK MEMORY function for the L092.
2.4.4.0 April 1, 2010 CCSv4.1.2 5.10.1 - FET600 VCP 6.5.9017.0New Device Support:
  • MSP430F5510
  • MSP430F5630, F5631, F5632, F5633, F5634, F5635, F5636, F5637, F5638
  • MSP430F6630, F6631, F6632, F6633, F6634, F6635, F6636, F6637, F6638
  • MSP430F5131, F5132, F5151, F5152, F5171, F5172
  • MSP430G2211, G2201, G2111, G2101, G2011, G2001, G2231, G2221, G2131, G2121, G2031, G2021

New Features:

  • Added automatic protocol detection to DLL: Now it's possible that the DLL scans automatically, if the connected device operates in JTAG or Spy-bi-wire mode. If the function MSP430_Configure(INTERFACE_MODE, AUTOMATIC_IF) is called, the automatic protocol scanning will be started. Also the automatic mode is selected by default.
  • New behavior for reading dual port memories (derivatives with USB) has been implemented in the DLL. That means, just the dual port memory is read in a word by word mode. The rest of the memory is read in DATA QUICK mode. This fix increases debugging performance on 5xx device with dual port memory.
  • New API call: MSP430_OpenDevice() (see DLL documentation for details)
  • New API call: MSP430_GetFoundDevice() (see DLL documentation for details)
  • New API call: MSP430_SET_SYSTEM_NOTIFY_CALLBACK() (see DLL documentation for details)
  • The DEVICE_T struct was enhanced with device-specific EMM information (see DLL documentation for details)

Bug Fixes:

  • Implemented fix for HP machines and the eZ430-430: This fix enables the DLL to recognize the eZ430-430 on HP computers.
  • The read DATA QUICK MEMORY function has been fixed. Now, no invalid memory access is preformed under debugger control.
  • A fix for DMA debugging is implemented in the DLL release. However, the debugger may show invalid DMA transfer data.

Known Problems:

  • MSP430_EEM_SetBreakpoint() does not set register breakpoints correctly on all 5xx devices with small emulation logic. Workaround: None.
2.4.2.0 November 1, 2009 CCSv4.1.0 4.21.7 - FET522 VCP 6.5.9017.0New Device Support:
  • MSP430F5527, MSP430F5418A
  • MSP430F47163IPZ(R), F47173IPZ(R), F47183IPZ(R), F47193IPZ(R)
  • MSP430F47126IPZ/R, F47127IPZ/R
  • MSP430F46161IPZ(R), F46171IPZ(R), F46181IPZ(R), F46191IPZ(R), F4481IPZ(R), F4491IPZ(R)
  • MSP430F4616IPZ(R), F4617IPZ(R), F4618IPZ(R), F4619IPZ(R)

Bug Fixes:

  • MSP430_VerifyMem() and MSP430_EraseCheck() don't return STATUS_ERROR anymore when used for Flash memory verification with small F54xx(A) & F54xx devices
  • Fixed 'Debugger stops on the ISR-Handler, instead of BreakPoint.'
  • Fixed 'Wrong Stack value stored if CPU stops on breakpoint with incoming interrupt.'
  • Fixed 'CPU accepts interrupt requests although CPUSUSP is set.'
  • Fixed 'Singlestep over NMI request by Software stores wrong return address on stack.'
  • Fixed 'Stop and Go of Debugger in LPMx increments the PC by 2.'

Known Problems:

  • MSP430_VerifyMem() and MSP430_EraseCheck() return STATUS_ERROR when used for Flash memory verification of F5521 , F5521 & F5513 devices although the memory contains the correct content. Workaround: Use MSP430_Memory() instead for verification.
  • The Word-by-word mode is much slower than DATA_QUICK mode. This decreases the performance during the memory read on the MSP430F55xx devices.
2.4.1.4 October 9, 2009 CCSv4.0.1 4.21.4 - FET521 VCP 6.5.9003.0New Features:

The memory read routine was updated because of memory design changes on the F55xx family. If the device memory is spitted over two physical flash memory blocks it's important that both physical memory blocks are erased when a mass erase occurs.

Known Problems:

  • MSP430_VerifyMem() and MSP430_EraseCheck() return STATUS_ERROR when used for Flash memory verification with small F54xx(A) AND F55xx devices (MSP430F5436(A),MSP430F5419(A),MSP430F5437(A), MSP430F5435(A), MSP430F5418(A)) although the memory contains the correct content. Workaround: Use MSP430_Memory() instead for verification.
  • The Word-by-word mode is much slower than DATA_QUICK mode. This decreases the performance during the memory read on the MSP430F55xx devices.


New Findings

This section describes new findings that have been identified after the release happend (i.e. not covered in release notes). They are planned to be addressed in the upcoming release.


Msp430 Usb-debug-interface Msp-fet430uif

#SymptomsTreatment
1 DLLv3.3.1.3 only supports MSP430F5259, but none of the other F525x spins. No workaround, we're about to provide a new release with a fix for this issue.
2 A FET firmware update from older DLL versions (up to v3.2.3.15) to v3.2.4.5 and newer versions might not be completed correctly. In this case, the IDE/programmer software won't respond anymore. The IDE/programmer software will have to be closed and restarted. Additionally, the FET has to be unplugged and reconnected again.
3 Can't launch debug session for MSP430F67xx devices when using 4-wire JTAG mode. Make sure that device is not in LPMx.5 when launching a debug session or use 2-wire SBW mode.
4 Error message 'Can't set Vcc' occurs upon debug session launch with DLLv3.3.0.6. Known issue that's under investigation. Workaround: Unplug/reconnect debug interface and launch debug session again. This issue has been fixed in DLLv3.3.1.3 and newer versions.
5 Can't set breakpoints while device is running (FR59xx series) with DLLv3.3.0.6. This feature is not yet supported but will be for the next release. This issue has been fixed in DLLv3.3.1.3 and newer versions.
6 Can only access F2xx master devices (e.g. MSP430F2274 works, but not the F2272) with eZ-FET based emulators. This bug will be fixed with the next release. This issue has been fixed in DLLv3.3.1.3 and newer versions.


Feedback

Your feedback to the MSP40.DLLv3 binary as well as the open source release is highly appreciated! Please visit the E2E forums!