TM4C1290NCZAD: Generated .out file is not working as expected in CCS Version 12

Hi,

  Can you try one more thing before I send your question to our CCS expert.

  Did you use 'Load Program' instead of 'Load Symbol'. Just wanted to make sure you may have 'Load Symbols' at one point of time and after you rebuild the program you simply just select the most recent .out in the list which will continue to load symbols instead of reloading the program. 

Regarding loading of the program, when I try to load the program using CCS using the debug mode symbol "bug"       button, the program is running as expected.

But when I use the Uniflash tool for loading the .out file into the target device, the program is NOT running as expected.

Hi,

  Your problem description is confusing to me. At first you said the function you change is not reflected when you load the code using CCS12. Now you said CCS is fine loading and running the code but not Uniflash. What do you mean the program is not running as expected when you load the code using Uniflash?

Please consider the issue as updated below: New additions are given in bold.

"

Source code updates are not working as expected in the generated .out file with CCS Version: 12.1.0.00007, Compiler TI v20.2.7.LTS and TivaWare_C_Series-2.2.0.295.

If I make a function change in the source code and rebuild the workspace, the .out file is getting generated successfully. There is no issue in generating the .out file.

If the generated .out file is loaded into the target, the behavior of the .out file is not reflecting the function change and is not working as per the revised source code updates. 

The generated .out file is loaded using 2 methods.

1) The first method is in the CCS Tool itself with the debug mode symbol "bug"       button, the program is working as expected.

2) The second method is using the Uniflash tool for loading the generated .out file into the target device. In this case the program is NOT working as expected.

The program is running as expected means the functional changes or new addition of the source code implementation is getting reflected in the execution of the software in the target device. If I add a function called DisplayText() which is to display the user specified text "TexasSupport", then calling the function in the software is expceted to display the text in the display screen. I hope this details are sufficient for you to proceed further to escalate to CCS experts. Also, Just to mention that there is no issue with the target device.

Recently, I have migrated from CCS version 10.x to 12.x and rebuilt the source code with the above said compiler and TivaWare library.

Earlier, I was using CCS version 10.x and TivaWare_C_Series-2.1.4.178 in which I did NOT face this kind of issues(single time also) in the generated .out file.

I have tried with multiple approaches of cleaning the workspace, rebuilding only the updated source file, deleting the entire "Debug" folder and rebuilding the entire workspace but none of the approaches are helping out to resolve this issue.

My query is: 1) Is there any extra steps to be considered while building the .out file using CCS Version 12.x?

2) What is the difference between 10.x and 12.x CCS version?

3) Does I need to perform any settings in uniflash tool to handle such issues?

Please provide your inputs to resolve this issue.

"

Hi,

  I will pass your post to our CCS experts for comments. 

Hello,

Before answering your questions, I want to confirm some things.

Ram V said:

1) The first method is in the CCS Tool itself with the debug mode symbol "bug"       button, the program is working as expected.

This works for BOTH CCS10 + TivaWare 2.1.4 AND CCS12 + TivaWare 2.2.0 executables? Or ONLY CCS 10 + TivaWare 2.1.4?

Ram V said:

2) The second method is using the Uniflash tool for loading the generated .out file into the target device. In this case the program is NOT working as expected.

This works for CCS 10 + Tivaware 2.1.4 but NOT CCS 12 + TivaWare 2.2.0 executables?

What version of UniFlash are you using?

Thanks

ki

1) Yes, First method works for BOTH CCS10 + TivaWare 2.1.4 AND CCS12 + TivaWare 2.2.0 executables

2) Yes, Second method works for CCS 10 + Tivaware 2.1.4 but NOT CCS 12 + TivaWare 2.2.0 executables.

We have tried with different Uniflash versions 5.0.x and 8.2.x

This is odd. The debug engine used by UniFlash is similar to what is used by CCS.

Are the compiler versions used always the same exact version in all cases?

No, the different compiler versions are used.

With CCS 10.x, the compiler  - Compiler TI v20.2.1.LTS

With CCS 12.x, the used version - Compiler TI v20.2.7.LTS

With UniFlash, can you try the out file from:

- CCS 10.x + Compiler TI v20.2.1 LTS + TivaWare 2.2.0

- CCS 10.x + Compiler TI v20.2.7 LTS + TivaWare 2.1.4