Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Actually, TI doesn't seem to use that one. And if I want to keep the code compilable by IAR and mspgcc in addition to msp430-gcc, I'll have to differentiate between mspgcc and msp430-gcc in order to feed them, at least, different interrupt code.
  2. Ok, now I have one specific question. If I compile with mspgcc, this can be detected by __MSPGCC__ being defined. But how do I do the same thing with MSP430-GCC? SLAU132 http://www.ti.com.cn/general/cn/docs/lit/getliterature.tsp?baseLiteratureNumber=slau132&fileType=pdfseem to indicate that __TI_COMPILER_VERSION__ is the best available option?
  3. Thank you for all your responses, The question about documentation is a very good one, and SLAA664 plus SLAU591A, available from their download page, does indeed seem a bit meager, documentation-wise. SLAA534, linked from them, seem to contain interesting reading material for an evening or two, and SLAU132J should keep me busy for the rest of the week. Is there anything else a beginner in this field should read up on? I often find statements such as "no biggie, just tweak the interrupts, and it works", which does sound encouraging. I'll just have to learn the old and new interrupt syntax,
  4. Hi, I'm trying to port existing code, written for mspgcc and IAR, to the new TI toolchain. There are, as I understand it, a few vital differences in how you should write your code for the two chains. I've tried to find a summary of the differences, and how one should proceed to convert code from the old to the new chains, but I've failed to find very much on the subject. Is there any such tutorial or guide available? It's pretty risk-free to assume that I'm a beginner when it comes to MSP430 and related tools.
  • Create New...