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

NRF connect SDK 52840 and 5340 porting and relation to old sk 15.3

Hi we currently have a product develeped for 52840 on basis of old sdk 15.3.



We are just about to start a new development based on 5340 for which we are required (and want to) to use the new SDK and Zephyr.

So a few questions WRT to process that is recommended to follow....


So new product is going to be an enhancement of our sdk 15.3 based product. So is it easy to port an SDK 15.3 product to the new Zephyr based SDK?
Would we want to do this? Does that make new project a bit of a mish/mash not an ideal new project optimised for use with the  new SDK? Is it not better to start with a clean nrf connect SDK based project?


Old SDK's are depreciated; only path forward is to use Nrf Connect SDK.
Do we do a clean implimentation of the 52840 based product and then port to 5340?
Do we port old sdk 52840 to new SDK, then on to 5340?


Hopefully some of you have some experience here and and can give us some guidance?

Regards,
Owain

Parents
  • Hi!

    I think the answer to this question would depend on how complex your application is. If it's not too much work, I would recommend starting with a clean NCS based project on the nRF5340, to be able to utilize all the functionality NCS has to offer for the nRF5340 and especially use the dual cores on the nF5340. And then back-port to the nRF52840 once this is complete.

    Best regards,

    Heidi

Reply
  • Hi!

    I think the answer to this question would depend on how complex your application is. If it's not too much work, I would recommend starting with a clean NCS based project on the nRF5340, to be able to utilize all the functionality NCS has to offer for the nRF5340 and especially use the dual cores on the nF5340. And then back-port to the nRF52840 once this is complete.

    Best regards,

    Heidi

Children
Related