project with NUS prevents DFU from advertising

[Richard]

Nrf52/Kiel/SDK11

My application was at the point where I needed to add DFU. Following the examples and SDK doc, I added the files and code needed. It would NOT advertise. So I looked at the examples (eg Heartrate with dfu) and noticed the only difference was the NUS service. I removed it and the DFU finally advertised.

So I add the code back for the NUS and again, the DFU went away. Next, I switched the order of initialization in my serivces_init file, and it appears that the service that is initialized first is the one that gets to advertise.

Finally, I used the heart rate w/ DFU example and added the NUS service, and again, it would not advertise as long as it initialized after the DFU.

Any ideas?

Rich

[Susheel Nuguru]

You have to debug your application to see why it is not advertising, i am guessing that some condition fails and your system is restarting. Please follow this to see if your NUS app is asserting with APP_ERROR_CHECK

[Richard]

I was sure I checked this, but it turns out I was wrong. The NUS service is failing on the call to sd_ble_uuid_vs_add with a NRF_ERROR_NO_MEM error. Now where do I go?

[Richard]

I started looking at the example app (hrms w/ dfu). I added NUS service to this example and it will not advertise it. only the DFU comes up. No errors are generated!!!!

[Susheel Nuguru]

It is not possible that the program is not stuck and still not advertising. Which part of advertising are you talking now, is it NUS advertiser or DFU advertiser that is not working?

[Richard]

To be clear, I simply took the example from examples\ble_peripheral\ble_app_hrs\pca10036\s132_with_dfu\arm5_no_packs, added the NUS service, and the service does not get discovered. I can remove the DFU init from services_init and the NUS is now discovered. SO, when probably should be more correct and say the service is not discovered (which I assumed related to advertising).