• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1433 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.

.out to .hex conversion - "duplicate section" warnings

Sarvani Chadalapaka
Intellectual 270 points

Hi,

When we are trying  to convert .out files to .hex format using hex6x.exe hex converter, we see several warnings of this kind:


warning: duplicate section name bdtest.out(.sysmem) (ignored)
warning: duplicate section name bdtest.out(.stack) (ignored)
warning: duplicate section name bdtest.out(.text) (ignored)
warning: duplicate section name bdtest.out(.fardata) (ignored)
warning: duplicate section name bdtest.out(.switch) (ignored)
warning: duplicate section name bdtest.out(.far) (ignored)
warning: duplicate section name bdtest.out(.cio) (ignored)

These sections do not appear in the hex6x.exe output .map file. Also, we found the following thread related to similar kind of issue that suggests to create a custom RTSC platform instead of adding a custom linker command file to the project.

http://e2e.ti.com/support/development_tools/compiler/f/343/t/190766

Is there any other way around this, for example giving SECTIONS {} directive to hex6x ?

-- 
Thanks!

Regards,
Sarvani Chadalapaka
HPC Systems Engineer
Signalogic Inc.
  • TI__Guru* 84285 points

    The workaround would be to rename the sections in the linker command file.  There is no way in the current hex converter to process multiple sections with the same name.

  • in reply to Archaeologist
    Intellectual 270 points
    Archaeologist,

    Thank you for your fast response.

    Can you explain why this does not cause duplicated sections or any other problem in the .out files?

    Also, in our application specific .cmd file, we have a line like this:

    .switch: load >> L2SRAM
    Its not really a rename, just a reference. Is this causing the conflict?

    --
    Thanks!

    Regards,
    Sarvani Chadalapaka
    HPC Systems Engineer
    Signalogic Inc
  • in reply to Sarvani Chadalapaka
    TI__Guru**** 253300 points

    sarvani chadalapaka said:
    .switch: load >> L2SRAM

    This line (among other things) creates an output section named .switch.  In your case, it is likely there is a similar line in another linker command file which also creates an output section named .switch.  When you create two output sections with the same name, the hex utility ignores the second one and issues the warning you show in your first post.

    The answer is to change your build so that no duplicate output sections are created.  The forum thread you refer to in your first post is a reasonable approach.  If that does not work for you, I recommend you begin a new thread in the TI-RTOS forum about how to configure your build to avoid creating duplicate sections.

    Thanks and regards,

    -George

  • in reply to George Mock
    Intellectual 270 points

    George,

    Thanks for the reply. We will try modifying .cmd files. As a note, it appears that the hex utility  ignored both of the "switch" output sections, because we can't find "switch" in the hex utility output .map file and we cant find the starting address in the .hex file contents.

    -- 
Thanks!

Regards,
Sarvani Chadalapaka
HPC Systems Engineer
Signalogic Inc.