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.

Memory conflicts: DEFAULT memory range overlaps existing memory range

Other Parts Discussed in Thread: SYSBIOS

Hi,

I'm creating a new platform for EVM6678LE, due to several memory problems and inconsistencies between the default CCS memory map and the datasheet.

However, I'm getting and linktime:

error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_1
error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_2
error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_3
error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_4
error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_5
error: DEFAULT memory range overlaps existing memory range DDR3_SLAVE_6
error: DEFAULT memory range overlaps existing memory range DDR3_MASTER

I don't have a memory range named DEFAULT. My memory map is:

         name            origin    length 

L2SRAM 00800000 00078000 RW X
 MSMCSRAM_MASTER 0c000000 00100000 RW X
MSMCSRAM_SLAVE 0c100000 00100000  RW X
DDR3_SLAVE_0 80000000 02000000  RW X
DDR3_SLAVE_1 82000000 02000000 RW X
DDR3_SLAVE_2 84000000 02000000 RW X
DDR3_SLAVE_3 86000000 02000000 RW X
DDR3_SLAVE_4 88000000 02000000 RW X
DDR3_SLAVE_5 8a000000 02000000 RW X
DDR3_SLAVE_6 8c000000 02000000 RW X
DDR3_MASTER 96000000 0a000000 RW X

Why the linker reports conflict with a non-existing memory range?

  • Weber,

    Can you carefully inspect the build console and see if there is more than one linker command file being included? Also, check the linker map file to see how this DEFAULT memory map is being defined - my guess is that somehow this is defined from 0x00000000 to 0xFFFFFFFF...

    Hope this helps,

    Rafael

  • There is no DEFAULT range defined on the memory map.

    I've managed to apparently solve the problem: My shared region is inside MSMRAM, but defined b sysbios. When I defined a MSMRAM smaller than my shared region requires, this weird error happened.

    By just setting my MSMRAM to full range, the code compiles and links.