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.

MSP430F5529: How can run mcu self-test (IEC60730 lib) on TI-RTOS?

Other Parts Discussed in Thread: MSP430F5529

Dear all,

When I create MSP430F5529 non-OS example (such as, HELLO example), then include IEC60730 lib and call IEC60730_OSCILLATOR_TEST_testOsc() function.

The IEC60730_OSCILLATOR_TEST_testOsc() function will return PASS. 

But when I create RTOS example and include IEC60730 lib, the  IEC60730_OSCILLATOR_TEST_testOsc() function will return TEST_FAILURE.

I know RTOS need to use Timer0_A0. I change to TimerA1 or TimeA2 on IEC60730 config. But it also return TEST_FAILURE when I call  IEC60730_OSCILLATOR_TEST_testOsc() function.

Can anyone tell me, how should I setting?

Thanks. 

  • Hi All,

    My RTOS project use internal REFO.

    All clock information on below:

    UCS_getACLK = -32768
    UCS_getSMCLK = 8192000
    UCS_getMCLK = 8192000

    I adjust MAIN_CLOCK_FREQUENCY from 8000000 to 8192000 on IEC60730_system_config.h.

    And use  USE_TA1  and USE_CCR0.

    but when I call  IEC60730_OSCILLATOR_TEST_testOsc() again.

    The pass condition on below:

    FREQUENCY_COUNT = 13653
    freqMax = 14062
    freqMin = 13243

    But  my freqCounter is 10061 ~ 10260. not match pass condition.

    Anyone can tell me how to do?

    Thanks.

  • Hello,

    The IEC60730 library was not architected to be utilized with TI-RTOS. Along with possible resource conflicts, your timings could be off due to interference from TI-RTOS scheduler. 

    It is not recommended to utilize the IEC60730 library and TI-RTOS together. 

  • Hi Jace,

    Thanks your reply.

    According to your suggestion, it is recommended to utilize the IEC60730 library and NON-RTOS together?

    If system in TI-RTOS, is has another method to test OSCILLATOR?

    Thanks.

  • Correct, IEC60730 was built for NON-RTOS code development.

    We currently do  not have a solution for similar functionality that works with TI-RTOS. 

**Attention** This is a public forum