Lower numbers indicate higher priority. Init defaults to the highest
priority 1 if you don't override CONFIGURE_INIT_TASK_PRIORITY.
You are using events. Probably, the print statement comes after the
event send in your task, and the event send is causing the task to
self-suspend. That's my best
Well, really useful information Chris thanks, no worries about the lack of
documentation completely understandable.
Just let me ask you some more questions
- I´am trying to use it on a raspberry pi 2B, is it currently supported, do
i have to change something on the snippet of code you showed me?.
Yes, of course!
The Init function
rtems_task Init(rtems_task_argument argument)
{
rtems_status_code status;
rtems_name Task_name[TASKS]; /* task names */
rtems_id Task_id[TASKS]; /* task ids */
int i;
all_OK = 1;
g_init_task_id = rtems_task_self();
for(i = 0; i < TASK
On Thu, Apr 30, 2020, 10:14 AM Fernando Domínguez Pousa
wrote:
> Hello,
>
>
>
> I am executing a program which executes four different task with testing
> operations. These tasks were created and launched in this way:
>
>
>
> status = rtems_task_create(Task_name[i], (rtems_task_priority) 2,
> RTE
Hello,
I am executing a program which executes four different task with testing
operations. These tasks were created and launched in this way:
status = rtems_task_create(Task_name[i], (rtems_task_priority) 2,
RTEMS_MINIMUM_STACK_SIZE, RTEMS_DEFAULT_MODES,
(i%2) == 0 ? RTEMS_FLOATING
Hello, Chris,
thanks for testing it right away. It was a stupid mistake on my part, of course.
To get around the build error I had to define macros in the build-script.
“-DHAVE_MKTIME -DHAVE_TIMEGM”
Unfortunately, configure --extra-cflags does not work as expected
So I set CFLAGS before the call
