SoftDevice does not call the registered callback

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Wed, 12 Apr 2017 06:49:16 GMT

it is exact same problem you have Marcel? same sdk and softdevice versions?

RE: SoftDevice does not call the registered callback

Marcel — Wed, 15 Mar 2017 10:20:29 GMT

It has been a year now, but is there a solution to this? I have the same probleme :\

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Tue, 08 Mar 2016 12:05:45 GMT

Hi,

The RAM base address is defined by the settings in your sd_softdevice_enable. Since some of the features are runtime configurable, please read the migration documents which explains very clearly of what RAM base setting you need to use.

Migration document can be found in the zip file here. In migration document it give you an example how to find the RAM base address.

RE: SoftDevice does not call the registered callback

gaurav banyal — Fri, 26 Feb 2016 15:07:26 GMT

After further investigation I found out that it is dependent of RAM usage settings. When I change the base address for the APP to a greater value, it works fine. Now, I want to know what is the right value of the IRAM1 "start" address. All examples in the SDK use the address 0x20001D80 but the S132 documentation suggests that APP_RAM_BASE should be min 0x200022D8 when S132 is used. Which one is correct and why? BTW, for me it works when the IRAM1 start address is set to 0x200022D8 in the project settings in Keil. The value 0x20001D80 that is used by the example projects is not mentioned anywhere in the documentation.

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Thu, 25 Feb 2016 10:18:43 GMT

I am nordic employee and I have an NDA when you share information with me. So it is still ok to send me proprietary information. Ill send you pvt msg on more info. I am suspecting some thing is wrong in your proprietary code, so ripping it off might hide the problem.

I would try to debug and step into the function softdevice_sys_evt_handler_set to see if the sys handler has been successfully set inside softdevice. And after that I will set a breakpoint in softdevice_handler.c: SOFTDEVICE_EVT_IRQHandler to see if this is getting called at all or not? if not then we should figure out if there are any other higher priority tasks in your proprietary protocol which is starving this task.

RE: SoftDevice does not call the registered callback

gaurav banyal — Thu, 25 Feb 2016 09:47:25 GMT

I can send you my .c file with proprietary information removed. Would not be able to send the whole project as it already contains a lot of proprietary information. Will that help? How do I send it to you?

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Thu, 25 Feb 2016 09:32:06 GMT

Then it should be some thing in your source code. Are you sure there are no failures (errors returned by any function)?. Are you checking all error returns and handling them ? I would be interested to get your project and see this myself. Is that possible?

RE: SoftDevice does not call the registered callback

gaurav banyal — Thu, 25 Feb 2016 09:25:18 GMT

NordicSDK\nRF5_SDK_11.0.0-2.alpha_bc3f6a0\examples\ble_peripheral\ble_app_hrs\pca10036\s132 Works perfectly on the development board. I have copied this to my source code and removed the simulation code. Not much changes.

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Thu, 25 Feb 2016 09:20:58 GMT

which example you say is not working?

RE: SoftDevice does not call the registered callback

gaurav banyal — Thu, 25 Feb 2016 09:17:33 GMT

Hi Aryan,

Thanks for your response. I am using nRF5_SDK_11.0.0-2.alpha_bc3f6a0 and s132_nrf52_2.0.0-7.alpha_softdevice.hex. I am testing this both with breakpoints and serial port prints. Another fun fact is that the example HRM application from the same SDK runs fine on the PCA10036 development board.

RE: SoftDevice does not call the registered callback

Susheel Nuguru — Thu, 25 Feb 2016 09:12:04 GMT

That is not possible. Which SDK and SD version are you using? I can run a quick test. Also are you testing this by breakpoints or serial port prints?