OTA FWU bootloader timeout after SDK v8.1.0 upgrade

RE: OTA FWU bootloader timeout after SDK v8.1.0 upgrade

Nick Pelis — Fri, 22 May 2015 16:49:37 GMT

Yes...that is the key. First you start with SDK 8. Then you create an example project from SDK 8. Go in and check the box. Finally, at a later point in time, you upgrade to SDK 8.1.0. This blows away the configuration file.

RE: OTA FWU bootloader timeout after SDK v8.1.0 upgrade

Hung Bui — Fri, 22 May 2015 15:12:23 GMT

I checked the check box but still couldn't reproduce it. Maybe it must be checked before I update the packs. I will keep an eye on the issue to see if other people have the same problem. Thanks for sharing.

RE: OTA FWU bootloader timeout after SDK v8.1.0 upgrade

Nick Pelis — Thu, 21 May 2015 18:42:28 GMT

Thanks @Hung for looking into this. BTW the key difference between the example bootloader and my configuration is this little check box in the Keil Pack Selector to use the latest versions of all software packs:

I think what happened is that when I upgraded my Keil packs, Keil automatically deleted the original hci_mem_pool_internal.h (which was specially modified for the DFU bootloader) and replaced it with the stock version.

It would be much better from a code management perspective if Nordic moved all project-specific configuration values (like the contents of nrf_drv_config.h, hci_mem_pool_internal.h, and twi_master_config.h) out of the SDK packs and into each example project's source code. From my perspective, everything in the SDK should be considered read-only unless I have a very very good reason to change it.

RE: OTA FWU bootloader timeout after SDK v8.1.0 upgrade

Hung Bui — Thu, 21 May 2015 14:57:41 GMT

@Nick: RX_BUF_SIZE = 600u , is the configuration for the serial DFU. Are you sure you selected the dfu_transport component with BLE variant instead of serial variant ?

Could you let me know how do you clone the project from packs ?

I tried here but couldn't find the wrong configuration as you posted.