• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 189 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CC2652R7: Consecutive Builds without code change results in different .hex files

CC2652R7: Example of Consecutive Builds not building the same

Kenneth Thomas
Prodigy 220 points
Part Number: CC2652R7

Tool/software:

Hello,

So I opened a forum a while ago about an issue with building a project consecutively without changing the code. I didn't realize the forum would get locked else I would've just added it to that one but I would like to share an example project that I created using project_zero. I started with SDK: simplelink_cc13xx_cc26xx_sdk_7_40_00_77 and CCS Version: 12.7.0.00007. I removed the project_zero.h and .c files to condense the project files. The main issue seems to be using vsnprintf I tried to put it in the main.cpp file however I wasn't able to reproduce the problem I was seeing unless I made a separate class and had a function in there called the vsnprintf function. I would like to know why this would cause the project not to build consistently. Also to note this doesn't happen on every rebuild it but it can happen in a span of 1-10 rebuilds. I noticed this issue when I compared .hex files from a project built using the Command Line commands to one built via CCS. Attached along with this post is the file that I built and the original forum that I was getting help in.project_zero_LP_CC2652R7_tirtos7_ticlang.zip

Fourm:
e2e.ti.com/.../cc2652r7-consecutive-builds-without-code-change-results-in-different-hex-files

Best Regards,
Kenneth Thomas

  • 0
    TI__Guru**** 243820 points

    I presume the source code, compiler version, and build options never change.  Please verify the linker sees the all the object files, libraries, and other inputs in the exact same order.  

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 220 points

    Hey George,

    Yes the source code, compiler version and build options never change. To clarify when you mean to verify that the linker sees everything in the same exact order do you mean in the console. If so then I can confirm that they ARE different.

    Best Regards,
    Kenneth

  • 0 in reply to Kenneth Thomas
    TI__Guru**** 449771 points
    Kenneth Thomas said:
    To clarify when you mean to verify that the linker sees everything in the same exact order do you mean in the console. If so then I can confirm that they ARE different.

    Please try explicitly setting the link order in the project properties.

    See the below video for more details:

    https://www.youtube.com/watch?v=mN6SCwyxwbU

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 220 points

    Hey,

    So I tried explicitly setting the link order in the project properties just like it was shown in the video but it didn't seem to solve the issue.

    Thanks,
    Kenneth T

  • 0 in reply to Kenneth Thomas
    TI__Guru**** 449771 points

    Please send the full build output of both environments. You can copy&paste all output in the build console to a text file and attach the files to this thread (one file for each environment).