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.
I am trying to migrate a legacy project that was developed under CCSv2.21 to CCSv5.2
Target: TMS320VC5502 with 32K x 16-bit (64K bytes) of on-chip dual-access RAM.
External Memory: 512Kbytes of high-speed SRAM accessed via EMIF.
----------
CCSv2.21.00 environment:
DSP/BIOS 4.90.270 (including CSL)
Code Generation Tools 2.56
DSPLIB 2.20.02
JTAG Emulator: Spectrum Digital XDS510PP PLUS via parallel port connection to Windows XP PC
See attached files:
CCS2_main.cmd (linker command file)
CCS2_main.cdb (DSP/BIOS 4 configuration)
CCS2_maincfg.cmd (generated BIOS linker command file)
CCS2_main.map (generated memory map file)
----------
CCSv5.2 environment:
DSP/BIOS 5.41.13.42
CSL 2.31.00.9
Code Genration Tools 4.4.1
DSPLIB 2.40.00
JTAG Emulator: Spectrum Digital XDS560v2 STM via USB connection to Windows 7 64-bit PC)
Building the application in CCSv5.2 fails with several errors like these:
"./maincfg.cmd", line 164: error #10099-D: program will not fit into available
memory. run placement with alignment/blocking fails for section ".clk" size
0x8 page 0. Available memory ranges:
DARAM size: 0x7f00 unused: 0xa max hole: 0x4
.clk: block(0x20000), RUN_START(CLK_A_TABBEGb) {
"./maincfg.cmd", line 210: error #10099-D: program will not fit into available
memory. run placement with alignment/blocking fails for section ".idl" size
0x8 page 0. Available memory ranges:
DARAM size: 0x7f00 unused: 0xa max hole: 0x4
.idl: block(0x20000), RUN_START(IDL_A_TABBEGb) {
...
See attached files:
CCS5_main.cmd (linker command file)
CCS5_main.tcf (DSP/BIOS 5 configuration)
CCS5_maincfg.cmd (generated BIOS linker command file)
CCS5_main.map (generated memory map file)
CCS5_buildlog.txt
----------
Is a BIOS 5.41 application expected to require more memory than a BIOS 4.90 application?
I would be grateful if someone could point me to guidance to help me address this.
I would also be grateful if someone could point me to general guidance for migrating C55x applications from CCS2/BIOS 4 to CCS5/BIOS 5.
In the meantime, I will move modules from on-chip memory to off-chip memory to try to get something working.
Best regards,
Patrick McCloskey
Some of my previous posts related to this discussion thread:
"Legacy TMS320VC5502 project with updated C5500 compiler version 4.4.1"
http://e2e.ti.com/support/development_tools/compiler/f/343/p/194892/708551.aspx#708551
"Should I update from CCSv3.3 toolchain?"
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/199018.aspx
"Must specify a URI scheme"
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/199941/711314.aspx#711314
It turns out the legacy CCSv2 application included the DSPLib in the environment but it was not actually using it.
Some aspects of the DSPLib were borrowed, though.
We have been experimenting with some components in the DSPLib for our new CCSv5 application.
At this point we are not using it.
Do you have a specific concern regarding DSPLib v2.x?