What does it mean when debugger head lands on 0x00000000?

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Tue, 04 Apr 2017 00:31:59 GMT

Ok, I have been going through some more research on the settings that this chip requires and what the soft device requires. Since it is the s130, I looked at the infocenter pdf for the softdevice specification, made sure that the ram and rom memory locations in the project options matched correctly on the starting locations, then I made sure that the ram didn't exceed what the nrf51822qfaa indicated it had which was 16kB of ram. Since the softdevice was using 5kb of ram, I set the application to use 10 kb of ram so the size is at 0x2800 and then I set the crystal to 16MHz according to the spec sheet from the company in china, and now when I run it, it actually landed on the app_error_handler function with the line number error code and file name information. Yay!

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Mon, 03 Apr 2017 23:48:37 GMT

I think part of it might be because the oscillator wasn't correct in the project options, however I tried it on 16MHz and 32MHz and it still doesn't work for this board (which I think is just using the internal oscillator, but I am going to double check). When I changed the oscillator value for the devkit, everything worked fine, but before hand the example projects had the wrong oscillator values and they were not working properly on the nrf51 devkit board (weird considering that the example projects are built for the devkits).

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Mon, 03 Apr 2017 22:11:22 GMT

Yeah, I am flashing it with s130_nrf51_2.0.1

RE: What does it mean when debugger head lands on 0x00000000?

Daniel Wang — Mon, 03 Apr 2017 22:09:12 GMT

Have you flashed the soft-device? You should flash soft-device S130 v.2 if you use sdk 12.2. You can flash the softdevice using nrfjprog command-line

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Mon, 03 Apr 2017 18:33:01 GMT

Well, I just answered that question. I put in 'DEBUG' in the pre-processor symbols and it calls the app_error_handler function instead now and still doesn't call it before hitting 0x00000000.

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Mon, 03 Apr 2017 18:29:28 GMT

I just tried putting a break point on the app_error.c app_error_handler_bare (the other one wasn't compiled in) function and it doesn't appear to be called before 0x00000000 gets targeted. Is this because I am not using the app_error_handler instead of bare?

RE: What does it mean when debugger head lands on 0x00000000?

Tyler — Mon, 03 Apr 2017 18:16:32 GMT

Thanks for the link to that thread, I'll take a look at it. I am actually developing on a board from a manufacturer who makes watch devices in china and sells to whoever. I actually just opened up an nrf51422 devkit (hopefully the model difference won't throw off what I learn too much) so I can load my firmware onto there and activate some pins for uart to debug with.

RE: What does it mean when debugger head lands on 0x00000000?

Daniel Wang — Mon, 03 Apr 2017 18:13:10 GMT

I think that means that the program is reset. After a reset, the vector table is usually defined at the start of the memory space (address 0x00000000).

Have you tried debugging? devzone.nordicsemi.com/.../

Are you using a nRF51-DK? If so, it should not have been necessary to change target device...