Segger just released JLink V5.00 and it has this tiny tidbit in it
Firmware: JLink-OB-SAM3U128-mbedBTL-NordicSemi: Updated MSD files for new nRF52 based boards
So we know there are NRF52 boards, they use JLink OB and that hopefully means they are both JLink and MBED enabled. I say hopefully because I never want to use MBED again after the complete utter and total lack of support they have for OSX.
Don't really see your point there, we won't be writing embedded btle apps in Swift, but I do hope Swift 2 is better than Swift 1 which was a disappointing mess. And none of that is related MBED's lip-service-only support for OSX about which I was complaining.
I also note that there are no WWDC sessions this year on Bluetooth. I was hoping for some new API, more control of the connection from within iOS and the splitting up of the Master/Slave and Server/Peripheral connection which CoreBluetooth has perpetuated since the beginning, access to flags and raw data etc. There's no API diffs I can see yet but .. not looking good.
Don't really see your point there, we won't be writing embedded btle apps in Swift, but I do hope Swift 2 is better than Swift 1 which was a disappointing mess. And none of that is related MBED's lip-service-only support for OSX about which I was complaining.
I also note that there are no WWDC sessions this year on Bluetooth. I was hoping for some new API, more control of the connection from within iOS and the splitting up of the Master/Slave and Server/Peripheral connection which CoreBluetooth has perpetuated since the beginning, access to flags and raw data etc. There's no API diffs I can see yet but .. not looking good.
