• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 1200 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.

Compiler/TMS320F28388S: Align 16 used for F28388 CM cmd

Strong ZHANG
Expert 4740 points

Part Number: TMS320F28388S

Tool/software: TI C/C++ Compiler

Hi expert,

My customer are using Align(16) for each section below: then it should force the linker to align that one section to a 16-byte aligned address. 

but when take a look at the hex file generated, it did not work as below showed:

the line 215 seem it not 16 byte align.

Also the line 3680 is not 16 byte aligned.

attachment is the cmd file customer use, anything wrong for the result that hex file generated?

Fullscreen app.txt Download 
MEMORY
{
   /* Flash sectors */
//   CMBANK0_RESETISR   : origin = 0x00200000, length = 0x00000008 /* Boot to Flash Entry Point */
   CMBANK0_BOOTLOADER   : origin = 0x00200008, length = 0x00003FF7 /* user Boot loader Entry Point */
   CMBANK0_RESETISR     : origin = 0x00204000, length = 0x00000008 /* Boot to Flash Entry Point */
//   CMBANK0_APP        : origin = 0x00204000, length = 0x0003BFF0 /* app Entry Point */
//   CMBANK0_APP        : origin = 0x00204008, length = 0x0003BFF0 /* app Entry Point */
   CMBANK0_APP          : origin = 0x00204008, length = 0x0003BFE8 /* app Entry Point */
   CMBANK0_APP_META     : origin = 0x0023FFF0, length = 0x00000010 /* app meta. Entry Point */
   CMBANK0_BACKUP       : origin = 0x00240000, length = 0x0003FFF0  /* backup Entry Point */
   CMBANK0_BACKUP_META  : origin = 0x0027FFF0, length = 0x00000010  /* backup meat. Entry Point */

   C1RAM                : origin = 0x1FFFC000, length = 0x00000FFF
   C0RAM                : origin = 0x1FFFD000, length = 0x00002FFF

   BOOT_RSVD            : origin = 0x20000000, length = 0x00000800  /* Part of S0, BOOT rom will use this for stack */
   S0RAM                : origin = 0x20000800, length = 0x000037FF
//   S1RAM              : origin = 0x20004000, length = 0x00003FFF
//   S2RAM              : origin = 0x20008000, length = 0x00003FFF
//   S3RAM              : origin = 0x2000C000, length = 0x00003FFF
   S1_2_3RAM            : origin = 0x20004000, length = 0x0000BFFF

   E0RAM                : origin = 0x20010000, length = 0x00003FFF

   CPU1TOCMMSGRAM0      : origin = 0x20080000, length = 0x00000C00
   CPU1TOCMMSGRAM0_RT   : origin = 0x20080C00, length = 0x00000200
   CPU1TOCMMSGRAM1      : origin = 0x20080E00, length = 0x00000200
   CMTOCPU1MSGRAM0      : origin = 0x20082000, length = 0x00000C00
   CMTOCPU1MSGRAM0_RT   : origin = 0x20082C00, length = 0x00000200
   CMTOCPU1MSGRAM1      : origin = 0x20082E00, length = 0x00000200

}

