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.

Reuse BLE stack across multiple application images

Hi Forum,

Since the BLE stack takes up about 95k of space and using the OAD feature roughly halves the amount of code memory available, I was wondering if anybody has experimented with modifying the linker files to put the BLE stack in a known segment of code memory and sharing it between two application images (referred to as IMGA and IMGB in TI's examples).

In my application I can eke out enough code space by making IMGA and IMGB unequal sizes - roughly 100k for IMGA and 150k for IMGB.  It just seems like a waste to have 95k of redundant code.

So - has anybody shared a BLE stack between multiple images?

Best

~James

  • Hi James,

    Updating Application only is a feature that has been requested by many and it's something we are looking into. The initial idea for the OAD feature was to be able to update the complete package including newer stack builds.

    The ideal scenario would be a dynamic solution with multiple stacks and/or multiple applications. I'm not anticipating such a solution for CC254x in the short term but it's a really nice feature.

    Keep us updated if you are progressing!

    Best Regards

    Joakim