Installing legacy TI-ARM compilers for CCSv6

Martin Bertsche

Hi TI,

we have a project that was started about 9 Months ago. At the time the TI-ARM compiler's patchlevel was 5.1.8. New developers joining the project are having trouble to get the exact compiler version since our CCSv6 Installer will distribute version 5.1.6. While they can update to higher versions like 5.1.13 or 5.2.5 using "Help"->"Install New Software..." they cannot just update to version 5.1.8.

Since version 5.1.8 does not seem to be on the Code Generation Tools update site, could you please provide a link to the proper update site or a link to a zip archive containing the update?

The reason why we need the exact compiler version is that there are some subtle differences in the binary output that we cannot explain. We have been testing with binaries from the 5.1.8 version so far. We fear that the current test results could be invalidated by changing the compiler.

Regards,

Martin Bertsche

over 8 years ago

0 Martin Bertsche over 8 years ago

Prodigy 250 points

Nevermind, I found the checkbox in the dialog to show all patches of any version.

0 George Mock over 8 years ago in reply to Martin Bertsche

TI__Guru**** 232880 points

That's the best way to do it. -George

0 Martin Bertsche over 8 years ago in reply to George Mock

Prodigy 250 points

Well I found there actually is a small problem with this way which I couldn't find a workaround for. While "Install new software..." dialogs allows to install later versions of the "Code Generation Tools" I cannot install versions below my currently installed version. Is there a solution to that as well?

Regards,

Martin

0 George Mock over 8 years ago in reply to Martin Bertsche

TI__Guru**** 232880 points

How far back do you need to go? I can see version 4.6.6. That was released over 4 years ago.

Thanks and regards,

-George

0 Chester Gillon over 8 years ago in reply to Martin Bertsche

Guru 92251 points

Martin Bertsche said:
I cannot install versions below my currently installed version. Is there a solution to that as well?

See http://processors.wiki.ti.com/index.php/Compiler_Updates#Installing_Older_Versions for a possible solution.

[https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/336490 has some more information]

0 Martin Bertsche over 8 years ago in reply to Chester Gillon

Prodigy 250 points

Thank you for your reply.

Chester Gillon said:

See http://processors.wiki.ti.com/index.php/Compiler_Updates#Installing_Older_Versions for a possible solution.

I cannot verify that the downgrade to a lower version compiler is possible using that method when only the patch level (major.minor.patch) changed. The reason for that is indeed described in the discussion referenced below. I already had the solution given there in mind. However I was expecting a more convenient solution.

Chester Gillon said:

[https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/336490 has some more information]

In my opinion, compiler versions that produce different binary output on a reasonably sized project (20 ksloc or more) using the same command line, should not just lead to an increment of the patch level but also to an increment of the minor version.

Embedded people get terrified when after 3 years we pull the code of a long verified and validated product to change some constant just to see that in the resulting binary there are many more changes than just the expected ones.

So please consider this, and don't continue making it a chore for your customers that have to incorporate this in their processes (...write manuals and so on...)

Regards,

Martin

Code Composer Studio™︎

Code Composer Studio forum

Installing legacy TI-ARM compilers for CCSv6