• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1493 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: Import from CCS 3.3 to CCS v7 (and v5) project build program memory size increased

Maosong Young
Prodigy 55 points

Tool/software: Code Composer Studio

I have a CCS3.3 project imported to CCS v7.  The project built correctly but resulted in different size.  Comparing the generated asm files, I found the CCS3 asm file is using relative paths and CCS7 is using full path.  

For example, the generated CCS3 asm file has:

.dwpsn file C:"McBSP0Codec.c",line 346,column 1,is_stm

But the CCS7 asm file has: 

.dwattr $C$DW$87, DW_AT_TI_end_file("C:/code/Products/Source//USB/McBSP0Codec.c")

Also the .const section is different.  In CCS3: $C$FSL2: .string "ASSERT MEM_ILLEGAL!=g_Resample_to_SP0_NBCQ_handleMcBSP0Code".  But in CCS7: 

$C$FSL2: .string "ASSERT MEM_ILLEGAL!=g_Resample_to_SP0_NBCQ_handleC:/tfs/Pro"

What compiler options or build options I need to set to make both CCS3 and CCS7 build the exact same memory size?

Please help!

  • 0
    TI__Guru**** 479361 points

    Hello,

    Maosong Young said:
    The project built correctly but resulted in different size.

    What are you referring to when you mention the size difference? Is it the *.out file size? Or the actual code size used on the target?

    Maosong Young said:
    What compiler options or build options I need to set to make both CCS3 and CCS7 build the exact same memory size?

    The best thing to do is to make sure you are using the same version of the compiler with v7 that was used with v3.

    http://processors.wiki.ti.com/index.php/Compiler_Installation_and_Selection

    Once you do that, then confirm that your are using the same exact build options that were used to build the project in v3.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 55 points
    I was referring to the SARAM size in the generated map file.

    I setup my CCS v7 to use the same compiler and linker tools as in my CSS v3. At the end, I did find out why the SARAM size is different. It's due to the __FILE__ in my LOG_printf code. The __FILE__ is expended to full path name in v7 but in v3 it's only the file name, no path. After fixing that following the E2E community thread name of "__FILE__ without full path".