Compiler/TMS320C6747: declaring big matrix/array problem

Hi,

Which SDK is this?

Best Regards,
Yordan

CCS version:5.5.0.00077
I m debugging dsp card with 256 MBit SDRAM

Ok, so this is a bare metal code.
Have a look at these threads:
e2e.ti.com/.../340008
e2e.ti.com/.../247877
Hope this helps.

Best Regards,
Yordan

It is not the case i think. I have memory problem. When i create unsingned short array[1024], the debugging will be kept going. Debug process will not terminate.

in auto generated linker.cmd, memory configuration is as follows:
-args 0x0
-heap 0x1000000
-stack 0x1000000

MEMORY
{
IROM (RX) : org = 0x11700000, len = 0x100000
IRAM (RWX) : org = 0x11800000, len = 0x40000
L3_CBA_RAM (RWX) : org = 0x80000000, len = 0x20000
SDRAM : org = 0xc0000000, len = 0x10000000
}

---
as i mentioned before the dsp card has 256 MBit SDRAM. Even that specification, when i set stack size as 0x5000000 debug will not work. After i decrease as 1000000 then it will work.

Hi!
At the first glance, all memories look big enough to handle 2048 shorts. Although I believe your issue is memory related, I can't see it with info provided. Perhaps, you have some minimal testcase to share, so forum folks could look through.

Assuming your SDRAM is 256Mbit (as in bits), that is 32MiB or 0x02000000 bytes. The linker command would then be:
SDRAM : org = 0xc0000000, len = 0x02000000
Defining a stack of 0x05000000 is bigger than available memory. A stack of 0x01000000 is half of available memory. I assume you need a huge stack to a declare your array as a local variable. The linker will not be able catch allocaton problems. I would suggest declaring your array as a global variable to allow the linker to check your memory allocation.