[ABANDONED] Bug: breakpoint fails in ISR with FreeRTOS debug

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

  • [ABANDONED] Bug: breakpoint fails in ISR with FreeRTOS debug

    Background: Atollic 9.1, F429 Nucleo with Segger debug stub loaded.
    We'll be using Segger J-Link when production boards show up.
    CubeMX-generated FreeRTOS application.
    6.34h Segger software installed.

    Trying to debug an LwIP problem, but breakpoint does not operate properly.
    When the breakpoint is hit inside an ISR (and FreeRTOS idle, no active task),
    the breakpoint fails to operate properly. The application stops, and a debugging
    failure is reported in the console window (shown below).
    RTOS-aware debugging (RTOS variant) is set to FreeRTOS.
    If I change that to 'No RTOS' the ISR breakpoint works,
    but of course all the FreeRTOS-aware stuff stops working outside the ISR.

    Any idea how to work around this?
    Need the debugger to operate properly at the breakpoint!
    Thanks in advance!
    Best Regards, Dave

    Source Code

    1. [Switching to Thread 1]
    2. Temporary breakpoint 7, main () at ..\Src\main.c:139
    3. 139 {
    4. [New Thread 536873360]
    5. [New Thread 536872096]
    6. [New Thread 536872728]
    7. [New Thread 536877952]
    8. [New Thread 536879560]
    9. [New Thread 536887872]
    10. Program received signal SIGTRAP, Trace/breakpoint trap.
    11. [Switching to Thread 536873360]
    12. prvIdleTask (pvParameters=<optimized out>) at ..\Middlewares\Third_Party\FreeRTOS\Source\tasks.c:3166
    13. 3166 if( listCURRENT_LIST_LENGTH( &( pxReadyTasksLists[ tskIDLE_PRIORITY ] ) ) > ( UBaseType_t ) 1 )
    14. [New Remote target]
    15. [Switching to Thread 536877952]
    16. Invalid selected thread.
    Display All
  • Hello Dave,

    Thank you for your inquiry.
    Could you give the latest J-Link software version a try? Does that change the behaviour?

    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.