We are making a Visual Studio extension to build and debug MSP430 firmware with GCC/GDB. We are currently using the mspdebug project to interface the hardware debugger (eZ430-RF2500, Olimex MSP-JTAG-TINY, Olimex MSP-JTAG-ISO, TI FET430UIF). However, it seems that mspdebug does not support all modern on-chip debuggers.
Is there any official list of the on-chip debuggers used for MSP430 microcontrollers? Are there other programs that allow using gdb to debug those?
That's how we integrated the mspdebug tool and we would like to add similar support to other hardware on-chip debuggers.
Well, MSPDebug is still under development.
Most MSP software communicates with the MSPs through the MSP430DLL. Either the TI one (supporting the FET-UIF and most other TI FETs, including the EZ430 versions), or whatever comes with the FET used (e.g. the Olimex verison of the MSP430.DLL).The old mspgcc 3.2.3 project and its msp430-jtag tool used an own implementation too, which was only working with the standard serial or parallel FETs (and did not support the 20 bit addressing on many newer MSPs). GDBProxy was used to connect GDB with the MSP through this DLL. However, this toolchain was abandoned some years ago.
_____________________________________Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.
OK, thanks! Could you please suggest me where could I get the gdbproxy source code? Looks like the mspgcc sourceforge page only contains binaries and the link to the original website is broken. Also is there any official documentation on the API inside the msp430dll?
Ivan ShcherbakovAlso is there any official documentation on the API inside the msp430dll?
Also, the MSP430.dll source code is available for download in slac460 - see MSP Debug Stack
Sorry, I don't have the old source code. I dimly remember looking into the source code for teh MSPGCC.lib through sourceforge HTML-CVS browser some tiem ago. But I'm not sure whether the toolchain was available too.
Chester GillonThe download link on Download MSP430.DLL V18.104.22.168 Released 04/04/2012 contains documentation on how to use the API and some example programs which use the API.Also, the MSP430.dll source code is available for download in slac460 - see MSP Debug Stack
Jens-Michael GrossHowever, this is the 3x DLL API. IIRC, the older 2x API is likely different (or else there wouldn't be all the hassle with teh new IAR and CCS verisons requiring V3 DLL etc.)
However, at the DLL api level not sure if there are any differences. e.g. I had a CCS 4.2.5.00005 installation which installed MSP430.dll v22.214.171.124. I overwrote the dll used by CCS 4.2.5 with MSP430.dll v126.96.36.199 from a CCS 5.2.1 installation, and the CCS 4.2.5 installation was able to use the later 3x DLL to be able to download and single step a program.
By getting CCS 4 to use the later 3x DLL it means that you appear to be able to switch CCS versions without having to keep upgrading / downgrading the MSP-FET430UIF firmware (which causes the "hassle").
(I know TI don't suggest this is supported, but appears to work...)
Chester GillonI had a CCS 4.2.5.00005 installation which installed MSP430.dll v188.8.131.52. I overwrote the dll used by CCS 4.2.5 with MSP430.dll v184.108.40.206 from a CCS 5.2.1 installation, and the CCS 4.2.5 installation was able to use the later 3x DLL to be able to download and single step a program.
Anyway, without 'official' confirmation, I would use such a setup with extreme care. While download and single-stepping appear to work, there still might be differences that make othe rfeatures unavailable or lead to unexpected problems that do not show up immediately.
Jens-Michael GrossSo maybe the V3 DLL API is backwards compatible. It may still have been expanded. Did you try to use the 2x DLL with CCS5?
However, I have used an MSP430-JTAG-TINY with the Olimex.dll v1.0.42 with both CCS 4 and CCS 5. This Olimex driver was released in July 2011 when only CCS 4 was available. Since the Olimex driver developed for CCS 4 still works with CCS 5 it suggests that there is no fundamental DLL API interface change between the 2x DLL and 3x DLL. Will see if I can find any documentation about DLL API differences between the 2x and 3x DLLs.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.