• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 3977 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Error: DEFAULT memory range overlaps existing memory range DEFAULT

Trumaner
Prodigy 40 points
Part Number: CC2650STK

Tool/software: Code Composer Studio

Hello,

i have a Problem to build my Project. I've taken the simple ble peripheral example for the CC2650STK and made all files local.

But now I am facing this big issue with the Memory allocation. I get the following error in the linking phase:

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

<Linking>

"configPkg/linker.cmd", line 596: warning #10096-D: specified address lies outside memory map

error #10264: DEFAULT memory range overlaps existing memory range IMAGE_HEADER

error #10264: DEFAULT memory range overlaps existing memory range FLASH

error #10264: DEFAULT memory range overlaps existing memory range SRAM

"configPkg/linker.cmd", line 721: warning #10096-D: specified address lies outside memory map

error #10263: DEFAULT memory range has already been specified

error #10264: DEFAULT memory range overlaps existing memory range DEFAULT

error #10264: DEFAULT memory range overlaps existing memory range IMAGE_HEADER

error #10264: DEFAULT memory range overlaps existing memory range FLASH

error #10264: DEFAULT memory range overlaps existing memory range SRAM

error #10010: errors encountered during linking; "simple_peripheral_cc2650stk_app_local.out" not built

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

I've read some other entries in These Forums, but I couldn't solve this by myself.

in my Project there are several .cmd files, but i don't think they interfere in any way.

/cfs-file/__key/communityserver-discussions-components-files/81/Command_5F00_files.7z

Does anyone have a solution to my Problem.

Thanks in Advance ;)

Kind regards,

Alexander

  • 0
    TI__Guru**** 173310 points

    Trumaner said:
    But now I am facing this big issue with the Memory allocation. I get the following error in the linking phase:

    Could you please post the full output seen in the CCS build console? You could save it off to a text file and attach it here.

  • 0 in reply to AartiG
    Prodigy 40 points

    Sure AartiG.

    Btw I used the devPack Debug Probe from TI.

    Here are my Build Errors that I am facing right now:

    /cfs-file/__key/communityserver-discussions-components-files/81/Build_5F00_Log.txt

    Thanks in advance.

    Kind regards

    Alexander

  • 0
    TI__Guru**** 173310 points

    Trumaner said:
    I've taken the simple ble peripheral example for the CC2650STK and made all files local.

    Alexander,

    Did you make any changes to the example project other than making a local copy of the files? I see in your attached linker.cmd that .resetVecs is allocated to 0x0 while in the example project it is at 0x1010. I believe this address is determined by this build option that is passed to XDCTools in the Project Properties:

     --cfgArgs "NO_ROM=1,OAD_IMG_E=1" 

    Did you perhaps change some of these options? If so, that would impact the generated linker.cmd.

    I would suggest taking a closer look at the example project and comparing it with your copy to see if there are other differences in the build options. 

     

  • 0 in reply to AartiG
    Prodigy 40 points

    Thank you AartiG for your quick Response.

    So now I copied the Content of the cc26xx_app_oad.cmd file from the example to my local Project und added the flag --cfgArgs "NO_ROM=1,OAD_IMG_E=1".

    The error is gone, but now I think it doesn't allocate my code right, because when I Flash my target with it, I won't start Advertising.

    Here is my Build Log:

    /cfs-file/__key/communityserver-discussions-components-files/81/0552.Build_5F00_Log.txt

    Thanks in advance

    Kind regards

    Alexander

  • 0 in reply to Trumaner
    TI__Guru**** 173310 points

    Trumaner said:
    The error is gone, but now I think it doesn't allocate my code right, because when I Flash my target with it, I won't start Advertising.

    Alexander,

    OK so that helped you get past the build error. Unfortunately I am not as familiar with the code and application itself to tell you why the code is not running as expected. The best folks to help with this would be the experts in the BLE device forum. I would suggest posting in that forum and referencing this thread if necessary to give them a background. But they should be able to tell you if the code is getting allocated to the correct addresses or not.