Application service UUID gone after secure OTA DFU

[SK]

Hello, 

I am using nRF52832 on SES v4.12 with SDK v15.3 and SD v6.1.1 on a custom board.

Background: 

I want to perform OTA DFU and with that i have two services enabled (secure dfu buttonless and NUS). I was facing OTA DFU issue in which i was getting CRC does not match error. This has been resolved here - https://devzone.nordicsemi.com/f/nordic-q-a/55653/dfu-crc-does-not-match-error

So, i have been able to perform OTA update. 

The package that i created includes BL+SD+APP. 

Problem: 

Once i perform the update and connect again, i only see one service, which is Secure DFU service and the other which is the main application service ID (NUS) is gone. I looked in the forum and found this -https://devzone.nordicsemi.com/f/nordic-q-a/39982/after-ota-dfu-bootloader-application-gone

But i do not quite fully understand as to what is to be done here. Could you please highlight on what is required for a proper DFU process? From what i understand from the post and infocenter that it is still a single update, so BL+SD+APP merged together should work fine internally. 

EDIT:

Zip created has only application hex in it. BL+SD+APP is programmed directly using nrfjprog. 

Please let me know if you require more information. 

Thanks a lot!

-SK

[Aleksander Nowakowski]

Hello, I tried flashing your hex file on nRF52832 DK, but the device does not start advertising.

[SK]

Oh yes! it won't start advertising. Only after there is a button press, it will. :/ 

Do u want me to modify pins for the DK in order for you to test? 

[SK]

Hi,

I noticed something strange though. Wanted to share here. 

Once i program the device through nrfjprog and connect, i see the services as below:

After OTA DFU, when i connect again, i see the service as below: 

I noticed that characteristics for the secure DFU service is not buttonless service anymore and its something that is coming from bootloader (control point and packet characteristics).

Would this give any indication to what might be happening? Any DFU settings that i should enable/disable in sdk config? 

Attached - dfu logs for reference.

DFU_LOG_ISSUE.pdf

[SK]

Hi, 

This is what i tried and now it seems problem is with bond forwarding somehow.

I disabled the bond forwarding support in both bootloader and the application. So, basically this below:

When i tried without bonds, everything is working fine. I can see both services intact and running fine. 

Only when i tried to enable the bond support again, i ran into problems as discussed earlier. 

Attached is the no bonds support DFU log for your reference. DFU_NO_BONDS_LOG_SUCCESS.pdf

[Aleksander Nowakowski]

That means you're connected to the bootloader. In the log you got error 133, could you try repeating the test several times and send log where it went further?