• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 33 subscribers
  • Views 1569 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: The future TM4C ?

romain reicher
Prodigy 140 points
Part Number: TM4C123GH6PM
Other Parts Discussed in Thread: SEGGER

The EKTM4C123GXL kit is really popular.
Is a new version being considered?
- Integration of the XDS110 debugger (same as the SimpleLink family) with external JTAG / SWD.
- Jumper to isolate USB power and debug signals.
- Hibernate pins accessible

I have a very good experience with MCU TM4C and I think they are very good products.

The recent SimpleLink ecosystem offers a very interesting solution with the unified SDK part. In addition all the new board Launchpad are very very good.
But what will become of the Tiva TM4C family? Is there a family update plan?

KR

rrom

  • 0
    Guru 117855 points

    rrom said:
    Is there a family update plan?

    Is it not true - that by announcing such a plan here (publicly) - dreaded competitors (also) receive alert/advisement?

    Such questions - when straying so far from "MCU Tech-Centric" - are best directed to your local, Vendor's Sales Office.

    To your question re:  "XDSxxx w/external JTAG/SWD:"    It is already possible to "Bypass/Disable" the on-board MCU (serving as ICDI).     You should note a "row of pins" - suitable to receive a SIP header - located just beneath the ICDI MCU.    (you'll also note one pin marked "EXT" - which allows, "ICDI Disable" - such that  "EXTERNAL JTAG or SWD" may be introduced.)      

    Firm/I - always & only - employ this "External Debug/Program" method.      Our findings reveal that the "World's Leading JTAG/SWD probe" (Segger's J-Link) proves more robust, outperforms, and by being (properly) "Vendor Agnostic" - accommodates (most) ALL ARM MCUs - from "multiple vendors."     (is it not "unlikely" - that "one & only one vendor" - at all times - will, "Outperform the Market?") 

    You ask for a,  "Jumper to isolate USB Power & debug signals."     If we assume that those debug signals aim towards the "User MCU" (not the ICDI MCU) - then the above should serve your "debug signal" goal.    Your use of  "isolate" proves somewhat vague - again note that the "External JTAG/SWD" signals are introduced via a "separate header" (populated by user) & such may qualify as,  "isolated."

  • 0 in reply to cb1_mobile
    Prodigy 140 points
    cb1. Of course, this is not the place for an announcement.
    My initial question concerns above all the hardware aspect of the ecosystem (Tiva Launchpad)

    For competitors licensed at ARM, given the current trends, the strategy is I think more oriented to SOC + wireless dual core or high performance or mcu entry low power range. And in these market areas I think that TI has several years of advances.
  • 0 in reply to romain reicher
    Guru 117855 points

    Thank you - it (was) uncertain if you had that, "Place & form of disclosure" clarity. Clearly (now) - you do.

    As you well note - SOC has made gains - yet the appeal of an "unvarnished" MCU continues. The response & record w/in the "free marketplace" will (usually) "advise the future."

    Have I answered your "opening post's" JTAG/SWD issues to your satisfaction?

  • 0 in reply to cb1_mobile
    Prodigy 140 points
    Yes, you answered my question about the ability to do JTAG in / ext. And I already knew this feature of the ICDI debugger.
    However, the ICDI debugger only allows the standard JTAG mode and I use a Segger JLink that offers better performance in terms of breakpoints and trace function.
    It seems XDS110 offer consumption trace capabilities ?

    Regards
  • 0 in reply to romain reicher
    Guru 117855 points

    Firm/I "see no point" in using (lesser) JTAG/SWD probes - thus I have no (educated) comments re: XDS et. al..

    As you, "already knew" of the, "External JTAG/SWD signal introduction means" - the intent of your opening post (which appeared to seek such info) - has been clouded.

  • 0 in reply to cb1_mobile
    Prodigy 140 points
    Sorry sir, not really understand all your last post !!!
  • 0 in reply to romain reicher
    Guru 117855 points

    Your first post ASKED for Guidance in obtaining, External JTAG/SWD usage.     I believe that I, (highly) detailed) - "just how that is achieved."
    Your more recent post stated that you, "knew how to achieve such external usage!"      

    What (then)  "was the point" of your (opening)  forum question?        (on occasion - such "already known/answered questions" are asked to,  "Verify the "truthfulness/capability" of the responder."     (especially true in the courtroom - but unwise/unlikely - to be employed here!)    (A Tech Forum.)     Same "holds/proves" true - for your,  "Reveal your MCU roadmap" (which you "knew" was improper - to be presented here) - might a "tendency" have been noted?

  • 0
    Genius 3850 points

    I hope they continue to be a meaningful player in this space. the TM4C family is some of the most feature-rich M4F chips out there. Not sure how many of those chips they sell, however.

  • 0 in reply to cb1_mobile
    Prodigy 140 points
    Sorry for my lack of clarity. I simply rephrase my original question.

    Does TI plan to redesign the TM4C Launchpad kit in the same way as the MSP432Launchpad?

    With my greatest respect, CB1 KNOW that your way of responding (WITH too much parenthetical expression) is not so obvious to understand (IMHO)
  • 0 in reply to Danny F
    Prodigy 140 points
    Yes totally agree Danny F. SOC is great and Tivaware too
  • 0 in reply to Danny F
    Genius 4455 points

    Danny F said:

    I hope they continue to be a meaningful player in this space. the TM4C family is some of the most feature-rich M4F chips out there. Not sure how many of those chips they sell, however.

    I agree. The TM4C family is very important to us. We have selected several parts from the TM4C family for our new products and are in the very painful and costly process of migrating our extensive codebase to this family, coming from a totally different vendor and processor architecture. This represents a major commitment to TM4C on our part, especially when you consider the costs already invested into redesigning our hardware around TM4C.

    So far we are very happy with the TM4C family.

    I would love to see more growth and improvement in TM4C, whatever that might mean, whether it's from the standpoint of hardware or software. For example, TivaWare might benefit from an update, even if only to incorporate newer versions of some included 3rd party code -- the first that comes to my mind is lwIP. TivaWare includes lwIP-1.4.1; the newest available is 2.0.3 and includes important bug fixes. It is on my to-do list to update our codebase to use lwIP 2.0.3. If TI beats me to it and issues a TivaWare update, that would benefit everyone in the TM4C community.

    The bottom line is that seeing updates of any kind, even just a TivaWare update to bring 3rd party packages up-to-date, instills confidence in people like me. :-)