SYSBIOS - Task Status of all tasks, semaphores, etc..

Hi Hari,

I believe SYS/BIOS does not have any API that will return a list of all tasks. Same is true for Semaphore and mailbox too.

Task_stat() will only return the status (stack size,  priority, stack base, etc) of a single task whose handle has been passed as an argument.

You can always use ROV to view the list of all Tasks, Semaphore, Mailboxes, etc. for debug purposes.

Best,

Ashish

We are on a real platform without using JTAG. We need to have our own debug commands. similar to linux/vxworks relevant to task, semaphores, mailboxes etc.. 

Is there any way I can get information on currently running tasks information? similarly others? 

Regards,

Hari

All modules have APIs similar to the Task APIs below.   Use Task_Object_getCount() to get the number of static (config-time) tasks.  Use Task_Object_get(NULL, index) to retrieve static handle.   Use Task_first() and Task_next() to iterate through the dynamic tasks.

To save memory, the static objects are allocated in an array while dynamic objects are put on a linked list.

Int Task_Object_count();

Here's a simple example. You can follow the pattern for other SYS/BIOS objects. Obviously, adjust dumpTask() to output the data to where it's actually needed.

#include <xdc/std.h>
#include <xdc/runtime/System.h>
#include <ti/sysbios/knl/Task.h>

void dumpTask(Task_Handle task)
{
    Task_Stat stat;

    Task_stat(task, &stat);
    System_printf("0x%x: %s %d %d %d %d\n", task, Task_Handle_name(task), stat.priority,
                  stat.mode, stat.stackSize, stat.used);
}

void listTasks()
{
    Task_Object * task;
    Int i;

    for (i = 0; i < Task_Object_count(); i++) {
        task = Task_Object_get(NULL, i);
        dumpTask(task);
    }

    task = Task_Object_first();
    while (task) {
        dumpTask(task);
        task = Task_Object_next(task);
    }
}

Mark,

  I am looking for Semaphore and Mailbox statistics like the following parameters. On Semaphore, I am unable to get any other info other than "count" using Semaphore_getCount(). Whenever I try to use Semaphore_Object in the application program, it comes with compilation problem when I access elements of this Object. casted to Handle. Pl. advise. 

Regards,

Hari

Hello Hari --

Those data structures are not documented or readily accessible by the application code.  We might change them in a future release.   You should only use APIs to reference the state.

If you must access the internals you can use:

#define ti_sysbios_knl_Semaphore__internalaccess

before the #include <ti/sysbios/knl/Semaphore.h>

But, be aware that these structure elements can change between this release and the next.

-Karl-

Hari,

Karl's right, but you can get most of the status from public APIs without resorting to looking "inside". Here's a (compile-tested) version for the the Mailbox module:

#include <xdc/std.h>
#include <xdc/runtime/System.h>
#include <ti/sysbios/knl/Mailbox.h>

void dumpMailbox(Mailbox_Handle mbox)
{
    System_printf("0x%x: %s %d %d %d\n", mbox, Mailbox_Handle_name(mbox),
                  Mailbox_getMsgSize(mbox), Mailbox_getNumFreeMsgs(mbox),
                  Mailbox_getNumPendingMsgs(mbox));
}

void listMailboxes()
{
    Mailbox_Object * mbox;
    Int i;

    for (i = 0; i < Mailbox_Object_count(); i++) {
        mbox = Mailbox_Object_get(NULL, i);
        dumpMailbox(mbox);
    }

    mbox = Mailbox_Object_first();
    while (mbox) {
        dumpMailbox(mbox);
        mbox = Mailbox_Object_next(mbox);
    }
}

For the Semaphore module, looks like all you can get are the name and count: Semaphore_Handle_name(sem) and Semaphore_getCount(sem).

Mark

I tried Semaphore module. I get a problem with name. 

Semaphores List():
semaphore count event eventId , mode
{unknown-instance-name} 0x8112d780 0x0 0x0 0x1 COUNTING
{unknown-instance-name} 0x8112d798 0x0 0x0 0x1 COUNTING

void dumpSemaphore(Semaphore_Handle sem, int dynSem)
{
Semaphore_Object *semobj;
semobj = (Semaphore_Object *) sem;
st_dpf("%s\t\t0x%p\t\t 0x%X\t0x%X\t0x%X\t%s\n", Semaphore_Handle_name(sem), sem, Semaphore_getCount(sem), semobj->event, semobj->eventId, &semmode[0x1 & (semobj->mode)][0]);
}

