Need Zepher RTOS porting support for nRF52840 Based Application.

[Srinivas V]

Hi Team,

We build the bare application with nRF52840 Soc with the SDK Version 16 with out any RTOS Layer. We are planning to port our code base to Zepher RTOS layer.

We need the support for basic porting, like any Reference example or any documentation for porting is helpful to us. Please support us for seem less porting without giving any integration issues.

Regards,

Srinivas.V

[Srinivas V]

Hi Simon,

Once again Thanks for your reply.

We will use reference project from NCS only, on top of that we will start our project porting, in this way we can avoid the Zephyr basic things which are already taken care by NCS Layers, till this part i have clarity.

So far our project is built on nRF52840 with the SDK Version 16, when we start porting the HAL(BLE Stack, peripheral Drivers - SPI, I2C, Flash, Gpio's, Timers, RTC) and Application layers to new NCS, what are things we need to take care bothe hal and other layers. Please help us on this aspect it would be helpful to us.

If we want to take the Zephyr based project as Reference project and on top of that we will start our basic porting, in this manner which project us best fit for us.

Mean time i will go through the documentation, will see any clue can i get. Any Zephyr documentation please let us know.

Thanks & Regards,

Srinivas.V

[Simonr]

Hi

Unfortunately there are so many differences between the Zephyr RTOS and the nRF5 SDK that reimplementation will in any case be easier and faster than porting, as things that work in the nRF5 SDK might not work if ported directly to Zephyr. The nrfx libraries/drivers should stay the same though, so only the most basic things really need to be reimplemented if you use our drivers/libraries.

Best regards,

Simon

[Srinivas V]

Hi Simon,

Once again thanks for reply.

Again i am repeating the same questing, If we want to take the Zephyr based project as Reference project and on top of that we will start our basic porting, in this manner which project is best fit for us like which sample project from Zephyr folder , Eg:     Samples/bluetooth,   Samples/application_development, Samples/basic ...etc

Basically we are expecting one ref project which is having the multi tasks and some os internal calls like memory mgmt, semaphore and mutex mechanisms usage etc...

Any way nrfx libraries/drivers should stay the same, only Zephyr related layers going to change the some of the basic things.

Could you please mention the things which we need to take care while porting to Zephyr, apart from nrfx related, it would be helpful to us.

Regards,

Srinivas.V

[Simonr]

Since you're using BLE, I would suggest choosing the BLE sample fitting your application best, and implementing the nrfx drivers you need for your application. The biggest changes are in terms of configurations, etc. as this is no longer done in an sdk_config.h file, but rather prj.conf and Kconfig files. This is better described in our nRFConnect getting started tutorial series.

You also need to note that the Zephyr RTOS doesn't use the SoftDevice, so the BLE/radio functions are somewhat different. 

You also mentioned Direction Finding earlier, which is only supported by the nRF52833, nRF52811 and nRF5340 SoCs. Not the nRF52840.

Best regards,

Simon

[Srinivas V]

Hi Simon, 

Thanks for providing the reply.

We will use BLE Sample as a base project for our application porting.

Why we need to implement the nrfx drivers , those are part of NCS right? 

How to do configurations by prj.conf and kconfig file. 

iF We want to use the Zephyr RTOS with BLE Softdevice how we can use this  combination.

For our application we are going to use the Nrf52833 not nrf52840.

Regards,

SrinivasV