Hi, is there any preferred mode of profiling port code to validate performances after making changes or it all depends on the targeted architecture? I am currently working with Armv7-A and I could not find anything suitable other than Gprof and cycle counting with PMU.
Tracelyzer is another option you can look at - New free trace tool from Percepio.
1 Like
@Matth9814,
There is also Run Time Statistics - FreeRTOS™, though this is more for identifying task resource usage - not necessarily profiling a specific FreeRTOS-Kernel port.
1 Like
Thank you for the suggestions and sorry for using this thread for a different question but it is somewhat related to the previous one. I also need to test the same port code and I was wondering if I can just modify one of the available demos for this purpose or if there are some other tests I should execute.
You can use these tests. Here are the instructions about how to create a project to run these tests - FreeRTOS/FreeRTOS/Demo/ThirdParty/Template/README.md at main · FreeRTOS/FreeRTOS · GitHub .
1 Like