Ble bootloader Dfu not Advertising in Nrf connect

[deepak01]

Hello,

Im New to Nrf51822 im trying with Nrf51822 dfu bootloader dual and single in sdk51 . But after compiling the ble not showing in Nrf connect at all. Whats the IROM and IRAM need to give and also changed Bootloader button to the  D port GPIO also connect the tact switch . Pressed the button when connecting , erazed the program and compiled softdevice and dfu bootloader hex using nrfgo . But not showing in NRF connect not advertising . Anything i missed or any change i need to do.Please Help.

Thanks 

[Einar Thorsrud]

Hi,

I understand you programmed both the SoftDevice and the bootloader, so that should be good. Which SDK version are you using? And which example bootloader project from that SDK?

[deepak01]

[Einar Thorsrud]

That should be all. Is it still not advertising? If not, are you testing on a DK or custom board? If you are using a custom board that does not have an external 32.768 kHz crystal remember to modify the bootloader project to use LFRC instead.

[deepak01]

github.com/.../Bootloader.md did I want to do all this step before compilation, what and all change did I want to do??

[Einar Thorsrud]

I am not sure what you mean. Can you explain in more detail? Regarding the link you provided that seems to contain good information, but you do not need all that to run the DFU bootloader example. 

[deepak01]

I need to get Dfu bootloader in Connect .

I compiled the code in {sdknrf51} examples/Dfu/bootloader/pca10028/ single bank/arm5 no packs in keil.

After that I used that hex in the build in the folder. And updated by erasing all then updated softdevice and then this hex file.

But this case it's not advertising also not blinking led.

That's why for getting that did I want to do all this step in the link for getting the ble Dfu??

I got an hex from single Dfu that done this step or something that advertising. So what I missed and what all things did I want to do in this before this?

Thanks

Deepak

[Einar Thorsrud]

I can see if I find a more detailed step-by-step guide. Which exact SDK version are you using (I understand you are using the eS110 version 8.0.0 SoftDevice, but I also need to know the SDK version)? Also, assuming you have decided to use the nRF51 - why do you not use a more recent SDK if you are starting development now? The most recent SDK with support for the nRF51 is the nRF5 SDK version 12.3.

[deepak01]

But over there only secure bootloader only seen. Sdk 51 what can I do to advertise

[Einar Thorsrud]

SDK 51 is no SDK version. Can you check which version you have? If you want to use the legacy bootloader, that was used up to and including SDK 11. By the way, why do you want the legacy bootloader?

[deepak01]

Sdk11 that's what I'm using, bootloader dfu single bank. Actually I need to send program hex to nrf using Dfu and work that hex in that.

[Einar Thorsrud]

I see. The DFU bootloader in SDK 11 is quite well documented. Can you start by testing the unmodified example on a DK so that you understand the process before moving on to your custom HW? That way we can keep any uncertainty about adaptations to your HW out of the equation in the beginning, reducing the number of unknowns.

[deepak01]

I checked with with single bank for me it's not getting, I tried with other shared hex and softdevice that is working. But in my case it's not working. Other how can I send a work the blink hex in the working single bank what and all things I need to do in that.