[SOLVED] Time line window main() stack up. Any solutions?

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

  • [SOLVED] Time line window main() stack up. Any solutions?

    With Ozone we have encountered a rather strange display artifact.
    Every time an software interrupt call ends, the whole stack does not drop down one bar, instead one main() gets filled in immediately after the terminated interrupt handler, resulting an ever stacking up main(), see below.
    Is there any way to alleviate the problem?
    Edit: I later found out that this stacking up would only happen during a software interrupt ending, normal interrupt are handled correctly
    And it seems rather bizarre that the sw interrupt ended without PE coming back from the call stack to end it, it just suddenly ended on its own.
    The chip we are tracing is nRF52833 from Nordic, it's a cortex M-4 processor. Is there any explanation as why a sw interrupt would end on its own?
    Thanks.

    The post was edited 5 times, last by cpeng ().

  • Hello,

    Thank you for your inquiry.
    We received your inquiry in parallel via our support system so this thread will be closed now.

    For other users that find this thread:
    Such timeline usually appears when either compiler output with maximum optimization is debugged or if sleep modes/low power modes are used which will result in lost trace data and thus an incorrect timeline.

    Best regards,
    Nino
    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.