• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 80 subscribers
  • Views 1573 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSP430 CCS adding Timer1_A3 error when not used

Glenn Jackson
Prodigy 180 points
Other Parts Discussed in Thread: MSP430FR5739

I am using CCS v5.4.0.00091 for the MSP430FR5739.

I am using Grace to define Timer0_B3, Timer1_B3, and Timer2_B3 for PWM outputs.

CCS is forcing  Timer0_A3, and Timer1_A3 into the compile adding the error, "Timer1_A3" is not defined.

I cannot remove the *_A3 timers as they are locked on the main.cfg peripheral list.

What can I do to remove the *_A3 Timers so that I can compile my code.

Thanks.

  • 0
    Guru 227245 points

    Strange, as the FR5739 has these. Actually all the FR573x have two Timer_A3, only the ones with an even number have just one Timer_B3 instead of three.
    Sure you selected the proper target in the project settings?

     I’m sure you noticed that in your other post, there Is no content after “I get this:” and “and this:”.

  • 0 in reply to Jens-Michael Gross
    Guru 23000 points

    And for the FRAM devices keep your CCS (and his header files) updated, select the latest version of the compiler. Also its recommended to use the eabi (ELF) output format.

  • 0 in reply to Glenn Jackson
    Prodigy 180 points

    Let's see if this works:

  • 0 in reply to Jens-Michael Gross
    Prodigy 180 points

    From Table 1. "Family Members" (Pg.2) of the MSP430FR573x Data Sheet for the MSP430FR5739, under Timer_A is listed 3,3 and under Timer_B is listed 3,3,3. This gives the available timers as Timer0_A3, Timer1_A3, Timer0_B3, Timer1_B3, and Timer2_B3. The Grace modules confirm these availabilities. I am not using any of the *_A3 timers and I am using all three *_B3 timers.


    When I attempt to remove (deselect) the *_A3 timers, I get the error: 

    Unable to stop Using Timer1_A3 Reason: ti_mcu_msp430_csl_timer_Timer1_A3 is still being used, on line 30

    and

    Unable to stop Using Timer0_A3 Reason: ti_mcu_msp430_csl_timer_Timer0_A3 is still being used, on line 36

    ******************

    The Error that pops up when I attempt a compile is:

    "Timer1_A3" is not defined.  
    Resource: main.cfg  Location: Configuration Validation  Type: XDCTools Configuration Marker

    ******************

    main.cfg is the Grace main configuration file. Timer1_A3 is not defined, because I am not using Timer1_A3.

    This error pops up when I try to increase the speed configuration of the *_B3 timers.

  • 0 in reply to Leo Bosch
    Guru 227245 points

    Leo Bosch said:
    And for the FRAM devices keep your CCS (and his header files) updated, select the latest version of the compiler. Also its recommended to use the eabi (ELF) output format.

    And don’t import old FR5x-based projects into new CCS versions. Create a new project and copy the source files (or manually update the linker script, as the old one in the project folder probably won’t work with the newer header files)

  • 0 in reply to Glenn Jackson
    Prodigy 180 points

    So, the question is, What is the dependency on the *_A3 timers to the *_B3 timers in Grace? How do I eliminate the *_A3 timers from the build (that are currently causing an error block to building)? This occurs when I adjust the *_B3 clocks to a higher frequency; the *_A3 clocks are brought in by Grace.

    Thank you.

  • 0 in reply to Glenn Jackson
    TI__Guru 68116 points

    Hi Glenn,

    Thanks for reporting this. We have reported your issue to the Grace development team as a potential bug, so they will investigate it further. Sorry to hear of your difficulties.

    Regards,

    Katie

**Attention** This is a public forum