FRDM-K64 break in IRQ

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

FRDM-K64 break in IRQ

跳至解决方案
1,370 次查看
oaf
Contributor IV

I've got into a serious problem today when trying to set a breakpoint in an IRQ function on my FRDM-K64 board.

When the breakpoint is hit the console is continuously showing some read from target, it will not stop

and the stack-frame is only partly filled in namely the function-name of the break-point function

is shown but not the previous ones....

The HDTR Debug [GDB SEGGER J-Link Debugging] JLinkGDBServerCL:

Read 4 bytes @ address 0x0000058A (Data = 0xBC08B672)

Read 2 bytes @ address 0x00000584 (Data = 0xB408)

Read 2 bytes @ address 0x00000586 (Data = 0xB662)

Read 2 bytes @ address 0x00000588 (Data = 0x4790)

Read 4 bytes @ address 0x0000058A (Data = 0xBC08B672)

Read 2 bytes @ address 0x00000584 (Data = 0xB408)

Read 2 bytes @ address 0x00000586 (Data = 0xB662)

Read 2 bytes @ address 0x00000588 (Data = 0x4790)

Read 4 bytes @ address 0x0000058A (Data = 0xBC08B672)

Read 2 bytes @ address 0x00000584 (Data = 0xB408)

Read 2 bytes @ address 0x00000586 (Data = 0xB662)

Read 2 bytes @ address 0x00000588 (Data = 0x4790)

Read 4 bytes @ address 0x0000058A (Data = 0xBC08B672)

标记 (3)
0 项奖励
回复
1 解答
1,235 次查看
oaf
Contributor IV

It seems that the problem is that GDB is trying to get an infinite stack-backtrace.

The solution is to add this command to the Debugger->Commands:

    set backtrace limit 20

Ref:

KDS debug for K22F120M in interrupt enviroment.

在原帖中查看解决方案

0 项奖励
回复
1 回复
1,236 次查看
oaf
Contributor IV

It seems that the problem is that GDB is trying to get an infinite stack-backtrace.

The solution is to add this command to the Debugger->Commands:

    set backtrace limit 20

Ref:

KDS debug for K22F120M in interrupt enviroment.

0 项奖励
回复