[SOLVED] More troubles with JLink stack trace (FreeRTOS, KDS)

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

  • [SOLVED] More troubles with JLink stack trace (FreeRTOS, KDS)

    Related to previous post: [SOLVED] JLink stack trace 0xA5A5A5A4
    Freescale K64F, KDS 3.2, FreeRTOS-aware debugging on Windows 8.1, JLink_Windows_V612a

    Thanks to Arne I found and reset a well-hidden size-optimization setting,
    and now most FreeRTOS tasks show accurate call stacks.

    Unfortunately "BT input" task shows incomplete call stack.
    Same project as Arne received last week; just start it and pause.
    Any ideas?
    Thanks as always, Best Regards, Dave

  • Hello Dave,

    to test this, I have disabled the RTOS plugin and single-stepped to the location, the plugin reported as PC when the BT task got suspended. Attached is a screenshot of what I have got.
    I also compared the register values to the values reported from the plugin (these are taken from the stack memory, as the task is suspended there), they are 100% identical. I do not
    know, why the stack trace fails. Just one instruction ahead, it still was fine. But as you can see, this definitely has nothing to do with the RTOS plugin.

    I would suggest you to contact NXP support regarding this.

    Best regards,
    Arne
    Images

    • Debug_Without_Plugin.png

      104.95 kB, 1,214×988, viewed 476 times
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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 you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.