RTOS/CC1310: TI-RTOS, CC1310 Timer linker errors

David Wells58

Part Number: CC1310
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

Hi,

I am trying to get a periodic timer working where it calls an ISR every 200ms. This is my code (largely copied from ti_rtos_spruex3q.pdf):

/* XDCtools Header files */
#include <xdc/runtime/Assert.h>
#include <xdc/runtime/System.h>
#include <xdc/runtime/Error.h>
#include <xdc/std.h>

/* BIOS Header files */
#include <ti/sysbios/BIOS.h>
#include <ti/sysbios/knl/Swi.h>
#include <ti/sysbios/timers/dmtimer/Timer.h>
//#include <ti/sysbios/hal/Timer.h>

/* Board Header Files */
#include "Board.h"

/* Global memory storage for a PIN_Config table */
static PIN_State ledPinState;

extern PIN_Config ledPinTable[];

/* Prototypes */
void timerIsr(xdc_UArg);


void timerTest(void)
{
    Timer_Params timerParams;
    Timer_Handle myTimer;
    Error_Block eb;

    Error_init(&eb);

    Timer_Params_init(&timerParams);
    timerParams.period = 200000;
    timerParams.periodType = Timer_PeriodType_MICROSECS;
    timerParams.arg = 1;
    myTimer = Timer_create(Timer_ANY, timerIsr, &timerParams, &eb);
    if (myTimer == NULL) {
        System_abort("Timer create failed");
    }
}


void timerIsr(xdc_UArg uarg)
{
	;   // Toggle led or something like that here
}

but I can't get it to build as there are these linker errors:

Error[Li005]: no definition for "ti_sysbios_timers_dmtimer_Timer_create" [referenced from C:\Users\dw\Documents\TestProj\Debug\Obj\timer_test.o]
Error[Li005]: no definition for "ti_sysbios_timers_dmtimer_Timer_Params__init__S" [referenced from C:\Users\dw\Documents\TestProj\Debug\Obj\timer_test.o]
Error while running Linker

I suspect I'm missing something like a project setting. Any help would be much appreciated please?

over 8 years ago

0 Alan DeMars over 8 years ago

TI__Mastermind 30830 points

The CC1310 does not have DMTimers so using the ti.sysbios.timers.dmtimer.Timer module will not work for you.

However, the ti.sysbios.family.arm.lm4.Timer module works on the CC1310. It has 4 timer instances available.

You should be able to use the same C code as with the dmtimer Timer module. Just include <ti/sysbios/family/arm/lm4/Timer.h> instead and modify your .cfg file to pull in the lm4 timer module instead:

xdc.useModule('ti.sysbios.family.arm.lm4.Timer');

Alan

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

Thanks Alan, that did the trick.
What I'm finding now though is the timer ISR is only being called every 198ms. Do you have any ideas why that might be please?

0 Alan DeMars over 8 years ago in reply to David Wells58

TI__Mastermind 30830 points

That's unexpected. Using the BIOS ROV view, is the reported CPU frequency correct? In the lm4 Timer "Basic" or "Device" ROV views can you confirm that the 'period' value shown is consistent with 200ms? The period should be the number of CPU cycles in 200ms.

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

I'm new to IAR Embedded Workbench that we're using so when I've worked out how to install the BIOS ROV view plugin or equivalent I'll let you know thanks.

0 Alan DeMars over 8 years ago in reply to David Wells58

TI__Mastermind 30830 points

Select the "TI-RTOS" Plugin as shown below:

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

Thanks for your reply Alan. I did a re-installation and now I can see the BIOS ROV view. These are from the lm4 timer Basic and Device respectively:

Given a 48MHz clock the period looks correct for a time of 200ms (48000000*0.2=9600000). Maybe it's not a 48MHz clock fitted to the SmartRF06 Evaluation Board?

0 David Wells58 over 8 years ago in reply to David Wells58

Prodigy 150 points

I found the RAT to be far more accurate:

.
.
.
    time = RF_getCurrentTime();
    
    while(1)
    {
        time += ((uint32_t)(4000*200);  /* 200ms */
        RF_ratCompare(rfHandle, &pCmdStruct, time, rat_callback);
        Semaphore_pend(semHandle, BIOS_WAIT_FOREVER);
        
        /* show delay on scope */
        PIN_setOutputValue(ledPinHandle, Board_LED1, 1); /* led on */
        CPUdelay((uint32_t)(12000*1));  /* 1ms */
        PIN_setOutputValue(ledPinHandle, Board_LED1, 0); /* led off */
    }
.
.
.


void rat_callback(RF_Handle h, RF_CmdHandle ch, RF_EventMask e)
{
    Semaphore_post(semHandle);
}

0 Alan DeMars over 8 years ago in reply to David Wells58

TI__Mastermind 30830 points

How are your measuring the period? What are you using as your timebase to measure the 198ms?

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

I am toggling an led and using a scope on that to measure the 198ms.

0 Alan DeMars over 8 years ago in reply to David Wells58

TI__Mastermind 30830 points

I am concurring with your suspicion that the clock on the SmartRF board is not running at 48MHz but something 1% faster. Sadly, I don't know which pin you can monitor with the scope to verify the clock frequency.

Alan

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

Hi Alan, I am using the RAT timer now as that seems to be working well so I've decided not to persue this timer issue. Thank you for your help though.

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

Thanks Alan. I was talking to a colleague about this and we think it's running from the RC oscillator and he seems to think 1% accuracy is good for an RC oscillator so perhaps it's as expected. I am using the RAT timer now that uses the crystal oscillator as that seems to be working well so I've decided not to persue this timer issue. Thank you for your help.

0 Alan DeMars over 8 years ago in reply to David Wells58

TI__Mastermind 30830 points

Sounds reasonable to me. Shall we declare that to be the correct answer? :-)

0 David Wells58 over 8 years ago in reply to Alan DeMars

Prodigy 150 points

I'm happy with that. Thanks Alan.

Processors

Processors forum

RTOS/CC1310: TI-RTOS, CC1310 Timer linker errors