Trace "timeline" doesn't make sense

[Chris Ergo]

I am working on customizing the DFU bootloader (to add encryption). When attempting to use the instruction trace in Ozone to debug, I see a lot of nonsense. One example is shown below. It is obviously in a loop (evidenced by the repeated cycle of function names), but they show up in the Timeline as nested functions. There seem to be periods of trace missing (shown as "<unknown>"), during which the instruction address jumps around seemingly randomly. Presumably the missing return's are in these areas.

My current hypothesis is that the SoftDevice disables tracing when execution is in it, which has the side effect of instructions being lost for some period of time before and/or after execution is in the SoftDevice.

Is this true? I don't care about tracing within the SoftDevice, but is there any way to get a more complete trace outside the SoftDevice?

[Aris]

Hello,

I am experiencing the same matter. I want to trace my application and validate it by viewing Ozone's Timeline. However the readings do not make any sense. My view is similar to the one of Chris Ergo. How can I resolve this? Do we have any other updates in the question?

To clarify, I do not want to trace the softdevice calls that are currently shown as unknown. But I want a clear view of the rest of the application. I do not need to set breakpoint and then continue. My intention is to stop the execution at a specific point and view the Ozone's timeline.

Thank you in advance,

Aris.

[Håkon Alseth]

Hi,

 

Aris said:

To clarify, I do not want to trace the softdevice calls that are currently shown as unknown.

This is not possible, as we provide the softdevice only as a binary. To filter out certain contents, I would recommend that you ask SEGGER about if that is possible or not.

 

Kind regards,

Håkon