Hello,
I currently use the FreeRTOS plugin Under Eclipse Neon, with the arm tool chain on an STM32F769I processor. I use a Jlink PRO debugger with the latest firmware available.
The plugin works very fine, congratulation to the development team and is very useful for multitasking debug.
But a problem occurs if I stop the debugger before the FreeRTOS kernel start. Of course at that time the thread information can’t be loaded but the problem is that the debug stack is no more actualized at all.
It seems that the plugin fail to retrieve the thread info and block the entire stack debug window update.
Here is what appends when I put a breakpoint before the call to “osKernelStart”:
Starting target CPU...
...Breakpoint reached @ address 0x08017E10
ERROR: FreeRTOS maximum used priority is unreasonably big, not proceeding: 80000001.
Reading all registers
Read 4 bytes @ address 0x08017E10 (Data = 0xFE56F7E9)
Reading all registers
Removing breakpoint @ address 0x08017E10, Size = 2
Removing breakpoint @ address 0x90019A4E, Size = 2
Removing breakpoint @ address 0x9001CF16, Size = 2
The same thing appends if the processors fall in Hard Fault Handler for example. It is then impossible to continue any debug under Eclipse
Version used :
Ecplise Neon CDT: 9.2.1.201703062208 (64bit, Windows 7)
ARM Compiler for MCU 1.15.0.201708311556
GNU ARM C/C++ J-Link Debugging 4.1.4.201704251808
GNU MCU C/C++ J-Link Debugging 4.2.1.201711101735
Seeger JLink V6.22b
Is there any workaround to be able to debug when the thread information retrieving process fails?
Thanks in advance
I currently use the FreeRTOS plugin Under Eclipse Neon, with the arm tool chain on an STM32F769I processor. I use a Jlink PRO debugger with the latest firmware available.
The plugin works very fine, congratulation to the development team and is very useful for multitasking debug.
But a problem occurs if I stop the debugger before the FreeRTOS kernel start. Of course at that time the thread information can’t be loaded but the problem is that the debug stack is no more actualized at all.
It seems that the plugin fail to retrieve the thread info and block the entire stack debug window update.
Here is what appends when I put a breakpoint before the call to “osKernelStart”:
Starting target CPU...
...Breakpoint reached @ address 0x08017E10
ERROR: FreeRTOS maximum used priority is unreasonably big, not proceeding: 80000001.
Reading all registers
Read 4 bytes @ address 0x08017E10 (Data = 0xFE56F7E9)
Reading all registers
Removing breakpoint @ address 0x08017E10, Size = 2
Removing breakpoint @ address 0x90019A4E, Size = 2
Removing breakpoint @ address 0x9001CF16, Size = 2
The same thing appends if the processors fall in Hard Fault Handler for example. It is then impossible to continue any debug under Eclipse
Version used :
Ecplise Neon CDT: 9.2.1.201703062208 (64bit, Windows 7)
ARM Compiler for MCU 1.15.0.201708311556
GNU ARM C/C++ J-Link Debugging 4.1.4.201704251808
GNU MCU C/C++ J-Link Debugging 4.2.1.201711101735
Seeger JLink V6.22b
Is there any workaround to be able to debug when the thread information retrieving process fails?
Thanks in advance