I am an embedded systems developer using CrossStudio for MSP430 v3.1 at my place of work. Recently, TI has put out a new version of their MSP-FET tool that they are calling the MSP-FET v2 (also referred to here http://www.ti.com/tool/MSP-FET as the "second generation of the MSP-FET"). From their MSP debugger's guide (http://www.ti.com/lit/ug/slau647l/slau647l.pdf) the MSP-FET v2 can be differentiated from the MSP-FET v1 by the presence of either a "W" at the end of the device's serial number, or a CE marking on the back of the device.
We are currently having issues getting the MSP-FET v2 to work with CrossStudio for MSP430 v3.1 and our research on TI's forums leads us to believe that the problem is that CrossStudio's MSP Debug Stack (in MSP430_v3.dll) is out of date and does not support MSP-FET v2. For instance, a TI employee (http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/701204?CCS-MSP-FET-Could-not-set-device-Vcc) mentions MSP-FET v2 support requires at least MSPDS 22.214.171.124 and Rowley's MSP430 CPU support package page (http://www.rowleydownload.co.uk/msp430/packages/index.htm?http://www.rowleydownload.co.uk/msp430/packages/msp430_v3.htm) mentions MSP430_v3.dll is built on MSPDS 3.8.0.001. We have attempted to rectify the issue by using similar DLLs with updated MSPDS versions (such as those provided by CodeComposer and IAR) but, perhaps unsurprisingly, CrossStudio debug features such as breakpoints end up not working with these DLLs.
We were wondering if the MSP-FET v2 issues were known to Rowley and if so, if either a workaround is known, or if CrossStudio will be updated to support MSP-FET v2 with a new MSP Debug Stack.
Please sign in to leave a comment.