Hello Nordic team,
I just post a message here to take the temperature, and your respective engineering opinions about that…
It's been a few months that I work on the development of our IOT and we have therefore chosen, and been well advised, for our Bluetooth base to go with Nordic, very good choice as much for the quality of the SDK, the Chip and the ecosystem.
A few months ago, I started to go on the SDK12.2, our device is functional as such and we use roughly the following stack:
- ANCS
- UART/NUS
- DFU Button Less
- Libs for MEMS
But, for example, there is some of this: one of your engineer, in the past, told me in a post (devzone.nordicsemi.com/.../ >> "Q2") that I was lucky that the buttonless DFU works because it was clearly still unstable on the V.12.X…
and also, just recently, I have discovered a nice x7 consumption bug of the electric current after making a division floating in my code (devzone.nordicsemi.com/.../) that I saw to counteract serious to this little hack in the power_manage(void)
As we wanting to incorporate some new feature into our existing code (send HID frames to our device connected to our IOT Object) and at the same time incorporate DualBank OTA and also make some TimeSlot (broadcast beacons frames at the same time we are in connected mode with an iOS ...)
It come to me that it's maybe the right time to migrate all our SDK12.2 code on the new SDK14 (I read somewhere that the DFU OTA Buttonless had finally arrived at maturity of production)
—> Do you see obstacles to this move, pitfalls to avoid or points of friction on this transition?
So It should update, for this next OTA which will therefore be done in 'Button Less' update on our existing devices at our customers, the three layers :
Bootloader + SoftDevice + App,
—> Will be there any problem with that?
—> Do you recommend the version SDK14 or SDK14.1?
Thank you for your estimates and have a good day