2. When I create a semaphore, how do I fill name using the APIs?

Semaphore_Handle semCCreate (int options, int initialCount, char *name)
{
Semaphore_Params semParams;

/* create a Semaphore Instance */
Semaphore_Params_init(&semParams);
semParams.mode = Semaphore_Mode_COUNTING;// FIFO
return(Semaphore_create(initialCount, &semParams, NULL));
}

Hari,

For any SYS/BIOS object, you use the instance->name field of the Params structure. So for your example, add

semParams.instance->name = name;

With this in place, the "unknown-instance-name" will be replaced by your (specified) name.

Mark

Mark,

  Thanks.

    For static definition in the cfg file, how do we get it displayed? (as I showed in the previous picture of .cfg)

   And also is there a API function look for mbx or sem search by Name field? 

Regards,

Hari

Hari,

It's the same for statically created SYS/BIOS objects in the .cfg file. Use the instance.name field of the Params structure:

var task0Params = new Task.Params();
task0Params.instance.name = "task";
task0Params.vitalTaskFlag = true;
Program.global.task = Task.create("&taskFxn", task0Params);

No, there are not any functions to "search" for named instances.

Mark

I able to get for TASKs. But for Semaphores, mailboxes I do not get any name displayed even though I use Semaphore_Handle_name(sem). The problem is for statically defined in .cfg file.

Hari,

The default for static instances is to not include the string name on the target. You will need to enable that for each module you want to keep the names. This was done to minimize (by default) the memory usage on the target. Here are examples for Semaphore and Mailbox instances created in the .cfg file. Note that you only need to enable "namedInstances = true" once. Why does Task work without this? For some reason, a different SYS/BIOS module (Load) is enabling this but only for Task.

Semaphore.common$.namedInstance = true;
var semParams = new Semaphore.Params();
semParams.instance.name = "example";
Program.global.esem = Semaphore.create(0, semParams);

Mailbox.common$.namedInstance = true;
var mailboxParams = new Mailbox.Params();
mailboxParams.instance.name = "super";
Program.global.mbox = Mailbox.create(16, 8, mailboxParams);

Mark

Sorry one more question:

  Is there a way to find out which task has post/Pend Held for Semaphore, mailbox etc.. I see Semaphore displays in the ROV tool as PendedTasks. Is it possible to display these pendedTasks ?

Thanks

Hari

Hi,

Even after giving the name like "semParams.instance->name = name;" I am not getting the name, still its printing the name as Task handle name: {unknown-instance-name}

in code 

Task_Handle task1,task2,task3;
Error_Block eb,eb2;
Task_Params params;

System_printf("enter main()\n");

Error_init(&eb);
Task_Params_init(&params);
// params.instance->name
params.instance->name = "First_Task";
task1 = Task_create(First_Fxn, &params, &eb);
if (task1 == NULL) {
System_printf("1:Task_create() failed!\n");
BIOS_exit(0);
}
Error_init(&eb2);
Task_Params_init(&params);
params.instance->name = "second_Task";
task2 = Task_create(second_Fxn, &params, &eb);
if (task2 == NULL) {
System_printf("2:Task_create() failed!\n");
BIOS_exit(0);
}

----

----

----

BIOS_start();

Please help.

Hi Ramesh,

Have you enabled named instances for the Task module ? If not, you can do so by adding the following code to your application's cfg file:

var Task = xdc.useModule('ti.sysbios.knl.Task');
Task.common$.namedInstance = true;

With named instances enabled, you should start seeing the Task name you set instead of {unknown-instance-name}.

Best,
Ashish

Hi Ashish,

I made the changes and now its displaying the names. Thanks for your help.

With regards,

Remesh

Hi Ashish,

With this method we will get the names of  dynamically created task in their order of creation. Is there any way to know what is the next task scheduled (each task have different priority settings ) ?

With regards,

Remesh N

Hi Remesh,

I am not sure I completely understand your question. Since SYS/BIOS scheduler is priority based, higher priority tasks will run first. Therefore, the next highest priority task is likely to run next. One thing to note is that since SYS/BIOS scheduler is pre-emptive, it is possible that an interrupt comes in and readies a higher priority blocked task. This would result in an immediate switch to the higher priority task. There is no way to predict this before hand, so it is difficult to predict which task will be scheduled next.

Best,

Ashish