• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 272 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Drawbacks of using multi-role stack in a non-multi role application

Harald Ilg
Genius 3060 points

Other Parts Discussed in Thread: CC2640

Hy,

my project (CC2640, Stack 2.1.1) has several variants, some of them are multi-role (peripheral/central), some of them are not (peripheral). So at the moment, I need to maintain two different stack versions. And I need to OAD stack and application when switching from one variant to another. Is there any drawbacks when using the multi-role stack in the non multi role application? Of course I need to recompile the application, but shouldn't it run without code changes?

Both stack variants occupy the same amount of flash pages, so the size difference doesn't really matter to me. Based on the map file, the multi-role stack need 0x10 byte more RAM (from gap_centdevmgr.o), that doesn't really bother me, either.

How about heap size? Any other disadvantages? Power consumption?

Best regards

Harald

  • 0
    TI__Mastermind 25035 points
    Hi Harald,

    The non-multi role application should work fine on a multi-role stack. Only thing I can think of is the possible increase of dynamic memory allocation. You can profile the heap at runtime and make connections to see the difference in memory usage. Also there are limitations on connection interval when using multiple connections, see here for more details:
    github.com/.../README.md


    Best wishes