• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 544 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.

About the xdl link file in BIOS6

Allen Lee
Genius 3770 points

Hi All,

When I build some of my BIOS6 project, there will produce 2 xdl files in *\Debug\configPkg\package\cfg directory whose name are xx_pe66_x.xdl and xx_pe66.xdl. And the xx_pe66_x.xdl has more content such as memory segments and sections. But other projects only generate one xdl file. I don't know which configuration introduce the difference?

Allen

  • 0
    TI__Mastermind 18320 points

    Allen,

    I wasn't sure after reading your post what you are trying to solve.  Are you trying to solve some kind of issue with building your application, or are you simply asking for more background info on how and when XDL files are generated by the config tool?

    Dave

  • 0 in reply to David Friedland
    Genius 3770 points

    Hi Dave,

    Yes, I want to ask for the background info about the XDL file generation. I guess there exists some configurations which have influence on the generation of XDL, so some of projects have two XDL files and the others have one.

    Allen

  • 0 in reply to Allen Lee
    TI__Mastermind 37985 points

    Allen,
    the only time we need two linker command files is when the profile "whole_program" is used. For that profile, the linker is invoked twice and each invocation requires a separate linker command file. First, XDCtools invoke linker to generate partially linked object file that contains everything except the app code. Then, that partially linked object file is linked again with the app code.

    This profile generates a high level of optimization, but the build can take minutes for larger configurations. Newer SYS/BIOS releases (6.32 and newer, I think) do not use "whole_program" because the similar performance is achieved in some other way that does not require long link times.

  • 0 in reply to Sasha Slijepcevic
    Genius 3770 points

    Hi Sasha,

    Yes, your explanation exactly meets the situation of XDL file.

    Thanks.

    Allen