• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 530 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

#pragma LOCATION for COFF?

Kier
Mastermind 8075 points

Hello,

I read in the compiler manual that #pragma LOCATION only works for EABI.

Is there an equally simple way to locate a symbol at a specific address in a COFF project please? For example, a CRC in the last two words of a flash sector.

The only solution I can currently think of is to define a MEMORY directive with the target address and length 2:

   FLASHM             : origin = 0x0BC000, length = 0x001FFE    /* on-chip Flash */

   FLASHM_CRC  : origin = 0x0BDFFE, length = 0x000002    /* on-chip Flash */

Then a SECTION directive to direct the variable to FLASHM_CRC. Is that my only option?

Thank you.

  • 0
    TI__Guru**** 161675 points

    Kier,

    Your approach should work.  Our expert on this is out today and can comment on if there is a better way to do this tomorrow.

    Regards,

    John

  • 0
    Guru 92251 points
    Kier said:
    For example, a CRC in the last two words of a flash sector.

    Another option could be to place the CRC in its own section, and use the HIGH Location Specifier for the section.

    See section 8.5.5.2.4 Controlling Placement Using The HIGH Location Specifier in TMS320C28x Assembly Language Tools v20.12.0.STS User’s Guide

  • 0
    TI__Guru**** 245040 points

    The method you propose is reasonable.  I'll suggest another way that is a little easier to implement and understand.

    In the C code where you create the symbol, use #pragma DATA_SECTION in a manner similar to ...

    Fullscreen
    1
    2
    #pragma DATA_SECTION(special_global_variable, "odd_section_name")
    int special_global_variable;
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    In the SECTIONS directive part of the linker command file, write something similar to ...

    Fullscreen
    1
    odd_section_name > 0x0BDFFE
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This code creates an output section named odd_section_name.  It is made up of all the input sections named odd_section_name.  In this case, there is only one such input section.  It is allocated to the hard-coded address 0x0BDFFE.   For more background on the terms used in this paragraph, please see the first part of the article Linker Command File Primer.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Mastermind 8075 points

    Thanks George. I think that will do nicely.