Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

Petter Myhre — Wed, 07 Oct 2015 12:31:25 GMT

So proximity from SDK 8.0.0 works. Then you have taken that example or ble_app_template from SDK 8.0.0 and added some custom services. This shouldn't affect anything inside ble_stack_init();, but there must be something that is different betweent the two applications. Maybe you could upload your complete project so we can test it here?

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Wed, 07 Oct 2015 04:54:51 GMT

I think You got it your last line sir.... It never returns when it get inside the sd_softdevice_enable function.. OK Can you guide me where I can be wrong with Softdevice.. Because I am using everything as shown in Document. I am using nRF51-DK Hardware Kit and S110 softdevice version 8.0.2.

One more thing If Softdevice compatibility is the only issue than why Application like Proximity run perfectly with same Softdevice.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Wed, 07 Oct 2015 03:56:39 GMT

I really don't understand what you're saying, sorry I just don't understand some of the English.

You're saying you fail in side the sd_softdevice_enable() function, well that's far before any services are added. So how can it have anything to do with the services?

If the chip REALLY is resetting inside the call to sd_softdevice_enable() then you have serious problems and that really sounds like you don't have the correct softdevice on the chip or you don't have it on there properly. I assume this is very close to the start of your main() routine. You're telling me that if you put a breakpoint RIGHT after the sd_softdevice_enable() call, in the assembler if necessary, that it never returns from there and the chip resets?

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Wed, 07 Oct 2015 03:45:25 GMT

Yes I have added my own Error handler there, but execution point may be not reached till that point. Because if it reached there till my error handler than also print the printf statement there. But it reset somewhere inside the sd_softdevice_enable Function which is simply an API, under SVCALL. SO I cant see what is happening inside there... Please clear my one doubt. As I have added three customized services and three characteristics for each services. May be this the main issue?? anything happening inside the sd_softdevice_enable function which is hardwired but I may be providing excessive values to any related parameters.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Tue, 06 Oct 2015 13:33:22 GMT

.. and if you've single stepped all the way to the line err_code = sd_softdevice_enable(clock_source, softdevice_assertion_handler); what is err_code? If it's not zero, you have an error and APP_ERROR_CHECK() is going to fail on the very next line.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Tue, 06 Oct 2015 13:25:09 GMT

One of the default error handler functions does reset the chip, which is why I suggested putting a breakpoint in the function before it does anything to see what the error code is. Or write your own error handler function which loops and you can break into it.

Usually the error handler is only defined to reset the chip in release code, but I don't know what flags you've built with so it's possible you have the 'reset the chip' error handler.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Tue, 06 Oct 2015 13:21:40 GMT

yes that two line has nothing to do. I am just to annotating a point so you can easily get it where I am stuck.

Look that things goes inside the stack_init function

there it is defined as err_code = sd_softdevice_enable(clock_source, softdevice_assertion_handler); APP_ERROR_CHECK(err_code);

which means I am calling an error handler function. But things happened here is when this Function get call it won't get inside this error handler (APP_ERROR_CHECK) it reset the program.

Softdevice and Application IROM and IRAM memory allocation is correct. Cause I did the same As it was shown in case of proximity service , which come within the SDK.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Tue, 06 Oct 2015 12:15:10 GMT

No i would doubt it. In fact those two lines of code wouldn't really compile down to anything which does anything much. Just moves the address of and size of a chunk of statically allocated memory into program memory somewhere.

Do you have an error handler? Put a breakpoint in that as well to check something else isn't landing you in there. None of the places highlighted so far are places which could send the chip into reset (and hence start main() again)

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Tue, 06 Oct 2015 12:02:13 GMT

Yes Softdevice Address is correct . I downloaded Softdevice first into Board than the application code. And same I checked with nRFGO studio everthing is fine.

The functions mainly stops after setting this two parameter inside the ble_stack_init_function() mp_ble_evt_buffer = (uint8_t *)p_ble_evt_buffer; m_ble_evt_buffer_size = ble_evt_buffer_size;

Is any issue with size??

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Tue, 06 Oct 2015 11:43:49 GMT

Yes ofcourse advertsing thing is irrelevant point here. As I am stuck somewhere inside SOftDevice. Thing is that is stuck at function which defination is abstracted. SO I cant add there any printf to look more. What is happening when it reached to that functions it immediately start executing from main() function

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Tue, 06 Oct 2015 10:51:31 GMT

Did you actually build your code with the correct addresses to use a softdevice and put the correct softdevice on the chip?

Do you check the error code or you don't even get that far?

If you put a breakpoint on the printf() function does the code break there?

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

SHubham — Tue, 06 Oct 2015 10:47:53 GMT

When execution point reached to this function ::::::::: err_code = sd_softdevice_enable(clock_source, softdevice_assertion_handler);

I added a printf function just below this function is also not get executed. It terminates everything at this point. and main() function starts again.

RE: Device is not advertising stuck at SOFTDEVICE_HANDLER_INIT Macro

RK — Tue, 06 Oct 2015 10:45:26 GMT

It doesn't 'stick' somewhere, microprocessors don't just stop running. You have a debugger, hit 'break' and see where you are in the code. Most likely you are in the error handler because one of the calls inside the handler init returned an error, the error was checked and the code jumped to the error handler, where it's looping quietly waiting for you to hit break, look at the stack trace, and see what caused the error.

If you're stuck in the softdevice init and haven't even returned from that, the advertising stuff isn't really relevant as you won't have got to that point in the code. However if those are 3 custom services with full length UUIDs, there's no way they are going to fit in the advertising packet, and that will be the source of another error later.