Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


Loading

Accessing scheduler list

Posted 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 list

Posted 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 list

Posted 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 list

Posted 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 list

Posted 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 list

Posted 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 list

Posted by dioghenes-0 on May 14, 2017

Really nice, just seen! Thank you all!


Accessing scheduler list

Posted by burry94 on May 24, 2017

Sorry can I ask how did you resolved the problem? How did you modify akernel variable?


Accessing scheduler list

Posted by burry94 on May 24, 2017

Sorry can I ask how did you resolved the problem? How did you modify akernel variable?


[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]


Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019

Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


Careers

FreeRTOS and other embedded software careers at AWS.



FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Renesas

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner