• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 33 subscribers
  • Views 965 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.

Am I able to leverage Stellaris code on TM4C?

TI Lady
Genius 4025 points

My customer has designed in LM3S9B92 and is looking to redesign due to the obsolescence.  Are they able to leverage any of their code in any currently supported TI MCU's (TM4C series)?

Thanks

  • 0
    Guru 47900 points

    May I report that my small firm has employed (most) of past "StellarisWare" code written for "LX4F231" (never were any LM4F's made) w/success w/in vendor's TM4C123 series.   And - to meet multiple clients' desire to avoid "RebrandWare" (and its numberous issues) we continued w/StellarisWare 9453 (which "uniquely" supports LM3S & LX4F).

    Not all code will run w/out (some) change/accommodation.   And if the peripheral match (or lack of same) between MCUs (past & present) is significant - your time & effort requirement - will increase.

    IMO this is a (sure) first-order task - which probes to see how much of the past code (continues) to function - when loaded w/in your new MCU.   Failure to make, "Last time/Lifetime buy" of those past MCUs will prove costly and time/effort consuming - unlikely your (customer) will make such mistake, again...

  • 0
    TI__Guru 59540 points
    Hello TI Lady,

    As StellarisWare was the precursor to TivaWare, there will be many similarities. As cb1 mentions, in many cases the code will port without too many modifications. However, there are some words of caution in that StellarisWare is not being updated and all efforts are to support the existing versions of TivaWare for the latest products. This doesn't mean that it isn't possible to maintain existing code bases and continue to reuse and redeploy that software. The primary obstacle I believe you will have is the device compatibility in regard to pin functions and available features.

    The document at this link outlines some of the key differences and care abouts when migrating from StellarisWare to TivaWare: www.ti.com/.../spma050a

    Keep us posted on the progress with your customer and let us know if there is any support we can offer to help with the transition.
  • 0 in reply to Chuck Davenport
    Guru 47900 points

    Perhaps it bears noting that "StellarisWare 9453" was very well developed, tested & received by the community (LM3S & LX4F) - and as such - does not require the (near constant) "UPDATING" - so repeatedly required by vendor's "ISSUE PLAGUED," "RebrandWare!"  

    In fact - my firm's major clients - getting "wind" of the "issues" directed that my firm (only) develop under the STABLE, PROVEN, EXHAUSTIVELY TESTED STELLARISWARE 9453.   Thus - we've never employed rebrandware!       Small tech firms must deliver robust product - on time - and it proves (pointless) to migrate from a, long-proven, "Winning Hand!"   (to one - "not so much" ... ...   to be kind...)

    Lack of Updates - in this proven/robust StellarisWare case - proves NO/ZERO Disadvantage!

  • 0
    Expert 2355 points

    Hi TI Lady,

    I recommend having a look at: http://www.ti.com/lit/pdf/spma049 for salient differences.

    Regards,

    Dave

  • 0 in reply to SourceTwo
    Guru 117855 points
    Yet - does that "look" (at all) describe the terrible "over-reach" which plunged the stable, robust StellarisWare into, "NotsoGoodWare?" (aka Constant_UpdateWare)

    We note the (slowed reaction) which caused this requirement (by missing "Lifetime Buy") is alive/well - a lesson (apparently) unlearned...
  • 0 in reply to cb1_mobile
    TI__Guru 59540 points

    cb,

    Although the point of aggravation over our periodic updates of the TivaWare code set  is well noted, it is not mentioned that the bulk of these updates are, in effect, work arounds for newly found device issues. Not that this is any redemption or reasonable excuse for the updates/found issues, but it is much more palatable and comprehensive for field units to "fix" the issues through SW rather than through hardware updates. It is also worth noting that these same work arounds not being present in the older StellarisWare would represent a potential issue on the newer HW if StellariWare were used with the newer HW.

  • 0 in reply to Chuck Davenport
    Guru 47900 points

    Chuck Davenport said:
    It is also worth noting that these same work arounds not being present in the older StellarisWare would represent a potential issue on the newer HW if StellariWare were used with the newer HW.

    Possibly - although our use of "4C123" - strictly and entirely - under the jurisdiction of StellarisWare 9453 - has not revealed any such (potential) issues.

    Major clients insist that there is FAR MORE POTENTIAL for such "issues" under the (very/admittedly) buggy, newer, non-robust, software regime.    The non-LMI team went for a "major SW overhaul" rather than the KISS (or always safer, incremental) method which my firm teaches & exploits.  

    That "Kill StellarisWare "decision" (some call over-reach) still plagues many here.   StellarisWare 9453 escapes all of those (unwanted) improvements - which led to a wellspring of unanticipated consequences - ALL BAD!