Sign in

username:

password:



Not a member?

Search adsp



Search tips

Subscribe to adsp



adsp by Keywords

AD1819 | AD7332 | ADSP-2106 | ADSP-21060 | ADSP-21065L | ADSP-2116 | ADSP-21160M | ADSP-2181 | ADSP-218x | ADSP-219 | ADSP-2199 | ADSP219 | BF531 | BF532 | BF533 | BF535 | Blackfin | FFT | JTAG | LDF | SDRAM | SHARC | SPORT | UART | VDSP++ | VisualDSP

Ads

Discussion Groups

Discussion Groups | Analog Devices DSPs | Re: memory allocation

Technical discussions related to Analog Devices DSPs (including Blackfin, TigerSHARC, SHARC and ADSP-21xx DSPs).

  

Post a new Thread

memory allocation - Tom Hanley - Jan 22 18:38:00 2001



Hello again,
Good news, I got the debugger running with some help from the
folks at tech support. it WAS the registry. Go fig... Anyway, now I'm
trying to convert a C-program over to assembler and see if maybe I can
streamline it a little. However, I get the following errors.

[Error E2007] Out of memory in memory segment "seg_dmda". While
processing the input section "seg_dmda" from file "INT_TABL.DOJ" of size
0x50a words

[Error E2007] Out of memory in memory segment "seg_dmda". While
processing the input section "seg_dmda" from file "DOPRNT.DOJ" of size
0x30c words

[Error E2007] Memory allocation errors. See the MAP file
".\DEBUG\PLAY_FILE.map" for details

those would lead me to believe that I ran out of memory in one of the
sections on the chip. However, when I look at the memory map file that
the compiler referred me to (one generated by the compile itself, not the
generic one) it says that I still have unused blocks of memory in each
section. One of them gets pretty close, but there are still 0x26
available. Am I not looking at the right thing?

Tom Hanley






(You need to be a member of adsp -- send a blank email to adsp-subscribe@yahoogroups.com )

Re: memory allocation - Kenneth Porter - Jan 22 21:55:00 2001

On Mon, 22 Jan 2001 13:38:20 -0500 (EST), Tom Hanley wrote:

> those would lead me to believe that I ran out of memory in one of the
> sections on the chip. However, when I look at the memory map file that
> the compiler referred me to (one generated by the compile itself, not the
> generic one) it says that I still have unused blocks of memory in each
> section. One of them gets pretty close, but there are still 0x26
> available. Am I not looking at the right thing?

No, you want to look at the LDF file (probably in 21k/ldf). "seg_dmda"
is the name of the section in an object or executable file. (Object and
executable section names in different name spaces, but the ADI
conventions typically use the same names for both. I use different
names in my LDF files, using seg_* for object files, out_* for
executables, and mem_* for memory regions, to make the error messages
easier to figure out.) The LDF describes the partitioning of memory and
which memory section to place each object section in. The first
(memory) section of the LDF file associates a memory section name with
an address space, specified by its starting address, length, width, and
type. The second LDF section associates an executable section name with
a memory section name, and specifies, for each object file, which
object sections go in that executable section.

Kenneth Porter
Kensington Laboratories, Inc.
mailto:
http://www.kensingtonlabs.com





(You need to be a member of adsp -- send a blank email to adsp-subscribe@yahoogroups.com )