Ti RTOS cc1310 idle loop function

Ben Duvenage22

Other Parts Discussed in Thread: CC1310, CC3200

Hi All RTOS gurus

I'm new to TiRTOS but not new to MCU's.

I recently got my hands on the TiRTOS and we did a board layout that works with the sample code in the TiRTOS cc13xx portfolio. I

I went through the training (online video) by Eric Willburr. I'm gald I did

I'm now busy to wrap my head around the way the RTOS runs a task in idle mode.

Here is what I'm trying to do.

1) I used the led toggle sample that runs a stask every so often

here the code of my main

/*
 *  ======== empty_min.c ========
 */
/* XDCtools Header files */
#include <xdc/std.h>
#include <xdc/runtime/System.h>

/* BIOS Header files */
#include <ti/sysbios/BIOS.h>
#include <ti/sysbios/knl/Task.h>
#include <ti/sysbios/knl/Clock.h>

/* TI-RTOS Header files */
// #include <ti/drivers/I2C.h>
#include <ti/drivers/PIN.h>
// #include <ti/drivers/SPI.h>
// #include <ti/drivers/UART.h>
// #include <ti/drivers/Watchdog.h>

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

#define TASKSTACKSIZE   512

Task_Struct task0Struct;
Char task0Stack[TASKSTACKSIZE];

/* Pin driver handle */
static PIN_Handle ledPinHandle;
static PIN_State ledPinState;

/*
 * Application LED pin configuration table:
 *   - All LEDs board LEDs are off.
 */
PIN_Config ledPinTable[] = {
    Board_LED0 | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,
    Board_LED1 | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,
	Board_LED2 | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,
    PIN_TERMINATE
};

/*
 *  ======== heartBeatFxn ========
 *  Toggle the Board_LED0. The Task_sleep is determined by arg0 which
 *  is configured for the heartBeat Task instance.
 */
Void heartBeatFxn(UArg arg0, UArg arg1)
{
    while (1) {
        Task_sleep((UInt)arg0);
        PIN_setOutputValue(ledPinHandle, Board_LED0,
                           !PIN_getOutputValue(Board_LED0));
    }
}

Void benSeTask(void)
{
	//while(1)
	{
		unsigned int t,x;
		for(t=0;t<500000;t++)
		{
			x=x++;
		}
		PIN_setOutputValue(ledPinHandle, Board_LED2,
		                           !PIN_getOutputValue(Board_LED2));
	}
}

/*
 *  ======== main ========
 */
int main(void)
{
    Task_Params taskParams;


    /* Call board init functions */
    Board_initGeneral();
    // Board_initI2C();
    // Board_initSPI();
    // Board_initUART();
    // Board_initWatchdog();

    /* Construct heartBeat Task  thread */
    Task_Params_init(&taskParams);
    taskParams.arg0 = 1000000 / Clock_tickPeriod;
    taskParams.stackSize = TASKSTACKSIZE;
    taskParams.stack = &task0Stack;
    Task_construct(&task0Struct, (Task_FuncPtr)heartBeatFxn, &taskParams, NULL);

    /* Open LED pins */
    ledPinHandle = PIN_open(&ledPinState, ledPinTable);
    if(!ledPinHandle) {
        System_abort("Error initializing board LED pins\n");
    }

    PIN_setOutputValue(ledPinHandle, Board_LED1, 1);

    /* Start BIOS */
    BIOS_start();

    return (0);
}

I have add the "idle" task as in picture

In the .cfg script I have done this

If I run the application the Led Task is running but the idle loop function does not work as expected.

I would expect that when the Led Task is running the idle loop function must stop and when the Led task is complete that the idle loop function toggles the other led.

So what do I miss?

Kind regards

Ben

over 7 years ago

0 Sasha Slijepcevic over 7 years ago

TI__Mastermind 37985 points

