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.

TM4C1294KCPDT: LMFlash Source Code

Part Number: TM4C1294KCPDT

This is related to my previous post regarding a bug in LMFlash. In that post I was told that there is no plan to update LMFlash.

Is there any possibility for an update (yet to be scheduled) in the future, or the release of the existing source code for patching by the community? If not, what is the reason that TI have deemed this project to be closed-source, given the availability of the availability of the open-source eflash utility? As I emphasised in my previous post, it is important for our organisation to have customers with limited technical ability able to perform Ethernet-based firmware updates, so we are still looking for solutions to the bug I shared in my previous post.

  • Hi Bryce,
    Unfortunately, the answer I gave e in the other post remains valid. There is no plan to update the LM flash programmer and neither the source code is available for public. eflash.exe is the command line equivalent of the LM flash programmer. If you could add the GUI interface to the eflash.exe then I hope it will suit your customer's need.
  • Charles Tsai said:
    Hi Bryce,
    Unfortunately, the answer I gave e in the other post remains valid. There is no plan to update the LM flash programmer and neither the source code is available for public. eflash.exe is the command line equivalent of the LM flash programmer. If you could add the GUI interface to the eflash.exe then I hope it will suit your customer's need.

    This hasn't actually answered any of my questions - you have simply restated what we already know.

    So I'll be more direct:

    • Is all further development of LMFlash discontinued?
    • Why is the source closed?
    • If all further development is indeed discontinued, how does TI support firmware updates on their newer microcontrollers?

    Thank you

  • Hello Bryce,

    Allow me to try and help answer these questions.

    1) We haven't entirely closed the books on future development for LMFlash, but at this time, as Charles mentioned, we don't have any updates planned to the program and if no critical issues occur that impact the functionality of the program for a notable set of users, then it is possible we won't make another update. In short, development will occur when the need arises, and right now we do not currently see such a need.

    2) The source code is closed for a few reasons, but one of the most pertinent ones is that if we opened the source code up for access to all, then we would put ourselves liable for supporting the source code if custom modifications are made and/or need to provide explanation/reasoning to why the program is written/functions as it does, both of which is beyond our support model for TM4C devices. Furthermore, the LMFlash program was never developed with intention to have source code be publicly released and at this point we would have many hurdles to cross just to be able to legally provide the source code. I am aware this explanation won't exactly be well-received, but please understand that we have to protect our own interests as well. While we offer many open source resources and support them to the best of our abilities through E2E and other means in order to ease development for our customers as much as possible, LMFlash is a rare exception where we simply cannot provide full open source.

    3) If there are any changes to how firmware updates are applied for TM4C microcontrollers in such a situation, that would certainly affect a notable set of users and would have to be dealt with accordingly by updating the program to ensure full compatibility with our TM4C portfolio. That is one of the possible needs that would certainly mandate an update to LMFlash.

  • Ralph Jacobi said:
    2) The source code is closed for a few reasons, but one of the most pertinent ones is that if we opened the source code up for access to all, then we would put ourselves liable for supporting the source code if custom modifications are made and/or need to provide explanation/reasoning to why the program is written/functions as it does, both of which is beyond our support model for TM4C devices. Furthermore, the LMFlash program was never developed with intention to have source code be publicly released and at this point we would have many hurdles to cross just to be able to legally provide the source code. I am aware this explanation won't exactly be well-received, but please understand that we have to protect our own interests as well. While we offer many open source resources and support them to the best of our abilities through E2E and other means in order to ease development for our customers as much as possible, LMFlash is a rare exception where we simply cannot provide full open source.

    I think this is actually quite a reasonable explanation, so thank you for taking the time to share that.

    Ralph Jacobi said:
    3) If there are any changes to how firmware updates are applied for TM4C microcontrollers in such a situation, that would certainly affect a notable set of users and would have to be dealt with accordingly by updating the program to ensure full compatibility with our TM4C portfolio. That is one of the possible needs that would certainly mandate an update to LMFlash.

    Understood.

    Ralph Jacobi said:
    1) We haven't entirely closed the books on future development for LMFlash, but at this time, as Charles mentioned, we don't have any updates planned to the program and if no critical issues occur that impact the functionality of the program for a notable set of users, then it is possible we won't make another update. In short, development will occur when the need arises, and right now we do not currently see such a need.

    It's unfortunate that TI doesn't see this as a critical issue for a notable set of users - I'd argue otherwise. Regardless, it is good to know that the proverbial door hasn't been shut.