[SOLVED] Ozone, ThreadX, Trace, and the call stack

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Ozone, ThreadX, Trace, and the call stack

    I am using Ozone + J-Trace Pro on a target that is running ThreadX, and I am seeing some pretty crazy results on the Timeline view. Unfortunately, the only environment I know of with a ThreadX awareness plugin is IAR, which this project is not set up for. Image 1 shows what I am seeing at some places; note the deep stacking of the same function (a while loop waiting on a queue).

    Is it expected that the stack unwinding for Timeline view will not be able to decipher the context switches?

    Of course, it is possible that I am actually catching a major error of my own here ...
    Images 2 and 3 show what a return look like in a case where the Timeline believes that it has returned to a function stacked upon itself, and the corresponding instruction trace.
    Images
    • Screen Shot 2018-02-02 at 3.50.17 PM.png

      124.44 kB, 1,052×738, viewed 98 times
    • Screen Shot 2018-02-02 at 4.43.58 PM.png

      75.43 kB, 1,051×747, viewed 84 times
    • Screen Shot 2018-02-02 at 4.44.03 PM.png

      195.58 kB, 524×1,107, viewed 88 times
  • Hi,

    Thank you for your inquiry.
    ThreadX task awareness is not natively supported by Ozone. Ozone does not know when tasks end so they simply get stacked on top of each other.
    More information about OS awareness can be found here: segger.com/products/developmen…echnology/rtos-awareness/

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support contact us per e-mail.
    The following contact form can be used for this: Contact Us