• State Verified Answer
  • Replies 2 replies
  • Subscribers 91 subscribers
  • Views 1128 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 315196
Options

Porting nRF52840 to nRF5340

MKJ

We have a system that uses the nRF52840 chip and we have our fimrware running under FeeeRTOS and SDK version 16.0.0; it would be reasonably straightforward to move to the latest SDK (17)

We are investigating porting our code to the nRF5340 which, of course, has a different architecture:

1) Although I see that Zephyr is the favoured OS for the nRF5340 is FreeRTOS also ported/available?

2) Is the SDK for the nRF5340 compatible with that of the nRF52840 at the API level? [Clearly we want to use the Nordic soft device as we do at present]

Parents
  • +1

    Hi Martin,

    1) Although I see that Zephyr is the favoured OS for the nRF5340 is FreeRTOS also ported/available?

    The only SDK we deliver that has support fort the nRF5340 is nRF Connect SDK. Zephyr is a key component in this and cannot be replaced by another RTOS. I recommend taking a look at the nRF Connect SDK and nRF5 SDK statement.

    It is theoretically possible to use FreeRTOS on the nRF5340, but that would require a significant effort by you, as you will have to live without an SDK (though we have low-level drivers and some libraries that is platform in dependent). You will also have to write your own or find another Bluetooth stack, though you could potentially use our SoftDevice Controller which implements the link layer only. In practice, this will likely be be much more work than porting your existing application, and you will be more or less on your own, so I wot not recommend this approach.

    2) Is the SDK for the nRF5340 compatible with that of the nRF52840 at the API level? [Clearly we want to use the Nordic soft device as we do at present]

    No. The APIs in the nRF Connect SDK are generally Zephyr based, and this also applies to the Bluetooth APIs. So porting an application from the nRF5 SDK to the nRF Connect SDK does in practice involve a re-implementation. However, the advantage is that you will have a stable API going forward that will be supported for many, many years, and Zephyr is also becoming more wide-spread in the whole industry.

Reply
  • +1

    Hi Martin,

    1) Although I see that Zephyr is the favoured OS for the nRF5340 is FreeRTOS also ported/available?

    The only SDK we deliver that has support fort the nRF5340 is nRF Connect SDK. Zephyr is a key component in this and cannot be replaced by another RTOS. I recommend taking a look at the nRF Connect SDK and nRF5 SDK statement.

    It is theoretically possible to use FreeRTOS on the nRF5340, but that would require a significant effort by you, as you will have to live without an SDK (though we have low-level drivers and some libraries that is platform in dependent). You will also have to write your own or find another Bluetooth stack, though you could potentially use our SoftDevice Controller which implements the link layer only. In practice, this will likely be be much more work than porting your existing application, and you will be more or less on your own, so I wot not recommend this approach.

    2) Is the SDK for the nRF5340 compatible with that of the nRF52840 at the API level? [Clearly we want to use the Nordic soft device as we do at present]

    No. The APIs in the nRF Connect SDK are generally Zephyr based, and this also applies to the Bluetooth APIs. So porting an application from the nRF5 SDK to the nRF Connect SDK does in practice involve a re-implementation. However, the advantage is that you will have a stable API going forward that will be supported for many, many years, and Zephyr is also becoming more wide-spread in the whole industry.

Children
Related
Terms of service