FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [May 2017 Threads] Accessing scheduler listPosted by dioghenes-0 on May 14, 2017 Hi all,
I need to write an application that is able to make FreeRTOS to fail under fixed conditions. To do so I need to access the scheduler List_t structure 'pxReadyTasksLists', in order to get data about TCBs and stacks of the started tasks, but looking at the code, the list I'm interested into is defined in tasks.c and so not visible to the programmer. Is there a good and elegant way to access to those data?
Thank you in advance.
Accessing scheduler listPosted by heinbali01 on May 14, 2017 A quick answer: there are more than 25 trace macros's that you can fill in, for example:
~~~
traceTASKINCREMENTTICK( xTickCount );
traceTASKSWITCHEDOUT();
traceTASKSWITCHEDIN();
~~~
You can define them in your FreeRTOSConfig.h .
Another trick you could do is include your own code into task.c, e.g. after the last declaration and macro definition:
~~~
#include "mytestingmodule.c"
~~~
When you mess up the code, no warranty is given, of course. Good luck
Accessing scheduler listPosted by dioghenes-0 on May 14, 2017 Uhm...there is no way, for example, to modify some field of some elements of pxReadyTasksLists without modifying the code of FreeRTOS? I ask because trace macros allow me only to 'react' to events while I need to access data in writing mode. I have tried with a 'dirty' trick: I have removed the PRIVILEGED_DATA ahead that list, so that it is accessible from anywhere...could it be a good way to proceed?
Thank you a lot.
Accessing scheduler listPosted by heinbali01 on May 14, 2017 It is dirty and risky to write e.g. in pxReadyTasksLists . There are many limitations on what you can do safely. One thing is for sure: things that might go wrong, certainly will go wrong.
The structure and objects have been kept local and static to avoid users from getting access to them.
Accessing scheduler listPosted by dioghenes-0 on May 14, 2017 Ok I will try to reduce as much as I can the modification to the code.
Accessing scheduler listPosted by rtel on May 14, 2017 A header file is included at the bottom of tasks.c that allow additional code to be added into the file specifically so static variables can be accessed during module testing.
Accessing scheduler listPosted by dioghenes-0 on May 14, 2017 Really nice, just seen!
Thank you all!
Accessing scheduler listPosted by burry94 on May 24, 2017 Sorry can I ask how did you resolved the problem? How did you modify akernel variable?
Accessing scheduler listPosted by burry94 on May 24, 2017 Sorry can I ask how did you resolved the problem? How did you modify akernel variable?
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|