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.

CC2640R2F: Linker file/insufficient memory

Part Number: CC2640R2F

Hi Team,

 

I'm trying to integrate the combined stack/app image with our bootloader (BIM.) Things seem to be mostly working -- but after modifying the linker file etc. the system seems to have insufficient memory (this was not the case before modifying the linker file.) Would you be able to take a quick look at our linker file to see what might be going wrong? I also added the following flags to the project (not sure that FEATURE_OAD does anything, since we aren't using the profile, but stuck it in just in case.) I also added HAL_IMAGE_E to the prebuild step.)

 

Here are the global flags that we've defined:

 

FEATURE_OAD

HEAPMGR_SIZE=0

HAL_IMAGE_E

BOARD_DISPLAY_USE_LCD=0

BOARD_DISPLAY_USE_UART=1

BOARD_DISPLAY_USE_UART_ANSI=1

CC2640R2_LAUNCHXL

CC26XX

CC26XX_R2

DEVICE_FAMILY=cc26x0r2

xDisplay_DISABLE_ALL

ICALL_EVENTS

ICALL_JT

ICALL_LITE

ICALL_MAX_NUM_ENTITIES=6

ICALL_MAX_NUM_TASKS=3

ICALL_STACK0_ADDR

MAX_NUM_BLE_CONNS=1

STACK_LIBRARY

USE_CORE_SDK

USE_ICALL

xdc_runtime_Assert_DISABLE_ALL

xdc_runtime_Log_DISABLE_ALL

  • Hi TI Team,

    I'm closing the ticket above. We got everything working. Here is how the issue was corrected:

    The problem was that the hard-coded SNV page count (from a header file) didn't match the bootloader, and our change to the hard-coded value was marooned on the older stack project. -- the SNV turned out to be the last blocking issue. After we patched SNV header files, and removed the SNV data from the image -- OTA and the reset of the feature set worked.
  • Hi OD,

    I'm glad you figured out your issue. If you have issues in the future, I recommend posting the SDK version you are using as well as which sample app you are evaluating to narrow down any issues.