• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 265 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.

Build conditions for AM335x

UNA
Mastermind 7980 points

Hi,

I am trying to build the following sample project with Windows XP and Windows 7.

 -AM335x StarterWare:DMTIMER sample  

\AM335X_StarterWare_02_00_00_06\examples\evmAM335x\dmtimer

 

I have same build　conditions except for WIndowsOS, but generated out file is different(not same binary).

Build conditions are as follows.

   - CCS version：5.2.0.00069

   - TI TMS40 Codegen Tool 4.9.5   

   - Build options : same conditions

 

What is the cause that the same　out  file is not generated ?

Is this cause depend on WindowsOS ?

 

Best Regards,

Chi

  • TI__Guru**** 252620 points

    Check how the linker is invoked on both builds.  This has to be exactly the same.  If the linker sees the same input files, but in a different order, that can cause differences.

    Next, compare the linker map files.  Use the --map_file option to create a map file. It will have the extension .map.  Expect to find minor differences.  But you should be able to explain them easily.  If you are unsure what you are looking at, post both of the map files here.

    Thanks and regards,

    -George

  • in reply to George Mock
    Mastermind 7980 points

    Hi George,

     

    Thank you for your reply.

    I understood the potential impact of the linker. I will check both map file.

     

    I am concerned about the impact of changing the PC, Windows OS and CCS version.

    For example, I assume that manages the maintenance of the product for 10 years.

    Then except for difference of linker order, Do I need to keep the environment of described above ?

    Is there a possibility that Windows library(ex: stdio.h) is used at build time ?

     

    Best regards,

    Chi

  • in reply to UNA
    TI__Guru**** 252620 points

    I thought of another way you could have differences in the .out file that are not meaningful.  The compiler embeds lots of information (call it meta-data) about the build in the .out file for the purpose of debugging.  This meta-data has no impact on the executable image.  The best example is the full path to the source files.  If the paths to the source files are different between two builds, that causes lots of differences in the meta-data.

    If you think this is the issue, then please try the utility objdiff from the cg_xml package.  It can compare two .out files.  The meta-data, by default, is ignored in the comparison.

    Thanks and regards,

    -George