Problems when using OTA DFU and 2.4Ghz RF at the same time

[nosebooster]

Hi guys!

I am making an application that uses the PCA10056 for 2.4Ghz RF communication using Enhenced shock burst(esb).

Also, when upgrading the application, i try to use Bluetooth communication with OTA DFU.

So I created a 2.4Ghz RF communication program using the proprietary_rf project, which is one of the examples in the nRF5_SDK, and it works well.

And I did the secure_bootloader example of nRF5 SDK to do OTA_DFU, and uploaded the application using Andriod cellphone. This also works well.

However, putting both 2.4Ghz RF file and OTA DFU file in flash does not work. (2.4Ghz RF application + OTA DFU bootloader + S140 Softdevice)

-->bluetooth is only used in debugging mode. When not in debugging mode, 2.4Ghz RF communication is used.

I found OTA_DFU to use s140 softdevice while I was trying to solve the problem, and I found that s140 is a file for bluetooth communication.

So what can I do to make a product capable of OTA_DFU and capable of 2.4Ghz RF communication? Is this possible?

Thank you.

[Hung Bui]

Hi, 

 

You are correct, in order to use BLE DFU you would need the BLE stack (softdevice). You can use your application with the softdevice without any modification in the code. You just need to move the flash address of the application to after the softdevice. Similar to what the \examples\peripheral\blinky\pca10040\s132 does but for the S140 softdevice. 

You can test first with just the softdevice and the RF application. After it worked you can use BLE DFU bootloader to upload the application to the chip (instead of flashing application using programmer). 

Another thing you need to think of is how to put your device to bootloader mode. By default what you need to do is to hold button 4 when resetting the device.