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.

MSP430F5438A: Compatibility with Grace

Part Number: MSP430F5438A

Hi,

I currently use CCSv6 for development of the MSP430F5438AIPZ, but I would like to use Grace in order to simplify configuration time and speed up development. I noticed this MSP430 isn't compatible with the current version of Grace (v3.0). Is there a way to add this MCU to Grace? Do I ened a config file or is there a way we can manually add this MCU to Grace? Is there any tool or plugin that we can use in lieu of Grace to speed up configuration time if Grace absolutely cannot work?

Thank you for your help.

  • Hi,

    As you can see in the Description section of the Grace tools page:

    "The Grace Configuration tool will not be updated beyond its current feature set; therefore, no new devices or peripherals will be added. The tool will remain available in its current state. Additionally, the CCS v6 plug-in will not be updated beyond CCS version 6.1.2. The installation instructions below suggest installing this older version of CCS to gain access to the plug-in."

    I suggest that you look into DriverLib or TI-RTOS if you would like an abstracted API for simplified MSP430 control.

    Regards,
    Ryan
  • This is too bad. Grace in CC6 was quite good. DriverLib doesn't support a large number of parts, which means if you are on a F or G part, you are back to 1990 and programming at the bit level, with the 600 page processor manual in one hand and a scope probe in the other as you try to figure out why the timer ISR isn't running.

    Grace made it possible to bring a new board up in minutes without any docs, logic analyzers or scopes, and you were confident all the registers were correct.

    DriverLib, on the processors on which it's supported, is OK IMO. But nowhere near as fast as Grace. I much prefer automatic setup of everything and then manually initiating actions at the register level. DriverLib still requires you to have a big doc open to do what you want. And with a loosely typed language like C and no intellisense, it's a mess. A strongly typed language with intellisense would make DriverLib a dream, but those two pieces aren't any time soon

**Attention** This is a public forum