I'm slowly learning about technology relating to BLE 4.0 and how it all fits with RFduino, Nordic, etc.
I'm trying to find a solution for remote distribution of sketch updates for RFduinos out in the field (i.e. RFduino embedded product we sell to customers). We're trying to avoid needing to include a USB shield and require the customer to download an updated sketch hex file and upload using a custom-written Mac/Windows app (which I have working). Ideally, our product will support OTA application updates as described by Nordic here:https://www.nordicsemi.com/eng/Products/S110-SoftDevice-v7.0
The RFduino demo shown in this thread uses Nordic SDK 4.4.1 and SoftDevice 5.2.1. Is it possible to use SoftDevice 7.0 and take advantage of OTA-DFU?
I realize that I would need to reimplement my RFduino Arduino code using the Nordic SDK. I'm okay with that if, in return, we can get OTA updates of the BLE application/stack. This is a huge issue for a company selling RFduino-embedded product to thousands of customers. Both the added costs of USB connectivity in our RFduino-embedded product AND the added complexity for our customers to have to find a computer, download a sketch update (hex) (and our custom upload app), connect and upload are very significant. I suspect there's a significant cost to development to switch to the Nordic SDK (plus invest in the Nordic Dev Kit, etc.), but we're willing to make the investment if we get OTA updates. Make sense?
Are there any limitations to using the Nordic SDK and SoftDevice 7.0 on an RFduino that would prevent me from being able to implement OTA updates?
I'm learning, so some of what I'm asking may be off track. I appreciate any replies.
Many, many thanks.