Tasking Library: stopping and starting tasks

I'm stopping and starting tasks in a project of mine during runtime. It works for me, but there is no documentation to this usecase available, so I wanted to check if what I do is allowed and specified behaviour.

Example:

Initialization:

ctl_task_run(&xLED_task, LED_PRIORITY, LEDTask, 0, "LED_task", LED_STACKSIZE, g_anLED_task_stack + 1, 0);

After some time, I stop the task and restart it:

ctl_task_remove(&xLED_task);
// set some new parameters for the task

// restart it:
ctl_task_run(&xLED_task, LED_PRIORITY, LEDTask, 0, "LED_task", LED_STACKSIZE, g_anLED_task_stack + 1, 0);

The task itsself doesn't set any mutexes, so removing it whenever and not running it again is no functional problem.

Another Question:

Calling ctl_task_remove and ctl_task_run from the task to remove/run itsself, does that break something?

Michael Johnson

October 16, 2023 11:47

The documentation states that ctl_task_restore should be used if ctl_task_remove has been used.

ctl_task_remove(ctl_task_executing) == ctl_task_die()

Johannes Schlichting

October 16, 2023 12:14

@Michael Johnson

unfortunately this doesn't do what I want. removing and restoring is more like "pausing". After restore the task starts from where it had been before. Instead I want to abort the task and start again from the beginning.

October 16, 2023 12:25

That should be okay, are finding problems with this?

October 16, 2023 12:35

No, not directly. But I have rare hardfaults who seem to be caused by overwritten memory. So I'm doublechecking everything.

October 16, 2023 12:36

Have you double/triple checked stack sizes.

October 16, 2023 12:50

yes, I did. crossworks has a nice feature that I just now discovered: "Stack Usage" monitor :).

Tasking Library: stopping and starting tasks

Comments

Didn't find what you were looking for?