• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 33 subscribers
  • Views 1543 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TM4C123GH6PM: How to Download old versions of Tivaware?

snellr
Intellectual 715 points
Part Number: TM4C123GH6PM

Hello,

I have a project which is dependent on an old version of Tivaware, but I cannot find that version available for download, even from an archive, anywhere.  Can someone point me to where I might be able to download TivaWare_C_Series-2.0.1.11577?

Thanks!

  • 0
    TI__Guru**** 244400 points
    Hello Snellr

    The older versions are not archived on the webpage for TM4C. There have been a lot of bug fixes in the software since 2.0.1.11577
  • 0 in reply to Amit Ashara
    Guru 117855 points

    Vendor's comment is "typical" yet unsatisfying.  (by "typical" - we've known (other) ARM vendors to respond similarly...Amit always strives to satisfy!)

    Lesson learned: each client-user MUST "safely store" ALL code & library elements - for future (even unexpected - especially unexpected) use!

    It appears that "re-casting" your appeal to, "General Users" (here) - and listing (promoting) your desired SW Version to the (easily noted) "Subject Line" of the thread - will prove "best bet."

    Should you have a "relationship" w/vendor's local office - (sometimes) they (may) "Pull a rabbit (or even past code ver.) from a (red) hat."

  • 0 in reply to cb1_mobile
    Guru 10570 points
    Even when vendor's brag about availability of older revisions (some do maintain them for just the reasons the OP outlined) when you ask you sometimes find that they have been 'lost'.

    Robert
  • 0 in reply to Amit Ashara
    Guru 10570 points

    Amit Ashara said:
    There have been a lot of bug fixes in the software since 2.0.1.11577

    No doubt, but updating the library could have increased the OP's scope of change by orders of magnitude.

    Robert

  • 0 in reply to Robert Adsett72
    TI__Guru**** 244400 points
    Hello Robert

    No. The fixes are in the APIs and driver files. The calling structure and return have not changed. So in my opinion the changes should not affect the application.
  • 0 in reply to Amit Ashara
    Guru 92251 points

    Amit Ashara said:
    The older versions are not archived on the webpage for TM4C.

    When faced with having to make a change to an existing product originally written by a different developer a sensible first step is to prove you can re-build exactly original executable before making any changes. For that you need to be able to obtain the original tools used.

    As an example I needed to make a change to a SYS/BIOS program for a LM3S2D93. The versions of the TI ARM compiler, SYS/BIOS and XDCtools used by the original project were all available for download from the TI website, even though they were no longer the "latest" versions. Fortunately the version of LM3S StellarisWare used in the original project was the still "latest" and therefore could still be downloaded.

    Why are TivaWare and StellarisWare different from the other TI tools by only allowing the "latest" versions to be downloaded?

    Amit Ashara said:
    There have been a lot of bug fixes in the software since 2.0.1.11577

    Conversely, have there been any changes which would break programs originally written for TivaWare 2.0.1.11577 ?

  • 0 in reply to Amit Ashara
    Guru 10570 points

    Amit the only way it would not affect the application is if there were no changes.

    Let me map out a scenario

    Testing and field experience has shown an edge case that was previously undetected. Covering this case requires a change in a manifest constant in one source file in an isolated region of the application.

    With the old library this would require a change to that constant, regression testing that file and any subsections deemed appropriate and a regression test of some parts of the complete application. If the product is agency listed and the change is small you may be able to limit the amount of retesting you do.

    If you replace the library then you now need to regression test every module and section of the application that uses that code. You have to check any work-arounds to any bugs that were in the previous version and ensure that at the very least they don't introduce issues. There's a good chance that you must re-test the complete application and if the product is agency listed they'll likely see this as a major change as well.

    A task of a day or two turns into months and many dollars.

    Robert

  • 0 in reply to Chester Gillon
    Guru 10570 points

    Chester Gillon said:
    When faced with having to make a change to an existing product originally written by a different developer a sensible first step is to prove you can re-build exactly original executable before making any changes. For that you need to be able to obtain the original tools used.

    Yep, and I've run into issues with that before myself.

    Chester Gillon said:
    Conversely, have there been any changes which would break programs originally written for TivaWare 2.0.1.11577 ?

    Pretty much by definition.

    A difference which makes no difference is no difference at all.
    ,1
    I knew the quote from Capers Jones but it appears to go back further

    Robert

    1 - William James Quotes

  • 0 in reply to Robert Adsett72
    Guru 47900 points

    Oh my - "How this forum has evolved!"    Literary notations & credits, manifest constants, & regression testing - all have "bubbled up!"

    "Defending the indefensible" (the weakly explained Vendor "pull" of past SW Versions) even by the talented Amit - proves difficult.

    The Regulatory Agency's intrusion is the VERY REAL, "Thorn in the side" of any/all attempts to "justify" past SW Version pulls!    "Code fixes" cannot justify the EXTRA pain & cost inflicted upon loyal users by such, "Far reaching" yet "short sighted" vendor decisions...

  • 0 in reply to Robert Adsett72
    TI__Guru**** 244400 points
    Hello All,

    I need to be as frank as possible. Yes, there are changes and tested with the "limited" number of examples that were there in TivaWare. The fixes that we have made to reported bugs are also based on the examples and for conditions that were not tested before. Enhancements that have been added also have led to updates for application notes or TI reference designs, that were otherwise done with HWREG macro.

    I do agree that not every possible scenario is covered by the tests. However we are trying to get the older releases archived on the web as well. It may seem to be a trival task, but not easy decision for me to make. We on the forum have highlighted this and do have the right audience, but will take time. However if the new release does break any of the applications, we could push for the older releases to be archived on the web too as it makes for a stronger case; and at the same time try to address the issue in the upcoming release.