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.

Why is TivaWare not an RTSC/XDC module/package?

Why is TivaWare software not taking advantage of the wonderful RTSC/XDC [1] framework?

And, how exactly is the ti.drivers.* related to TivaWare? Afaiu, ti/drivers are a higher-level abstraction, but it is unclear how exactly they dependend on TivaWare and why TivaWare is not a nice clean XDC package/module that the higher-level module would depend on. It seems that including a ti.drivers.* module in a .cfg file instructs the linker to pull in archives with a suffix ti/drivers/lib/*_tivaware.a*. What's the relationship between the code in packages/ti/drivers and in products/TivaWare (both logical and physical)?

[1] http://rtsc.eclipse.org/docs-tip/XDCtools_User%27s_Guide

  • Whom - besides you - describes the RTSC/XDC framework as wonderful?

    Some independent review - from both known & qualified sources - would make your "ad" for RTSC more compelling...

  • Whether it's "wonderful" or not is hardly of consequence. What's important is consistency: TI-RTOS is built as a set of RTSC packages. Even the build scripts for TivaWare within TI-RTOS build system look like a hack.


    I was looking for the arguments against having a consistent ecosystem.

  • Alexei Colin said:
    TivaWare software not taking advantage of the wonderful RTSC/XDC [1] framework

    If "wonderful" is of "no consequence" - why was that your, "out of the box" (yet unsupported) introduction?...

  • The point is supported by the fact that the current arrangement is so hacked together that I can't get it to build. I am still curious as to what is the argument of having this oddly (non-)integrated piece of software in an otherwise consistent set of TI-RTOS RTSC packages.

  • For a concrete example of the hackery: see the hardcoded suffixes that turned up in this question:
    http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/299202.aspx

  • Consider it might have to do with history.

    TivaWare is an 'update' of StellarisWare, and StellarisWare originated at LM, not TI. And, it predates any CMSIS efforts by ARM.

    Consider further, not everybody needs an RTOS within his Cortex M setup. A lot of customers are obviously happy within the Stellaris/TivaWare environment. No company will put much effort in products that (almost) no one requests/needs - at least not for long ...

  • f. m. said:
    Consider further, not everybody needs an RTOS within his Cortex M setup. A lot of customers are obviously happy within the Stellaris/TivaWare environment. No company will put much effort in products that (almost) no one requests/needs - at least not for long ...

    My understanding is that this is exactly where RTCS shines: you can link in just one module if you want to. RTCS is just a (very flexible) build framework.

    Regarding further development of TI's XDC which later became RTCS under Eclipse (with the noble goal of making the technology available without vendor dependence): (1) the initiative, the design, and the implementation used for several years (according to whitepaper/proposal) came from TI, (2) moving their (and other vendor's) many packages seems like a much more questionable and pointless undertaking ("that no one asked for") than making the one oddball piece of the puzzle comply with the rest.

    Obviously, RTCS is not a perfect solution (neither is anything else), but inconsistency is much much worse.