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]

After successful dfu the new application should be started. The services available after an update depend on what you have in it. If there's only Secure dfu service, than it's either the buttonless service (check characteristic name in nRF Connect for Android) which means that your have flashed an app without NUS, or you're still in bootloader mode, that is the app has been rejected by the new bootloader do for some reason. The old app has been removed, a specially if SD's major version has changed, to make space for dual bank.

In nRF Connect it may also be that another tab opened, with the bootloader address. Just close it and use the tab with your old device name. You may also clear cache, select Refresh services in the menu after connecting to your device.

[SK]

I migrated the SDK from 14.2 to 15.3. In v14.2, this DFU process worked fine. That means i have both the services running after DFU process and yes, there was another tab that opened with the bootloader address. 

But with 15.3, i donot see such a thing. SD major is still 132 that i am using with v6.1.1. 

I ran nrfjprog --eraseall before programming the module with merged hex (BL+SD+APP) and then did a reset. Till here, application runs fine. I can see both the services on the nRF Connect. It is only when i try to update the application (creating a package) via OTA DFU, that i see the problem. When i try to connect, i see only Secure DFU service and not the other one. Not sure whats going on :(  

[SK]

Hi,

To make it more clear, application is there is after firmware update. It's just that i see only secure DFU service and not the other one which is weird !! 

Wonder what is causing that? :/

[Aleksander Nowakowski]

Are you sure your device is in app mode, not bootloader mode? Does it advertise with the right name, or DfuTarg?

Make sure you created the zip file using the right application. You may also flash this application using segger, not ota, to verify that it works.

[SK]

Aleksander Nowakowski said:

Are you sure your device is in app mode, not bootloader mode? Does it advertise with the right name, or DfuTarg?

Yes it is in app mode where i see the device advertise by the given application name.

[SK]

Aleksander Nowakowski said:

You may also flash this application using segger, not ota, to verify that it works.

checked. So i programmed the module with BL+SD+APP hex and then via segger i tried to download. Connected to nRF connect and i can see both services. Only after DFU, i dont see both.

[Aleksander Nowakowski]

There's simply no other option. Either you're in bootloader mode with only Secure dfu service, or you're new app contains only the buttonless service. Or it's something with your fw that exposes the other service only in some conditions.

Could you post here the zip file and the hex file to flash on the device for testing? You may send it to my email if you don't want it to be publicly available.

[SK]

Okay will send you the files through email. Could you let me know your email address? But i am using custom board, so pin configurations are different from the nRF52 DK.

[Aleksander Nowakowski]

Send to [email protected].

I hope the pin configuration won't matter.

[SK]

Sent. I hope pins don't matter. Please let me know if there are problems. 

[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?