• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 791 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/TMS320C5504: Code Composer 10, cannot change output format on legacy v3.3.2 project.

Levi Amen
Prodigy 110 points

Part Number: TMS320C5504

Tool/software: Code Composer Studio

We are currently in the process of migrating an old Code Composer v3.x project into Code Composer 10. We are at the point where the project builds, using the C5500 Code Generation Tools 3.3.2, but the resulting program does not run on the TMS320C55x.

I came across the following warning while looking through the build log:  warning: '.sysmem' section not found -- ignoring '-heap <size>' option.


The project has a custom link command file, which appears to be in EABI format.

MEMORY

{

    PAGE 0:

        MMR     : origin = 0000000h, length = 00000c0h
        SPRAM   : origin = 00000c0h, length = 0000040h

        VECS    : origin = 0000200h, length = 0000100h
        DARAM0  : origin = 0000300h, length = 0001d00h
		DARAM1  : origin = 0002000h, length = 0004000h
     /* DARAM2  : origin = 0004000h, length = 0002000h	absorbed into DARAM1*/
        DARAM3  : origin = 0006000h, length = 0008000h   
     /* DARAM4  : origin = 0008000h, length = 0002000h
        DARAM5  : origin = 000a000h, length = 0002000h	 
        DARAM6  : origin = 000c000h, length = 0002000h	 absorbed into DARAM3*/
        DARAM7  : origin = 000e000h, length = 0002000h

        SARAM0_3: origin = 0010000h, length = 0008000h
/*        SARAM1  : origin = 0012000h, length = 0002000h*/
/*        SARAM2  : origin = 0014000h, length = 0002000h*/
/*        SARAM3  : origin = 0016000h, length = 0002000h*/
        SARAM4  : origin = 0018000h, length = 0002000h
        SARAM5  : origin = 001a000h, length = 0002000h
        SARAM6  : origin = 001c000h, length = 0002000h
        SARAM7  : origin = 001e000h, length = 0002000h
        SARAM8  : origin = 0020000h, length = 0002000h
        DMADATA : origin = 0022000h, length = 0002000h
        MSG     : origin = 0024000h, length = 0001000h
        MSGDATA : origin = 0025000h, length = 0001000h
        SARAM11 : origin = 0026000h, length = 0002000h

/*        CE0     : origin = 0050000h, length = 03b0000h 

        CE1     : origin = 0400000h, length = 0400000h

        CE2     : origin = 0800000h, length = 0400000h

        CE3     : origin = 0c00000h, length = 03f8000h

*/

        PDROM   : origin = 0ff8000h, length = 07f00h



}       



 

SECTIONS

{

        vectors  : {} > VECS PAGE 0
        .vectors : {} > SARAM11 PAGE 0         /* interrupt vector table */

        .text    : {} > SARAM0_3 PAGE 0

        .cinit   : {} > SARAM4 PAGE 0

        .switch  : {} > SARAM4 PAGE 0



        .stack   : {} > DARAM0 PAGE 0

        .sysstack: {} > DARAM0 PAGE 0

        .sysmem  : {} > DARAM1 PAGE 0

        .cio     : {} > SARAM4 PAGE 0

        .data    : {} > SARAM4 PAGE 0

        .bss:lecDelayLine : {} > DARAM1 PAGE 0 align 1024
        .bss:lecTaps      : {} > DARAM1 PAGE 0 align 1024
        .bss     : {} > DARAM1 PAGE 0

        .const   : {} > SARAM4 PAGE 0
        .dmadata : {} > DMADATA PAGE 0
        DLYSECTION : {} > DARAM3 PAGE 0

}

However, the project properties is set to use legacy COFF output format, instead of EABI, which cannot be changed as the drop down is grayed out. Any thoughts on how to address this?

  • 0
    Prodigy 110 points

    Here is a picture of the aforementioned project properties (general tab).

  • 0
    TI__Guru**** 253410 points

    The C5500 tools never supported EABI.

    Levi Amen said:
    I came across the following warning while looking through the build log:  warning: '.sysmem' section not found -- ignoring '-heap <size>' option.

    That is probably a real problem, and should not be ignored.  I don't know how it happened.

    I'd appreciate if you would submit your CCS project.  To create the zip file, please follow the directions in the article Sharing Projects.  Attach the zip file to your next post.

    If you are not comfortable sending in the project, then submit the linker map file and the full build log.  I cannot guarantee I can figure out the problem based on these files, but I might.  To create the build log ... In the Console (not Problems) view, use the icon Copy Build Log.  When you name the log file, be sure to use the file extension .txt.  Attach both files to your next post.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 110 points

    George Mock said:

    The C5500 tools never supported EABI.

    I will admit I only realized I had been reading the wrong Optimizing C/C++ Compiler User's Guide till after I made the post, and I realized once I read up the guide specific to the TMS320C55x that it didn't support EABI. I did try to take down the post after this realization, but I'm glad that didn't happen given the following...

    George Mock said:

    That is probably a real problem, and should not be ignored.  I don't know how it happened.

    I just recently took over trying to migrate this legacy project over from CCS 3.3.x, with this being the continuation of the effort found on this forum post . I'd wager the cause of the problem is another migration headache. I can share the build log and linker map files with you now, and if you need the full project to aid in resolving this issue, what is the best way to privately share it with you?

    Note: the dsp_mai_3_3.map file was generated on our old CCS 3.3.x machine, when the build is working properly. Hopefully comparing to it is of some help.support_files.zip

  • 0
    TI__Guru**** 253410 points

    I apologize, it turns out this ...

    Levi Amen said:
    warning: '.sysmem' section not found -- ignoring '-heap <size>' option.

    ... is of little concern.  When you link, you use these two options 

    1. --warn_sections
    2. --heap_size=1024

    The first causes the linker to be more verbose about certain common errors.  The second says the size of the heap should be 1024 bytes.  However, your program never calls any of the malloc functions.  Therefore, it does not need any heap.  Feel free to ignore this diagnostic.  Or, remove the --heap_size option.

    In case it matters ... Later versions of the C5500 tools do not issue this diagnostic.

    Thanks and regards,

    -George