Ben,
I tried a similar example on a different board and I can see that the idle loop is running as expected. Can you try adding System_printf to benSeTask() to separate a possible LED toggling problem from running the idle loop. If you haven't changed configuration for xdc.runtime.System, you should be able to see System_printf output in ROV, in xdc.runtime.SysMin, in the tab Output Buffer.

0 Ben Duvenage22 over 7 years ago in reply to Sasha Slijepcevic

Expert 1250 points

Hi
Will give a go and give feedback. Thanx

0 Ben Duvenage22 over 7 years ago in reply to Ben Duvenage22

Expert 1250 points

Can now go into the debug code but struggle to find Output Buffer

0 Ben Duvenage22 over 7 years ago in reply to Ben Duvenage22

Expert 1250 points

After I closed CCS and re-opend it I cannot go into the source code for the RTOS any more........Why

0 Ben Duvenage22 over 7 years ago in reply to Sasha Slijepcevic

Expert 1250 points

I dont get the SysMin section you talk about.

In xdc when in debug I have this

0 Ben Duvenage22 over 7 years ago in reply to Ben Duvenage22

Expert 1250 points

Ok have changed my .cfg file to
var SysMin = xdc.useModule('xdc.runtime.SysMin');
SysMin.bufSize = 128;
System.SupportProxy = SysMin;

from this
//var SysMin = xdc.useModule('xdc.runtime.SysMin');
//SysMin.bufSize = 128;
//System.SupportProxy = SysMin;
var SysCallback = xdc.useModule('xdc.runtime.SysCallback');
System.SupportProxy = SysCallback;

Now I can see the Output tab

0 Ben Duvenage22 over 7 years ago in reply to Ben Duvenage22

Expert 1250 points

Ok Finally I can see my Idle loop function is running.

But I would expect it to run continuously.

What I currently see is that my idle loop task gets fired once before the LEDTask and once after the LEDTask.

What Am I missing

Also I see when in debug mode the idle loop is running but when in the board run alone the 2 leds flash at the same rate?

Why?

0 Sasha Slijepcevic over 7 years ago in reply to Ben Duvenage22

TI__Mastermind 37985 points

I have to say first that I am using a different board because I don't have cc1310, but for basic functionality my cc3200 should work just as same. What I am seeing in my example, which I tried to make as close to yours as possible, the LEDTask and the idle loop run continuously, with about eight executions of the idle loop for each loop of the LEDTask.
Your LEDTask is an infinite loop and should run until you exit, which means you should see multiple output messages from it. If it exits after only one output message, something else might be wrong. Can you let it run for a little bit longer? What code is running when you interrupt the execution?

0 Sasha Slijepcevic over 7 years ago in reply to Sasha Slijepcevic

TI__Mastermind 37985 points

Ben,
I talked to a local Power mode specialist and he told me that cc1310 is a little bit different in the sense that you are not going to see the idle loop fire on every clock tick as it happens on cc3200, so normally you would see one run of the idle loop and then one run of the LEDTask, and that would keep repeating. However, there is also this statement
taskParams.arg0 = 1000000 / Clock_tickPeriod;
which seems to set up a fairly long sleep time. Can you make it
taskParams.arg0 = 1000;
and check if you multiple outputs from the idle loop and the LEDTask.

0 Ben Duvenage22 over 7 years ago in reply to Sasha Slijepcevic

Expert 1250 points

Hi Sasha.
I had a look and it seems that what you describe above is fairly close to what I'm seeing.
I have changed some of he timing in the LedTask so that the task runs faster more frequent. An I can now see that my idle loop function behaves more closely to what is expected. It seems that power management must be addressed in the RTOS for the CC1310

0 Sasha Slijepcevic over 7 years ago in reply to Ben Duvenage22

TI__Mastermind 37985 points

Ben,
is your question answered?

0 Ben Duvenage22 over 7 years ago in reply to Sasha Slijepcevic

Expert 1250 points

Hi Sasha
Yes Thankyou
Kind regards

Processors

Processors forum

Ti RTOS cc1310 idle loop function