• State Verified Answer
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 3224 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 107090
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52 Where to start?

Karel_TandD

A a couple of years after initially giving up on BTLE (due to Apple's refusal to implement reception certain advertising modes) I am back to have another go at it. Basically I am planning to start off with the nRF51822, but when I registered this morning I noticed the big Banner on the nordicsemi home page regarding the nRF52 "Game Changer", details on 17th June.

My question is of course what hardware/firmware should I invest my time in right now, which will give the cleanest transition path to the nRF52 devices. We plan to implement a proprietary data stream to carry or own existing protocol, not dissimilar to the nRF51 IoT SDK idea.

Any hints from someone in the know would be most helpful. Thanks. Karel

Parents
  • 0

    Hi Karel,

    Nordic is pretty secretive about nRF52 so there is basically nothing known except three things:

    • They promise to be again on top in terms of performance and power consumption;)
    • They promise easy migration from nRF51 - but no details if the HW architecture is similar or if this is true only on the Soft Device API level (their BLE stack). If you are using your proprietary radio and/or stack implementation I'd be very careful to extend this claim to your case;)
    • They will tell us everything on June 17 (late afternoon press conference held from Norway).

    So if you must/want start now then go with nRF51 and count that there will be some migration effort needed in H2 if you go to nRF52. Or simply wait one month as we all do;)

    Cheers Jan

Reply
  • 0

    Hi Karel,

    Nordic is pretty secretive about nRF52 so there is basically nothing known except three things:

    • They promise to be again on top in terms of performance and power consumption;)
    • They promise easy migration from nRF51 - but no details if the HW architecture is similar or if this is true only on the Soft Device API level (their BLE stack). If you are using your proprietary radio and/or stack implementation I'd be very careful to extend this claim to your case;)
    • They will tell us everything on June 17 (late afternoon press conference held from Norway).

    So if you must/want start now then go with nRF51 and count that there will be some migration effort needed in H2 if you go to nRF52. Or simply wait one month as we all do;)

    Cheers Jan

Children
Related
Terms of service