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

How different is timeslot management in nrf52840 than in nrf51422?

Hello, I understand this may be a very broad question, but I still need to find as much information as I can.

Give a general answer if you'd like to, or a very specific one if you are so inclined.

To help narrow down this topic a bit and give you something to begin with, these are the 2 aspects I'm concerned about the most:

  1. Is the underlying logic (the juggling between user app requested timeslot allocation and a more close to metal, hardware level usage as well as management of the timeslot) in nrf51 still valid in nrf52?

  2. If #1 is true, then how much different are nrf52 timeslot functions when compared with nrf51? More specifically, let's say I have a project which invokes extensively timeslot functions of nrf51 APIs, is it possible that I only need to modify a few function names to get the timeslot part of my project up and running on a nrf52 platform, or better, I don't even have to modify nearly as many function names, if at all?

Please do not feel deterred or discouraged to answer broadly, any information will be greatly appreciated and picked as the final answer accordingly. Consider your answer(s) an index which helps me decide where to look and what to expect.

Parents
  • Hello Mitch996

    As endnode stated the overall API should be the same for S130 and S132. There might have been some changes to the inner workings of how the Softdevice handles the scheduling but it should not be visible from a user perspective.

    As for the chip-side of things, the nRF52 has a faster HFCLK than the nRF51, meaning you can potentially get more work done with the same timeslot duration. The duration of interrupts leading into and out from timeslots are a bit faster on the nRF52 than on the nRF51, see here and here.

    Not strictly related to timeslots but the nRF52 has more interrupt priority levels than the nRF51. Priority level 0, 1 and 4 in the nRF52 is reserved by the Softdevice, while for the nRF51 only 0 and 2 are reserved. This could be worth considering when porting from the nRF51 to 52.

    Best regards

    Jørn Frøysa

Reply
  • Hello Mitch996

    As endnode stated the overall API should be the same for S130 and S132. There might have been some changes to the inner workings of how the Softdevice handles the scheduling but it should not be visible from a user perspective.

    As for the chip-side of things, the nRF52 has a faster HFCLK than the nRF51, meaning you can potentially get more work done with the same timeslot duration. The duration of interrupts leading into and out from timeslots are a bit faster on the nRF52 than on the nRF51, see here and here.

    Not strictly related to timeslots but the nRF52 has more interrupt priority levels than the nRF51. Priority level 0, 1 and 4 in the nRF52 is reserved by the Softdevice, while for the nRF51 only 0 and 2 are reserved. This could be worth considering when porting from the nRF51 to 52.

    Best regards

    Jørn Frøysa

Children
No Data
Related