Can't figure out why program is not running

RE: Can't figure out why program is not running

DJM — Thu, 31 Mar 2016 17:45:26 GMT

Thanks to the comments I was able to use GDB to figure out what was going wrong.

I stupidly had the wrong RAM length in my linker. Changed to the following and it now works:

MEMORY
{
  FLASH (rx) : ORIGIN = 0x1b000, LENGTH = 0x25000
  RAM (rwx) :  ORIGIN = 0x20002080, LENGTH = 0x5f80
}

RE: Can't figure out why program is not running

Anders Strand — Tue, 29 Mar 2016 12:43:39 GMT

See this to see how to use the error handler.

RE: Can't figure out why program is not running

RK — Mon, 28 Mar 2016 02:21:46 GMT

Put a breakpoint in the app_error_handler() as it's fairly likely you're ending up there. Then trace back to find out which api call returned an error and why.

And check out the blog posts about Segger Embedded Studio, it offers a somewhat better debugging experience than gdb over a socket.

RE: Can't figure out why program is not running

DJM — Sun, 27 Mar 2016 15:57:36 GMT

@tasketrond don't think I am. Going to move it up the Makefile to see if it is. It's being loading in the same order as the example application anyway so I don't think it will make a difference. I'm using the S130 SoftDevice which is the same one used in the example.

RE: Can't figure out why program is not running

wlgrd — Sun, 27 Mar 2016 15:33:51 GMT

Are you doing any init before that uses the drv_config.h? Are you using the same softdevice? Different versions has different memory mappings, so you might end up writing your application at the wrong vector