SVC Handler Missing

RE: SVC Handler Missing

Amit — Thu, 23 Oct 2014 23:12:26 GMT

Using the latest SDK (6.1.0) and S110 v7, I'm getting this error as well now. I've previously been able to run similar code witht the S110 but not sure which configuration it was. Getting the same error (NRF_ERROR_SVC_HANDLER_MISSING) on an invocation to sd_ble_gap_device_set_name.

RE: SVC Handler Missing

TEJ — Mon, 15 Sep 2014 07:36:24 GMT

It would be great if the header files could contain sdk version info and possibly also sd version.

RE: SVC Handler Missing

Lionel Sacks — Fri, 07 Feb 2014 10:58:18 GMT

Thanks Ole. yes, indeed, I was using the wrong examples... I guess I just didn't scroll down the file menu far enough!

(great support, by the way, thanks again)

RE: SVC Handler Missing

Lionel Sacks — Fri, 07 Feb 2014 10:56:23 GMT

Thanks, I had seen that post... but OM above has the solution!!

RE: SVC Handler Missing

Ole Morten — Fri, 07 Feb 2014 10:53:04 GMT

This is really a completely separate issue, so please post it as a new question, to avoid messing up this one, which already has a clear answer.

However, it sounds as if you may be working with the examples in Board\nrf6310\ble_s110_serialization. Beware that those are not for use with the softdevice, but with the serialization module, as indicated by the folder name. The ones that work with the softdevice are in Board\nrf6310\s110.

RE: SVC Handler Missing

DonalM — Fri, 07 Feb 2014 10:44:12 GMT

Hi Lionel, Instructions stolen from another thread here. BR, Donal

There could be several reasons for this, but the most common two are:

That the chip is in system off. When the chip is in this mode, it is not accessible to the debugger, and hence any download will fail. You can either wake it up in some way (pressing a button configured as a wake-up, reset or similar), or use nRFgo Studio's Recover functionality. If nRFgo Studio finds a programmer, but can't communicate with the chip, it will offer to try a recovery. This will erase all contents on the chip, and in that way ensure that it doesn't enter system off again.
That you try to flash a program on top of the softdevice If you have programmed the softdevice into the chip (which occupies the flash from address 0x0 to 0x14000), and then try to program an application in this same space (i.e. an application not meant for use with the softdevice), you may see this error.

Again, there are two ways to fix this: a. Erase the softdevice. b. Choose the nRF51822_xxyy_s110 target from the dropdown next to the Download button in Keil. All the non-BLE examples in the SDK come with project settings so that they can be used both with and without the softdevice programmed. If you set this to one of the _s110 targets, the application will be moved from address 0x0 to address 0x14000, meaing it will work nicely on top of the softdevice, even though it doesn't use it.

RE: SVC Handler Missing

Lionel Sacks — Fri, 07 Feb 2014 09:57:16 GMT

Hi, I though I'd append this problem here, rather than start a new thread as I'm having similar issues... for SDK 5.1.0, using Keil 5.1 and the _hrs example and _advertising example:

If I load the softdevice 6.0, I get

Error: Flash Download failed - "Cortex-M0"

If I clear the softdevice and download, I get no load errors, get some LEDs (for _advertising); but of course it stops when initialising the softdevice.

I've built for nrf51822_xxab and nrf51822_xxxx - same result.

thanks for any ideas,

RE: SVC Handler Missing

DonalM — Sun, 26 Jan 2014 16:59:36 GMT

Hi There, This problem also got me. NRF_ERROR_SVC_HANDLER_MISSING or 0x01 returned from sd_ble_gap_device_name_set() Donal

RE: SVC Handler Missing

Dalbert — Fri, 06 Dec 2013 09:37:07 GMT

Thanks. I expected it would be something simple that I overlooked. I appreciate your patience...

RE: SVC Handler Missing

Ole Morten — Fri, 06 Dec 2013 09:04:07 GMT

This is the error you will get if you use the wrong softdevice version with the wrong header files.

As stated in the release notes of SDK 5.0.0, it's built for S110 6.0.0, and if you try to use it with 5.2.1, you will see this error. If you want to stay on 5.2.1 (although I can't really see any reason why you would), you should also stay at SDK version 4.4.2 (or possibly later ones in the 4.x.y series).

You can access old versions of downloads by clicking on the version number in the download list on our regular web site.