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

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

bjorn-spockeli — Mon, 06 Feb 2017 15:20:43 GMT

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

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

kvolz — Thu, 02 Feb 2017 15:33:43 GMT

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

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

bjorn-spockeli — Thu, 02 Feb 2017 07:25:51 GMT

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?

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

kvolz — Wed, 01 Feb 2017 23:04:34 GMT

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!!

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

kvolz — Tue, 31 Jan 2017 20:24:42 GMT

Thanks for the suggestion. We will give this a try.

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

bjorn-spockeli — Mon, 30 Jan 2017 12:19:56 GMT

Im not able to identify the nRF51x22 IC that is used. However, our mobile apps are fully backwards compatible with all the bootloaders that we have released. Are you able to perform DFU if you only flash the bootloader and the SoftDevice?

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

kvolz — Thu, 26 Jan 2017 17:05:38 GMT

The markings that I can see: Rigado B M.N: BMD-200 R 001- A06997 AD0B53BF IC:12208A-01 FCC ID:2AA9B03

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

bjorn-spockeli — Thu, 26 Jan 2017 15:10:18 GMT

@kvolz: Can you provide the chip marking of the nRF51x22 that is used in you BMD-200 module? The bootloader in SDK 10 should be able to perform OTA on all generation 3 ICs, see the compatibility matrix found here.

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

kvolz — Thu, 26 Jan 2017 01:00:51 GMT

In my post, I forgot to indicate that the HW is the Rigado BMD-200.