Does experimental DFU application use the actual boot loader?

[wim]

Hi

I have been reading a lot of posts and the documentation on DFU for SDK7.2, but something is not really clear to me. When I compile and program the boot loader in my device (and also programmed the S110 soft device), I was able to update the firmware. But now with the experimental added DFU functionality in the application firmware, I am not sure what is really happening. Does it actually use the boot loader? Or is the experimental app doing the firmware update?

I also saw this post: devzone.nordicsemi.com/.../ In there it is said that in order to use it with gcc, the experimental app was not really ported to gcc yet. It said: it has to be in boot loader in order to do DFU. What does this actually mean?

Just or clarity, this is what I would like to do: I would like to be able to use a special characteristic in my service to force the device in boot loader mode, then do firmware update with my own iOS or Android app (into which I have integrated the DFU app functionality), and reset the device, without any hardware manipulation, as I do not have any buttons, and the only way to shut down the device is to take out the batteries, so everything, like e.g. a reset, needs to be done in software. I guess this should be possible with the DFU functionality introduced in SDK7.x.x?

[Hung Bui]

@wim: You still need to flash the bootloader in place.

What we do in the experimental button less project is only to START the bootloader from the application via a characteristic that you can set using your phone, exactly like what you described.

You can have a look at question C in this FAQ.