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.

Grace doesn't have option to set 16MHz for msp430g2230

Other Parts Discussed in Thread: MSP430G2230, MSP430G2553

I created project for grace 2.2.0.00006.

CPU: msp430g2230

I want to set up clock to 16MHz in BCS+ page, but only 1MHz precalibrated option is available.

Datasheet states, that 16 MHz is available for msp430g2230.

Is it grace bug? Any workaround?

  • >Is it grace bug?
    Yes.
    >Any workaround?
    Yes. You shall read 16MHz DCO calibration values and accordingly configure DCO registers in your code.

  • EDIT:  I see I was not choosing the same processor as you. The G2230 seems to have have the additional options. I will file this as a bug with the GRACE team. Int he mean time, you can use another Grace project such as for the G2553 to set up your clock as they use the same clock module. this means the code will be the same.

    Hello KOSTYANTYN,

    I see you are using an older version of Grace. Please update Grace tot he newest version. You can do this from within CCS by navigating to View > CCS App Center, then clicking the See More link on the top right for Code Composer Studio Add-ons. Check the Grace box for update and click the Install Software option at the top left. This should update you tot he latest version of Grace that includes the additional options such as 16MHz clock for MSP430G2553.

    Regards,
    JH

  • Even if we'll override grace-generated init code, Grace will still perform wrong calculations for timer, pwm etc.

    Some further investigation lead me to %grace_dir%\grace_2_20_02_32\packages\ti\catalog\msp430\MSP430.xs
    Looks like Grace keeps model configurations here. It looks like javascript, therefore pretty readable and editable.
    I found parameter hasAllCal. When set to false it "unlocks" only 1MHz. When true - all 4 frequencies.
    I changed it for my 2230 to true, and now I'm able to choose 16MHz for 2230 in Grace.

    To be sure I dumped INFO A of actual 2230 chip. It contains calibration for all 4 frequencies, so seems like it is really bug in Grace.

    I'm not sure if it's 100% correct fix, but at first glance it works.

    PS Btw does anybody know what's writen @ 1000h (very first bytes of INFO A)? Just curious.
  • I'm using Grace standalone (I use IAR, not CCS). Version 2.2.0.00006 is the same as offered for download from http://www.ti.com/tool/grace.
    I tried to update it from About -> Installation Details -> Target content -> Update, but it replies "No updates were found".
    Do you mean, that CCS version of grace is updated while standalone version is outdated?
  • Kostyantyn,

    I do believe the standalone is no longer receiving regular updates, but is kept for legacy reasons. Grace for CCS has improved since the CCSv6 release and is more integrated via the App Center.

    Regards,
    JH
  • >Even if we'll override grace-generated init code, Grace will still perform wrong calculations for timer, pwm etc.
    Yes you are right. I missed this point because don't even know what Grace is.
  • Downloaded the recent CCS with Grace. Same bug there. And I fixed it in the same way: in C:\ti\grace_3_10_00_82\packages\ti\catalog\msp430\initMSP430.xs changed hasAllCal to true for my device model.

**Attention** This is a public forum