The TI E2E™ design support forums will undergo maintenance from Sept. 28 to Oct. 2. If you need design support during this time, contact your TI representative or open a new support request with our customer support center.

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.

CC2642R-Q1: CC2642 non-volatile memory

Part Number: CC2642R-Q1

Hi Team,

Here're few questions from the customer may need your help:

1) There're about 20K of data stored in non-volatile memory. Is it OK to store so much data?

2) How to check how much memory is being used by the user's own ICALL_malloc allocated memory?

3) In which document is the CC2642 Flash distributed? Include NVS, Bluetooth Protocol Memory Footprint etc.?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi,

    1) There're about 20K of data stored in non-volatile memory. Is it OK to store so much data?

    The device has 352KB of Flash that should be shared between the non-volatile storage and the binary. So, as long as the binary size is not too large, you can store this amount of data in flash.

    2) How to check how much memory is being used by the user's own ICALL_malloc allocated memory?

    Please refer to the debugging guide and the functiuon ICall_getHeapMgrGetMetrics

    3) In which document is the CC2642 Flash distributed? Include NVS, Bluetooth Protocol Memory Footprint etc.?

    If you are asking about where you can find the source code owning the data stored in NVS, then you cannot really access it as this code is provided as library. I can only tell you the larger part of the NVS flash consumption comes from the GapBondManager.

    If you are asking about details on the data stored, you can refer to the User's Guide.

    I hope this will help,

    Best regards,