Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Migrating S112 to S113 and nRF52832 to nRF552840?

I have application developed that works ok on nRF52 DK (nRF52832) with S112 and now want to migrate it to a custom board with nRF52840.

  1. Could you confirm that S113 is applicable to nRF52840, because on this page S113 is listed only for nRF52833?
  2. Is there any migration guide or examples that are written for both S112 and S113 that can ease this migration?
  3. Can the old application with S112 with adjusting only the SOC defines and memory addresses work (at lest partially) on nRF52840 as I see plenty of examples for pca10056e with S112 ?

Thanks

  • Sorry, some misunderstanding - I was asking not how/where in SES to set those values, but how to calculate (and verify after) that the values for heap and stack are good for my application i.e. neither less what I need nor too much unused memory to reserve?

    For the clocks obviously I'll need some more time to research and try myself the proper solution Disappointed

    Thanks

  • Hi,

    There is no easy way to calculate exactly how much stack you need. You could do it experimentally (writing a fixed pattern to RAM and check how

    The FreeRTOS heap is isolated to FreeRTOS and has no dependencies to the toolchain or SDK. The FreeRTOS heap is defined by configTOTAL_HEAP_SIZE and implemented in one of the optional heap implementations in FreeRTOS. Heap usage is often easier to calculate, but that depends on your application. If it is very complicated and allocates and frees memory in a non-deterministic way, then finding the exact required size is difficult. But you should anyway make sure to handle situations where there is no more available heap (so an attempt to allocate memory fails).

Related