Compiling Old Build with New CCS Version

The string "/.obj" is probably a corrupted filename. Most likely, there's some build variable which isn't being defined in the project. Is PLEX_dsp1.cmd a linker command file? Can you show us this file?

The entire file contents are:

//-l PLEX_dsp1cfg.cmd
 
SECTIONS{
     .commandblock:         {} > command_sec
     .uartcontrolblock:     {} > uartcontrolblock
     .bufblock:             {} > IntMem
     .fpgablock:            {} > fpga
     .gmbufblock:           {} > GMBuf
  .ChanListBlock:   {} > SDRAM_ChList
  .ChanDataBlock:   {} > SDRAM_ChData
  .FullMagBlock:    {} > SDRAM_FullMag

  .text:      {
         .= 20;
        /*load lib first to get around dsp1 lockup bug*/
        -lrts6700.lib(.text)
        -lcsl6713.lib(.text)
        ./Debug/PLEX_dsp1cfg_csl.obj (.text:cslCfgInit)

        *(.text)
        } > ProgramSec

 /*group them in the order you want them in memory
 SDRAM uninit vars loaded last (or after all the init var)*/
  GROUP{
   .switch:      {}  
   .bss:      {}
   .cinit:     {}
   .pinit:     {}
   .printf:     {}
   .const:     {}
   .far:      {}
   .SDRAM:     {}
      .defaultblock:         {}
   .data:      {}
   .cio:       {}
  } > SDRAM
 
}

Done. Next Error:

>> PLEX_dsp1.cmd: error: system error, can't open file

'./Debug/PLEX_dsp1cfg_csl.obj' for input: No such
>> Compilation failure
file or directory

Unless you're sure you need the code in PLEX_dsp1cfg_csl.obj to appear before code from other modules, comment out this line:
/* ./Debug/PLEX_dsp1cfg_csl.obj (.text:cslCfgInit) */

One other thing to check on.

From the perspective of the current working directory as seen by the linker, is:

Chad Wolter said:

./Debug/PLEX_dsp1cfg_csl.obj

a valid path to that file?

Thanks and regards,

-George

it is not...I already discovered that error. I replaced that line with "PLEX_dsp1cfg_csl.obj (.text:cslCfgInit)" and got past that error. Now I have around 20 other errors..

