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.

CC2652R7: TI-Matter Lock-app uses almost all of available CC2652R7 Ram Space.

Part Number: CC2652R7

Issue:
Our team has extended the TI-Matter Lock-app with a modest amount of additional logic. We were very surprised that along the way we encountered a build failure claiming that we had exceeded the available RAM region. We really hadn’t added that much. Our temporary workaround required reducing the system’s STACK region to give a bit more to the RAM region but we don’t feel confident this won’t show up as a defect down the road. E.g. this change:

$ grep STACKSIZE ~/matter/src/platform/cc13x2_26x2/cc13x2x7_cc26x2x7_freertos_ota.lds
STACKSIZE = 0x700; /* Original TI value was 0x800 */

Question:
Is this a known issue? Are there upcoming plans to reduce the overall footprint of a Matter Accessory implemented on a CC2652R7?

Thanks in advance!
Steve K.

  • Hi Steve,

    It is known that the TI Matter application demos are constrained on memory, for example the default lock-app (MTD configuration with OTA enabled) has been observed to use ~120 kB of RAM out of the total 152 kB available (144 kB SRAM + 8 kB Cache).  During that investigation it was also noted that 50 kB is allocated as heap, but that part of this could instead be used by the application.  Thus I would recommend slightly reducing the TOTAL_ICALL_HEAP_SIZE inside main.cpp to alleviate your RAM overflow.  There are also instructions for Configuring the Cache as GPRAM inside the BLE5-Stack User's Guide, which may be able to be ported to Matter projects (this has not yet been evaluated).

    Regards,
    Ryan