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.

It's fast, it's stable, it's open source - the MSP430.DLLv3 Debug Stack

Other Parts Discussed in Thread: CC430F6137

We're glad to announce that we've just released the MSP430.DLLv3 - TI's all new MSP430 Debug Stack!

The MSP430.DLLv3 is the component in between your IDE and the MSP430 microcontrollers when you download or debug code. This all new version provides faster debugging and significant stability improvements. In addition, it is available as OPEN SOURCE and was created in an host operating independent manner!

The first product that includes the new MSP430 debug stack is CCSv5.1, the IAR Embedded Workbench and all other 3rd party product releases will follow immediately. The migration to the new MSP430.DLLv3 works in a fully automated manner (see important note below).

The MSP Debug Stack Wiki page www.ti.com/mspds contains all information and download links.

YOUR FEEDBACK COUNTS!

We're highly interested in any feedback! Please use the E2E forum to provide feedback or to contact us in case problems.

IMPORTANT NOTE:

(1) This software requires an update of the MSP-FET430UIF firmware that goes beyond the usual updates. In addition to the firmware, also the USB stack of the debugger will be updated. Once an update was done, the debugger won't work with old IDE versions ("Interface not found"). However, CCSv5.1 includes a small utility that allows downgrading the debugger at any time to be used with old IDE versions and utilities again. Please see www.ti.com/mspds.

(2) Old MSP-FET430UIF interfaces may require an extra  step in the automated update procedure. Please visit  www.ti.com/mspds for additional information.

 

 

 

  •  After update to new version doesn't work with older ide...

     I got a lot of UIF interfaces broken by windows service pack and failed upgrade so why try this one and lose other and last one??...

     Older IDE have a cost and why lose them? Why not to preserve compatibility did you learn from M$?

     Wrong move!!!

     Regards

     Roberto

  • Roberto Romano said:

     After update to new version doesn't work with older ide...

     

    I guess you have to "downgrade" the firmware if you want to use with the old IDE which uses the old DLL. Please refer to: http://processors.wiki.ti.com/index.php/MSP_Debug_Stack#Downgrade_back_to_old_MSP430.DLLv2

  • Hi Roberto,

     

    Now worries - we're not taking anything away from you. I may not have been clear above - you can switch amonst the IDE version! You just need to downgrade the interface if you want to go back from e.g. CCSv5.1 to CCSv4.

    It's fully backwards compatible (see www.ti.com/mspds) - all new products will use this new, significantly improved version.

     

    Regards,

    Markus

  • I downloaded the new CCSv5.1 and well during that time I read some things what I can expect from it, and the new Debug Stack in particular. What jumped right in my face is, that the clock cycle count is no longer working. I hope this is only for some time and not forever - it's a quite critical tool if you want to analyze your code for efficiency.

    But then I could try it out, and wow - it's amazingly fast, I can't tell the difference between single stepping a program on my computer or on the MSP. Well done indeed, I probably can't turn back now, you just get used to speed, and if you loose it, something always tells you how fast you could go...

    I like the recent turns you have taken to support open source even more - keep it up.

  • Hi Bernhard,

    Great to hear - thanks a lot for your feedback!

    You are right, the Cycle Counter support is not functional in this particular release, but will come in the next package (planned for January).

    Regards,
    Markus

  • So will the FET update process work on ez430 FET debuggers?

  • Tim,

    The new MSP430.DLLv3 supportes the eZ430 debuggers, but will not update them yet (it's planned however). Please see www.ti.com/mspds for additional details.

    Regards,
    Markus

  • I'm not exactly sure, but I think I stumbled upon a possible bug in either the CCSv5.1 or the MSP430.DLLv3, I've posted a detailed report in the CCS Forum. (I don't want to blow this thread up by lengthy discussions, and it's not a MSP430 problem so it should go there, right?)

  • Hello,

       IIRC this debug stack was the last piece missing in making a mac version of Code Composer. I've heard rumors from inside TI that there's an unsupported, don't call us if it breaks, use at your own risk port of Code Composer for Mac. Would that be possible to get? Of course with all the aforementioned caveats, obviously.

     

    --Derek

  • Hi markus,

    I been through MSP debug stack Wiki,Its saying that its not supporting for linux yet ..IIts bad to hear that Since many people(almost all in my company) using Linux..cant you people release along with the Windows.. Now i needed to takeout my Linux OS and install the Windows for using CC430F6137.. ...When  you people planning to release for Linux(Ubuntu 10.04 or later versions)...

     

     

     

     

     

     

    regards,

    Jagas

  • JAGAS EDARA said:
    Now i needed to takeout my Linux OS and install the Windows for using CC430F6137

     Hi Jagas, I am using win$ product on Virtual box, they work better than in native mode.

     The worst is no compatibility with the past and I don't like this upgrade downgrade to restore compatibility. Also worst not to have a linux native layer nor method to repair broken interfaces. If you are using more than one version of IDE this is a pain and also risky due to possible blow out of interface.

     Again to TI staff: how can i repair UIF and EZ430 broken from winz upgrade failure? After that I am using a launchpad and a elprotronic fetpro430 I never buy an UIF to risk broke and i wish use Linux only...

     Why not build a compatibility layer to avoid broke interfaces???

    Regards

     Roberto

  • Hi roberto,

    Now  my using windows for that..

    ya i also felt bad about upgrade and downgrade Since some projects are done under CCSv4 and SOme r using CCSV5..

    If i wanted 2 use same UIF for ccsv4 n ccsv5 i need to do upgrade or downgrade again n again..

     

     

     

    Regards,

    Jagas

  • I found another bug with the new version that I've posted in BSL Access under v5  (It was originally posted in the CCS forums but someone moved it to the MSP430 forums)

    Hopefully this is another fix for your planned release this month.

**Attention** This is a public forum