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.

CCS 5.5 MSP430ware, force download\update to intermediate (previous) version

Other Parts Discussed in Thread: MSP430F5310, MSP430WARE

I have an MSP430F5310 project that uses MSP430ware version 1.80.01.03. I checked the project into revision control and then checked it out on another PC. I did not check the MSP430ware directory into revision control as it is provided by TI as a resource.


However, on the second PC, I had MSP430ware 1.60.01.11 and 1.60.02.09. When I imported the project, CCS reported a warning "This project contains unresolved buildable linked resources".

I did not realize at the time that I had any MSP430ware installed so I went to Help->Install New Software and selected MSP430ware. CCS informed me that MSP430ware was already installed and that it was switching to an "Update" (rather than New Install I suppose).

So, CCS installed 1.95.00.32 but my project was using 1.80.01.03. We have a policy here that all developer MUST be able to build the exact same .hex file. So, just using the newest is not always an option, especially on a quick patch or short schedule.

So, now I have the following version installed:

1.60.01.11

1.60.02.09

1.95.00.32

So, how can I get CCS to install an intermediate (previous) version (1.80.01.03 in this case)?

Regards,

Jim

  • Jim,


    You can download an installer by changing the URL to the version you need. MSP430Ware 1.80.01.03 can be found here:

    http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430ware/1_80_01_03/index_FDS.html

    By changing 1_80_01_03 to "latest" you will get the latest download page.

    Regards,
    Zack

  • Zack,

    OK, got it. That worked.Thanks.

    I guess there is no way to do this via the CCS update (or Install New Hardware) features.

    Jim

  • Jim, I completely understand your problem. Indeed, it is necessary that all parts of a build can be reproduced. This includes the tools themselves (the Compiler revision and any libraries). The more and more common practice of a ‘just in time installer’ that downloads the latest version during installation, contradicts this.
    I consider software that uses this kind of not-reproducible install
    as dangerous for serious development (that’s why I’m still using the old MSPGCC3.2.3 - all our code was built and verified with this compiler, even though there are more advanced versions out for long).
    And for private use of software, those installers are risky, as nobody can guarantee that I can re-install a game or tool again next year. Not as risky on a big company such as TI, but who guarantees that the servers of a small company are still running in a year or two.

    I understand that a manufacturer doesn't want to provide olde versions of his software anymore, but making older (sold and used) software revisions unavailable for a later re-install is somthing that might disqualify a development tool for professional development.

    IMHO, all versions of all tools and libraries (and documents!) should be available and selectable at installation (not requiring deep links) unless they have been originally delivered on an install media (and only there, so people are and can be responsible for keeping a copy of the install media). It makes an installer a bit more complex, but that’s a price to pay for providing tools for professional use.

**Attention** This is a public forum