NCS BLE Project using too much flash

RE: NCS BLE Project using too much flash

Amanda Hsieh — Wed, 04 Sep 2024 17:00:13 GMT

Hi,

Extended Advertising allows for more flexible and robust advertising scenarios. This includes support for larger payloads, which can increase the amount of data that can be broadcasted in a single advertising event and could potentially explain the increased memory usage.

Besides the Memory footprint optimization doc, I don't have extra suggestions for Extended Advertising.

-Amanda H.

RE: NCS BLE Project using too much flash

dlewis — Wed, 04 Sep 2024 16:14:35 GMT

Hi, I've gone through and disabled as many features as I can as well as reducing the buffers to the minimum amounts allowable for the specific project. The amount of additional space saved was less than 50 bytes. Do you know why extended advertising uses an additional 34kb? Is there any ways to reduce this? I am only using about 40 bytes in my advertising data and don't need all 1650, but setting

CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=40
only reduced the flash usage by 1 byte.

RE: NCS BLE Project using too much flash

Amanda Hsieh — Thu, 29 Aug 2024 18:31:31 GMT

Then, you has to consider disable some features or reduce the overall number and the sizes of the Bluetooth buffers.

RE: NCS BLE Project using too much flash

dlewis — Thu, 29 Aug 2024 17:20:16 GMT

Hi Amanda, I have referenced that document. It has a fair bit of overlap with the devzone guide I linked. Unfortunately, adding additional flash is not an option. The hardware is being supplied by the customer and has no option to use a different chip with more flash or add external flash.

RE: NCS BLE Project using too much flash

Amanda Hsieh — Thu, 29 Aug 2024 15:50:51 GMT

Hi,

You also can take a look at the Memory footprint optimization doc. If you already did all to optimize, but still get size overflow. You might consider using an external flash as the secondary slot for BLE DFU or another nRF Chips with larger internal memory.

Regards,
Amanda H.