gdb signal SIGTRAP 0x00014fde

RE: gdb signal SIGTRAP 0x00014fde

sam wagner — Fri, 22 May 2015 07:41:46 GMT

Somehow the issue went away and I am not sure why... One thing we fixed was the clock frequency setting since we are using 32MHz crystal on the board and that seems to have fixed several issues.

RE: gdb signal SIGTRAP 0x00014fde

Lilligosi — Tue, 19 May 2015 09:12:32 GMT

Hi. The same thing is happening to me as well. As soon as I start the soft device, run the following code

sd_mbr_command_t com= {SD_MBR_COMMAND_INIT_SD,}; sd_mbr_command(&com)

the code execution will stall. When I break the code manually the instruction pointer seems to be pointing to 0x14fde. I ran the exact same code on two computers and on one the code runs fine but the other it is stalling. The only difference between the two computers is the version of IAR ide that is used to compile the code. The one that works is running on version 7.20.2.7431 but the one that fails on 7.40.2.8570. I am using the same SDK and SD as Sam Wagner

RE: gdb signal SIGTRAP 0x00014fde

Stian Røed Hafskjold — Mon, 20 Apr 2015 12:12:19 GMT

Did you include the -g3 flag in the makefile? Did you run 'mon reset' after load? If you post your .out file I can try it in the debugger here.