• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 217 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.

Original question:

AM2434: using ARM Fusa compiler on M4F

AM2434: Purpose of section ".TI.section.flags" generated by TI ARM Clang for M4F

awolde
Prodigy 60 points
Part Number: AM2434

Tool/software:

From the ELF file generated by tiarmclang (for M4F CPU), I see a section named .TI.section.flags in the type "PROGBITS". 


Following questions regarding to that:
1. what's is the purpose of that section and when/how it's used?
2. Would it make the binary in RPRC file different with the binary in memory when the firmware running?
   FYI, we are going to check the bianary with CRC, but seems get differ between them.

 

Section Headers:
  [Nr] Name              Type            Addr     Off    Size   ES Flg Lk Inf Al
   ....
  [34] .TI.section.flags PROGBITS        00000000 12fe38 00001a 00      0   0  0
    ....
Key to Flags:
  W (write), A (alloc), X (execute), M (merge), S (strings), I (info),
  L (link order), O (extra OS processing required), G (group), T (TLS),
  C (compressed), x (unknown), o (OS specific), E (exclude),
  D (mbind), y (purecode), p (processor specific)

  • 0
    TI__Mastermind 49508 points

    Hello Awolde,

    Thanks for reaching out to Texas Instruments E2E support forum.

    I have taken your inputs. Please allow some time to check the above details and revert back.

    Regards,

    Tushar

  • 0
    TI__Mastermind 49508 points

    Hello Awolde,

    Thanks for your patience.

    awolde said:
    1. what's is the purpose of that section and when/how it's used?

    I will check this details internally with the compiler team and update here. Please allow some time.

    awolde said:
    2. Would it make the binary in RPRC file different with the binary in memory when the firmware running?
       FYI, we are going to check the bianary with CRC, but seems get differ between them.

    Can you please tell how are loading the binary on EVM? 

    Are you using CCS to load the binary or using SBL to load binaries?

    Also can you please tell how are calculating CRC for the loaded binary?

    Regards,

    Tushar