This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF51 or nRF52 in new production design

I have been using nRF51 since 2013 in a lot of product. Haven't paid a lot of attention to nRF52 series because nRF51 has been a working horse and enough for our applications. Now I am just wondering if I need to switch nRF52 before Nordic stops supporting nRF51 series.

I am planning to use nRF52 in my next design. Just want to hear different opinions from other people with more experience on both.

Thanks

Paul

Parents
  • I think going with the nRF52 for the reasons endnode states is the way to fly. Our HW guys absolutely love the lower power consumption. The FW transition took about 1 week flat out to get something running and probably another 1 week total of little odds and ends that were missed in the initial transition. If you do the conversion at the start of a project, you will likely never see an impact on anything other than the tightest of schedules.

    Keep in mind that the initial week of transition included not only going to the nRF52, but upgrading the SDK by about 4 major revisions at the same time.

Reply
  • I think going with the nRF52 for the reasons endnode states is the way to fly. Our HW guys absolutely love the lower power consumption. The FW transition took about 1 week flat out to get something running and probably another 1 week total of little odds and ends that were missed in the initial transition. If you do the conversion at the start of a project, you will likely never see an impact on anything other than the tightest of schedules.

    Keep in mind that the initial week of transition included not only going to the nRF52, but upgrading the SDK by about 4 major revisions at the same time.

Children
No Data
Related