SECTIONS
{
   .resetisr        : > CMBANK0_RESETISR,ALIGN(16)
   .vftable         : > CMBANK0_APP ,ALIGN(16)  /* Application placed vector table in Flash*/
   .vtable          : > S0RAM                   /* Application placed vector table in RAM*/
   .text            : > CMBANK0_APP,ALIGN(16)
   .cinit           : > CMBANK0_APP,ALIGN(16)
   .pinit           : > CMBANK0_APP,ALIGN(16)
   .switch          : > CMBANK0_APP,ALIGN(16)
   .sysmem          : > E0RAM

   .stack           : > C1RAM
   .ebss            : > C1RAM
   .econst          : > CMBANK0_APP,ALIGN(16)
   .esysmem         : > C1RAM
   .data            : > S1_2_3RAM
   .bss             : > C0RAM
   .const           : > CMBANK0_APP,ALIGN(16)

    MSGRAM_CM_TO_CPU1_RT    : > CMTOCPU1MSGRAM0_RT  , type=NOINIT   //must noinit type?why?
    MSGRAM_CM_TO_CPU1_NRT   : > CMTOCPU1MSGRAM0     , type=NOINIT
    MSGRAM_CM_TO_CPU1       : > CMTOCPU1MSGRAM1     , type=NOINIT
    MSGRAM_CPU1_TO_CM_RT    : > CPU1TOCMMSGRAM0_RT  , type=NOINIT
    MSGRAM_CPU1_TO_CM_NRT   : > CPU1TOCMMSGRAM0     , type=NOINIT
    MSGRAM_CPU1_TO_CM       : > CPU1TOCMMSGRAM1     , type=NOINIT

    Identification_Section  : > CMBANK0_APP_META

    .TI.ramfunc : {} LOAD = CMBANK0_APP,
                           RUN = S0RAM,
                           LOAD_START(RamfuncsLoadStart),
                           LOAD_SIZE(RamfuncsLoadSize),
                           LOAD_END(RamfuncsLoadEnd),
                           RUN_START(RamfuncsRunStart),
                           RUN_SIZE(RamfuncsRunSize),
                           RUN_END(RamfuncsRunEnd),
                           ALIGN(16)
}

  • 0
    TI__Guru**** 253590 points

    Those sections are aligned, but the length (the number of words) in the section is not a multiple of the alignment.  If you need that behavior, in the linker command file, replace ALIGN with PALIGN.  For more details, please search the C28x assembly tools manual for the sub-chapter titled Alignment With Padding.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Expert 4740 points

    Hi George,

    It work to make length (the number of words) in the section is a multiple of the alignment by using PALIGN, but there have another issue that there are big hole between two section, for example, the address of line 3690 is 0x0B60, and the address of line 3681 is 0x0C00, 0x0C00 - 0x0B60 = 160, so there are 160 byte are filled nothing,  why would have so big size are hole? it should be less than 0x20. how to reduce the hole size between these two section?

    It seem C28x compiler does not have this issue, only CM compiler have this issue.

  • 0 in reply to Strong ZHANG
    TI__Guru**** 253590 points

    Holes between sections are normal.  How is the output of the hex utility used?  Why does a hole like this cause a problem?

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Expert 4740 points

    the problem is not there have the holes, but the holes size are too big. what customer want is below 30 byte,  the holes size so big will impact the programming by PC.

    below are how customer do the configuration for hex.

  • 0 in reply to Strong ZHANG
    TI__Guru**** 253590 points

    Strong ZHANG said:
    the problem is not there have the holes, but the holes size are too big. what customer want is below 30 byte,  the holes size so big will impact the programming by PC.

    There is no method by which you can limit the size of a hole in memory.  You can either live with them, or eliminate them.  Thus, I presume you want to eliminate them.  There are two methods to consider.

    One method is implemented in the linker command file.  In the MEMORY directive (and not the SECTIONS directive) specify a fill value.  For more details, please search the TI ARM assembly tools manual for the sub-chapter titled The MEMORY Directive.

    The other method is implemented with the hex utility.  Use image mode and the related fill feature.  For more details, please see this forum thread.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Expert 4740 points

    Hi George

    One method is implemented in the linker command file.  In the MEMORY directive (and not the SECTIONS directive) specify a fill value.  For more details, please search the TI ARM assembly tools manual for the sub-chapter titled The MEMORY Directive.

    --> For this method, all the flash sector will be filled with a value, including those that may not be used. what customer want is to only fill the hole between sections with a value.

    The other method is implemented with the hex utility.  Use image mode and the related fill feature.  For more details, please see this forum thread.

    --> customer try this method, but face an error below, could you suggest how to fix?

  • 0 in reply to Strong ZHANG
    TI__Guru**** 253590 points

    In reference to using the fill feature on the MEMORY directive, you say ...

    Strong ZHANG said:
    --> For this method, all the flash sector will be filled with a value, including those that may not be used. what customer want is to only fill the hole between sections with a value.

    Another alternative is using the fill feature related to the SECTIONS (not MEMORY) directive.  This is more difficult to understand, and I'm not sure it solves the problem.  But, you are welcome to try.  For the details, please search the C28x assembly tools manual for the sub-chapter titled Creating and Filling Holes.

    Regarding image mode of the hex utility you say ...

    Strong ZHANG said:
    customer try this method, but face an error below, could you suggest how to fix?

    When you use image mode, you must supply a ROMS directive.  A ROMS directive can only be supplied in a hex command file, and not on the command line.  This forum post demonstrates the details.

    Thanks and regards,

    -George