./PLEX_dsp1cfg_c.obj" "./PLEX_dsp1cfg.obj" "./PLEX_dsp1.obj" "./DSP_Time.obj" "./CLM_subcmd.obj" "./ADC_flash_interface.obj" "./ADC_flash_drv.obj" "./ADC_LED.obj" "./ADC_DSP_PLL.obj" --library="C:\Program Files\C6xCSL\lib_2x\csl6713.lib" "../C6713.cmd"
>> ../C6713.cmd, line 28: warning: multiple definitions of SECTION named '.text'
>> ../C6713.cmd, line 29: warning: multiple definitions of SECTION named
'.stack'
>> ../C6713.cmd, line 30: warning: multiple definitions of SECTION named '.bss'
>> ../C6713.cmd, line 31: warning: multiple definitions of SECTION named '.cio'
>> ../C6713.cmd, line 32: warning: multiple definitions of SECTION named
'.const'
>> ../C6713.cmd, line 33: warning: multiple definitions of SECTION named '.data'
>> ../C6713.cmd, line 34: warning: multiple definitions of SECTION named
'.switch'
>> ../C6713.cmd, line 36: warning: multiple definitions of SECTION named '.far'
>> ../C6713.cmd, line 37: warning: multiple definitions of SECTION named '.args'
>> ../C6713.cmd, line 42: warning: multiple definitions of SECTION named
'.pinit'
>> ../C6713.cmd, line 43: warning: multiple definitions of SECTION named
'.cinit'
>> error: memory types IntMem_Unused and IRAM on page 0 overlap
>> error: memory types CACHE_L2 and L2RAM on page 0 overlap
>> error: memory types HWI_Table and EMIFCE0 on page 0 overlap
>> error: memory types Flash and EMIFCE1 on page 0 overlap
>> error: memory types uartcontrolblock and EMIFCE2 on page 0 overlap
>> error: memory types fpga and EMIFCE3 on page 0 overlap
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.args'
>> error: can't find any memory areas for allocation of '.args'
>> error: can't allocate '.args' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.binit'
>> error: can't find any memory areas for allocation of '.binit'
>> error: can't allocate '.binit' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.bss'
>> error: can't find any memory areas for allocation of '.bss'
>> error: can't allocate '.bss' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.c6xabi.exidx'
>> error: can't find any memory areas for allocation of '.c6xabi.exidx'
>> error: can't allocate '.c6xabi.exidx' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.c6xabi.extab'
>> error: can't find any memory areas for allocation of '.c6xabi.extab'
>> error: can't allocate '.c6xabi.extab' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.cinit'
>> error: can't find any memory areas for allocation of '.cinit'
>> error: can't allocate '.cinit' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.cio'
>> error: can't find any memory areas for allocation of '.cio'
>> error: can't allocate '.cio' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.const'
>> error: can't find any memory areas for allocation of '.const'
>> error: can't allocate '.const' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.data'
>> error: can't find any memory areas for allocation of '.data'
>> error: can't allocate '.data' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.far'
>> error: can't find any memory areas for allocation of '.far'
>> error: can't allocate '.far' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.fardata'
>> error: can't find any memory areas for allocation of '.fardata'
>> error: can't allocate '.fardata' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.init_array'
>> error: can't find any memory areas for allocation of '.init_array'
>> error: can't allocate '.init_array' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.neardata'
>> error: can't find any memory areas for allocation of '.neardata'
>> error: can't allocate '.neardata' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.pinit'
>> error: can't find any memory areas for allocation of '.pinit'
>> error: can't allocate '.pinit' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.ppdata'
>> error: can't find any memory areas for allocation of '.ppdata'
>> error: can't allocate '.ppdata' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.ppinfo'
>> error: can't find any memory areas for allocation of '.ppinfo'
>> error: can't allocate '.ppinfo' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.rodata'
>> error: can't find any memory areas for allocation of '.rodata'
>> error: can't allocate '.rodata' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.stack'
>> error: can't find any memory areas for allocation of '.stack'
>> error: can't allocate '.stack' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.switch'
>> error: can't find any memory areas for allocation of '.switch'
>> error: can't allocate '.switch' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.sysmem'
>> error: can't find any memory areas for allocation of '.sysmem'
>> error: can't allocate '.sysmem' into 'IRAM' (page 0)
>> warning: can't find a memory area named 'IRAM' on page 0 for allocation of
'.text'
>> error: can't find any memory areas for allocation of '.text'
>> error: can't allocate '.text' into 'IRAM' (page 0)
>> error: errors in input -
K:/Infrastructure_Group_Stuff/TS2_ADC/Code/TS3/3.01.19.3000_CCS5_test/Source/DSP1/PLEX_dsp1/../../DSP1/Debug/TS2ADC_Dsp1.out not built

okay...got through these errors. CCSv5 puts its own linker command file by default, which needed to be swapped out for my custom one. The code now builds, but my post build steps are messed up. Need to figure out what I am seeing here first before asking the next question.

OK. Seem to have the post-build steps squared away. I am now going to compare the memory maps of the projects compiled by both IDEs

The Memory maps are a bit different, particularly in the .text and related memory sections. I attribute this to the slightly different compiler and DSP/BIOS versions I am using under CCSv5 and CCSv3.3. In CCSv3.3: Compiler 6.0.27, DSP/BIOS: 5.41.06.21. IN CCSv5.3: Compiler: 6.0.31, DSP/BIOS 5.42.1.09. Thanks to George and Chris for the assistance. I'd like to keep this thread open, if possible, as I plan on digging into the debugger/emulation stuff tomorrow.

Chad Wolter said:

I plan on digging into the debugger/emulation stuff tomorrow.

This forum is for issues with the compiler and related tools.  For issues with CCS and emulation, please use the CCS forum.

Thanks and regards,

-George

Very well, I'll follow up with Chris if I need assistance with that. Thanks again, guys.
Chad