CCS/TMS320F28034: output static library

After you create the a.lib file, what is the very next step that happens with it?  Please be as specific as you can.  Show the next command you invoke, or whatever happens. Copy-and-paste the text, and do not use a screen shot.

Thanks and regards,

-George

Thanks george for such a quick reply！

We encapsulate several .c files into an Utility.lib file, and add the Utility.lib file to the project. It can compile and link successfully after adding the Utility.lib file to the project,and generate a .out file.

But we find burn the .out generated by the above compilation into the chip, and find the same .c file, one part of the program logic is the same as the design, but other part of the program logic is different from the design.However if burn a program that is not packaged into .lib to the chip, the logic of the program is the same as the design.

The Utility.lib file in the project as shown below.

The properties as shown below:

The compilation result as shown below:

By the way, would you tell what specific documents I need to provide? the compilation result? the properties? or others?

Sorry!supplementary the picture, would you see the picture?

The likely reason your screen shots do not show is explained here.  

If you are showing the text of a command, or the output of running  a command, please copy-and-paste the text, and do not use a screen shot.

Jim-9920 said:

but other part of the program logic is different from the design

How do you know this occurred?  Exactly what you look at?  What do you see?  What do you expect to see instead?

Thanks and regards,

-George

Dear George,

Our project is a solar Inverter firmware,we expect to aotomatic save solar input accumulated energy to Eeprom once a minute,but we find this part of the action was not executed when burning the .out generated by encapsulating several .c files into an Utility.lib file into the chip. However, it can automatic save solar input accumulated energy to Eeprom if we burn a program that is not packaged into .lib to the chip.

You build your program twice.  In one build, Utility.lib is used.  In the other build, it is not.  In terms of the functions and data it contains, each program is the same.  However, the functions and data are at different addresses.  And a difference in the address is the likely cause of the problem.  You need to learn more details about what has gone wrong.  Determine what functions or data are related to the error.  Then compare the address of those functions or data and see why changing the address causes a change in behavior.

Please let me know what you find.

Thanks and regards,

-George

Dear George,

I compare the two map files, but I can not determine what functions or data are related to the error. would you help provide us with some relevant file?

The two map files are shown in the attachment. Thanks.

5265.Project.txtProject_Lib.txt

Jim-9920 said:

I compare the two map files, but I can not determine what functions or data are related to the error.

That's not what I meant.  First, you use debugging techniques to work out which functions or data are related to the error.  Then you look at the addresses of those functions or data in the map file.  The difference in those address in the two builds is probably related to the error.

Jim-9920 said:

The two map files are shown in the attachment.

The attached files are not ordinary text files. They are binary files.  I don't know what software to use to view those files, so I cannot see their contents.

Thanks and regards,

-George