• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 955 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.

UNIFLASH: Uniflash on Mac M1

Michael Fuhrmann
Intellectual 770 points
Part Number: UNIFLASH

Hi everyone. CCS is pretty much usable on a Mac m1. However Uniflash is crippled. I can get load it but it just shows "Detecting Devices". Also I can't click on anything. Has anyone managed any work around?

  • 0
    Intellectual 770 points

    OK, so I've tried with an arm Vm and wine but still the same issue. "SLImageCreator.exe:Auto detect failure". Things that do work:

    • CCS and run debug work fine
    • Starting Uniflash, working with it is fine, just cannot flash anything.

    It might be a port issue or something like that.

    It's been nearly a year, would be good to have TI have it running on m1s.

  • 0 in reply to Michael Fuhrmann
    TI__Guru**** 162305 points

    Michael,

    Can you let me know which device you are using?  Is it a CC32xx of some kind?

    Neither CCS nor UniFlash officially support running on an Apple M1 however in general I am able to use both fine on my M1 MacBook Air.  The main issues I have are BigSur related and impact the UI in CCS.  CCSv11 will address the majority of those UI issues.

    I am guessing that you are on a CC32xx device due to the mention of SLImageCreator.exe.  For CC32xx, UniFlash is really just a front end and then we switch over to Image Creator.

    I will likely need to loop in the WiFi team if this is an ImageCreator issue.

       

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 770 points

    Hi John, thanks for the followup. It's a 3220SF launchpad and custom board. I did my best to find a workaround, Linux and arm windows vms etc. As I said CCS is completely workable even runtime debugging. But flashing an image is as far as I know impossible on an m1.

  • 0 in reply to Michael Fuhrmann
    TI__Mastermind 38980 points

    Hi Michael,

    "Auto-detect failure" has to do with detecting the device's COM port. One thing you can try is manually setting the COM port from the ImageCreator command line. See section 7 and 7.1.3 Program Image of the ImageCreator User's Guide.

    If that works, there is also a gui_cfg command that should change the default settings for the GUI tool.

    Best regards,

    Sarah

  • 0 in reply to Sarah P
    Intellectual 770 points

    Hi Sarah, thanks for your suggestion, however I can debug fine using CCS, so not sure why it would be a port issue. Is there any way to program a factory image using CCS?

  • 0 in reply to Michael Fuhrmann
    TI__Mastermind 38980 points

    Hi Michael,

    Debug uses JTAG. Flashing the CC3xxx devices is done over UART using the ImageCreator executable (or other production line methods).

    Persistent images cannot be loaded over JTAG due to device security features.

    Best regards,

    Sarah