OTA worked, Now it doesn't. Does the current nRF DFU tools support the BMD-200?

[kvolz]

Hello,

I took this project on about a month ago to do bug fixes within the app. The bugs are fixed but the OTA was not tested for the last 2-3 months. No changes were made in this area and this is the FIRST time doing OTA.

Using the latest nRF Toolbox/DFU (iOS) and the latest nRF Connect (Android), OTA downloads cannot be accomplished. The device connects, then "Enabling DFU Bootloader".. "Starting ?" loop continuously. Downloads via wire are possible.

I have tried:

1. 2 Sets of hardware
2. 2 different ways to get code into the boards by wire (J-Link and USB)
3. Removed and installed the develop environment
4. Went back to code that had working OTA (had to build - still failed)
5. Used old project files for builds (in-case a compiler/linker directive was changed)
6. Use iOS and Android tools

My development (using):
nRF51_SDK_10.0.0 (last supporting of S110):
s110_nrf51_8.0.0:
Keil:

So, the only think I can think of is the DFU tools are no longer compatible. If this is the case, how do I upgrade the code or downgrade the DFU tool?

I'll take any other ideas to fix this that are reasonable in time (< 1-2 days).

Thanks,

Kim

[kvolz]

There were two issues causing this problem.

First: The boot loader was being removed during troubleshooting; therefore, there was nothing to communicate with the phones to accept the OTA update. I'm not sure how the 'application' loads and runs without a boot loader, but it is possible.

Second: The boot loader had to be modified based on: devzone.nordicsemi.com/.../ The area that effected our code was the change to the definition: DFU_APP_DATA_RESERVED

We now have been able to use 2 Android phones and 1 iPhone to do downloads to 11 systems. My counterpart in Poland has an issue with OTA that we are still working on, but, this is the fix for the original question.

Thanks to all that helped!!

[bjorn-spockeli]

Hi Kvolz, glad to hear that you found issues that caused the DFU to fail. Issue 1: You say that the bootloader was removed during troubleshooting, do you mean during debugging? A nRF5x device will jump to the bootloader if it is present(i.e. the bootloader start address is written to one of the UICR registers) otherwise it will jump directly to the application. Issue 2: Are you using pstorage to store application data that you want to be retained during a DFU?

[kvolz]

Hello Bjorn, Thanks for the education on the events after reset!!
1: Yes, I meant debugging. The debugger has a 'erase' feature, it erases the Chip. 2: I'm not educated about the OTA enough to answer this question. I know the boot loader is part of an example as is the main application. The main application started out as a Heart Beat Monitor from the comments that I see in some of the code. Again, thanks for helping and educating me further! - Sincerely, Kvolz

[bjorn-spockeli]

Happy to help @kvolz :) Let me know if there are any other issues.