Tracealyzer for "FreeRTOS+Trace"

RE: Tracealyzer for "FreeRTOS+Trace"

Susheel Nuguru — Wed, 18 Jul 2018 19:28:17 GMT

Sorry for the late reply, I am on vacation and hence did not have internet access at all times.

Looking at the picture below

The library itself is in FreeRTOS kernel and the application, which does not depend on softdevice resources. So Tracealyzer should work with the softdevice presence. But I am not sure about the statistics it will present. I mean that FreeRTOS port that Nordic has implemented has no clue about the softdevice activity.

Lets assume that there are two FreeRTOS tasks that you are trying to analyze using the Tracealyzer. Lets say that Task A runs for 20 ms and then softdevice steals the CPU for 3 ms to configure for the upcoming RADIO activity and give the control back to the FreeRTOs at which point it will schedule Task B. But your Tracealyzer will definitely show that Task A has been running for 23 ms (Task A + Softdevice run time) instead of 20 ms since it has no clue about softdevice (as this is not running as a task) but it still can see that 23 ms ticks has been passed when it does a context switch from Task A to Task B. I am sure that this will be very confusing data for you.

In short, You cannot get meaningful data without telling Tracealyzer about the softdevice activity, which in turn cannot be done without RK's hacks.

RE: Tracealyzer for "FreeRTOS+Trace"

5upercircuits — Fri, 13 Jul 2018 10:01:40 GMT

Thank you for your answer 🙂

I found the article where RK has provided instructions on getting it to work with hacks. However, I don't feel comfortable applying those hacks and then ship that product. (refer to initial question)

What about Tracealyzer for "FreeRTOS+Trace"? Would it work without any hacks in the softdevice? I only want to analyze the behavior of FreeRTOS (blocking tasks, ressource usage, etc.). To my knowledge, Tracealyzer would be perfect for that.

However, this requires that Tracealyzer works even if the softdevice is present.

RE: Tracealyzer for "FreeRTOS+Trace"

Susheel Nuguru — Fri, 13 Jul 2018 07:01:00 GMT

No, there are no hooks in the softdevice that will allow you to use the SystemViewer. So you cannot use them to analyze softdevice interrupts. But you can ofcourse use it to analyze application interrupts. A long time ago RK has provided some hacks to be able to instrument your whole system using SystemViewer. Maybe you can use that .