I'm using an Analog Devices 21161N EZ-Kit Lite board and a third party library by the name of SigLib and programming in c++. I'm using the Visual DSP++ 3.0 with SP-1. I'm running out of room in the seg_pmco segment and am trying to move the Siglib library to external SDRAM. I created a segment as follows: seg_pmsdram { TYPE(PM RAM) START(0x280000) END(0x2fffff) WIDTH(48) } and mapped the file as follows : seg_pmsdram{ INPUT_SECTIONS(SigLib.dlb(seg_pmco)) }>seg_pmsdram When I compile the file, I find that the routines I use from the library are still being mapped to the seg_pmco output segment. I know I must be missing something simple but I can't figure out what. I promise to stop looking as soon as I find it. Has anyone else had success in moving third party libraries to external SDRAM and if so, could you share your ldf file and any other pertinent info? Thank you.
Moving libraries to external SDRAM
Started by ●August 13, 2003
Reply by ●August 14, 20032003-08-14
sholle@link-comm.com (Steve Holle) wrote in news:ba83847d.0308131447.5cd3c537@posting.google.com:> When I compile the file, I find that the routines I use from the > library are still being mapped to the seg_pmco output segment.What do the other output sections look like, in particular the one where the library in question is erroneously being written? I'll bet it has a macro that includes your library. -- Kenneth Porter http://www.sewingwitch.com/ken/