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.

CCS/CC2650STK: CC2650 build failure

Part Number: CC2650STK
Other Parts Discussed in Thread: CC2640, CC2650,

Tool/software: Code Composer Studio

I am getting the following error.  I switched to CC2640 and built the project.  It was successful.  I then switched back to CC2650 and I am now getting this error...

-l"C:/ti/tirtos_cc13xx_cc26xx_2_20_01_08/products/cc26xxware_2_24_02_17393/driverlib/bin/ccs/driverlib.lib" -l"C:/ti/simplelink/ble_sdk_2_02_01_18/src/rom/common_rom_releases/03282014/common_rom.symbols"
<Linking>
"configPkg/linker.cmd", line 721: warning #10096-D: specified address lies outside memory map
error #10264: DEFAULT memory range overlaps existing memory range RAM

undefined first referenced
symbol in file
--------- ----------------
heapEnd <whole-program>
heapStart <whole-program>

error #10234-D: unresolved symbols remain

error #10010: errors encountered during linking; "sensortag_cc2650stk_app.out" not built
>> Compilation failure
makefile:229: recipe for target 'sensortag_cc2650stk_app.out' failed
gmake[1]: *** [sensortag_cc2650stk_app.out] Error 1
gmake: *** [all] Error 2
makefile:225: recipe for target 'all' failed

**** Build Finished ****

-----------------------------------------------------------------------------------

Suggestions?

  • Duane Perry said:
    I switched to CC2640 and built the project.  It was successful.  I then switched back to CC2650 and I am now getting this error...

    Do you mean that you went into Project Properties and changed the device variant? If so, it is possible that an extra linker command file got added to the project during that process. Please check if the Project Explorer view shows a file named cc26x0f128.cmd or similar inside the project. If it does, you would need to right-click on the file and select "Exclude from Build". Then rebuild your project.

    Let us know if this resolves the issue.