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.

MSP-FET: MSP430Flasher + MSP-FET - STILL no macOS 10.14 Mojave update - TI, please help.

Part Number: MSP-FET
Other Parts Discussed in Thread: MSP-EXP430FR5994, MSP430FR5994, UNIFLASH, , MSP-FLASHER

Hello,

This is a "related" question to the thread "MSP-EXP430FR5994: macOS 10.14 Mojave — Upload to MSP430FR5994 ezFET Fails". Since that thread is marked "TI Thinks Resolved" (it is not really) and there is still an issue unresolved since November, I thought I would raise it here.

While CCS now does support macOS Mojave's revised USB port naming (my term) when detecting the MSP-FET, the MSP430Flasher is still stuck at version 1_03_18_00 which does not. I believe UniFlash is also non-functional on Mojave.

If anyone at TI--perhaps in their tools department--is reading this, or if you know someone there, please ask about MSP430Flasher support. It is really causing problems for at least this user. Given that CCS, and by extension the debug stack, seems to include a fix then why not MSP430Flasher?

Regards,

Bill.

  • If I remember right, TI will not update MSP-Flasher anymore, they push UniFlash as MSP-Flasher replacement. However, problems related to macOS Mojave's revised port naming are fixed inside MSP Debug stack dll, and I guess that (old) MSP-Flasher just should be linked to new dll to work OK.  

  • Hi Bill,

    I finally got a response from our team that supports the MSPFlasher and UniFlasher tools.
    They have indicated that MSPFlasher is being deprecated (no new fixes or features added) and UniFlasher will be recommended as the tool going forward.

    Regarding the bug fix, they indicated that if you have latest version of CCS and UniFlash 4.6, then it should work for you.
    Give it a try and let me know.
  • Hello Bill,

    It has been some time since your last response, so I'm assuming you have resolved your issue and I will be closing this thread.
    If this is not the case and you need additional help, you can re-open this same thread.
  • Dennis,

    Yes, it is resolved, so to speak. If you have the ear of anyone that sets the roadmap for developer tools, let them know that the facility to automate (programmatically customize) the flashing of MCUs in a production environment is greatly enhanced by the simple command line interface that MSP430Flasher provides (or, now, "provided"). We don't mass-flash the same code, but rather have many different code files and need to have their selection automated.

    I can use the command line interface of Uniflash but it is more involved and seems to require I create a separate configuration file and set of programs (dslite?) that gets handed off for controlling the process. I just hope that my programming of such a process doesn't get sidelined someday with another "DEPRECIATED" notice for the CLI to Uniflash. ;-)

    Thank you for your help in communicating with the Tools group.

    Cheers,

    Bill.

  • Hi Bill,

    Yes, I will most certainly pass this feedback to the tools team. It's comments like this that help steer the direction or roadmap.
  • Hello Bill,

    Our tools team informs me that they did add the fix for the mac OS Mojave to MSP Flasher (v1.03.19.00) and is now available if you still require using it over Uniflash.

**Attention** This is a public forum