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.

CCSTUDIO: New Mac - M1 Monterey - no love from v. 10/11 installers

Part Number: CCSTUDIO
Other Parts Discussed in Thread: MSP430FR5849

Moving to a new Macbook Pro w/ M1 Pro chip and Monterey.  Can't get the CCStudio installers for v. 11 or v. 10 to work - they launch but the intro screen never appears. (both remote and single file) 

Version 9 I managed to install with help of Rosetta, but it spits out a bunch of null pointer errors and doesn't do the simplest things. 

My current Macbook is (2016/Mojave - because 32 bit legacy stuff)  has v. 8 on it, which is fine.  Not doing a lot of dev, mostly maintenance.  It runs these installers fine though.

Anyway, out on bleeding edge I guess and wondering if and when I can get CCStudio running on new machine.

thx,

Jim

  • Jim,

    I had another user hit something similar where the installer would not run properly on a BigSur M1 machine.  It basically would bring up the initial installer screen but it was blank.  I was never able to reproduce this.  I would recommend CCSv11 for BigSur or Monterey.  There were changes introduced in BigSur that cause a lot of GUI issues in CCS/Eclipse.  CCSv11 has a newer Eclipse that addresses the majority of them.  I have not had any issues running the installers on my M1 machine.

    Let's see if we can get some logs of what is going on.

    Start with the single file installer for CCSv11

    double click on the .dmg to open it.

    Then drag the .app and contents items from the dmg into a folder.

    Then open the terminal app and go into that folder and run:

    open ccs_setup_11.0.0.00012.app --args --syncdebugtrace /tmp/debug.txt

    You will likely get a pop up like this.  Click Open.

    Normally you would then see the splash screen and then this:

    If you can then attach the debug.txt file that will be in the /tmp folder that would be great.  You can also change the command to put the txt file in a different writable folder.

    Regards,

    John

  • John,

    Thanks for the reply.  I followed your instructions and took a look at the debug.txt file.  It is 1.4 MB and not much of it is readable.  Am a bit of a noob to this forum - don't see obvious means of attaching file.  Pasting 1.4 MB of gibberish doesn't seem polite.  Notice a installer log file w/ 0 bytes was created at same time in /tmp, fwiw.

    cheers,

    Jim

  • Also - splash screen never comes up.  In version 9 installer it does, and v. 11 installer works fine on my old Mojave machine. 

    Menu for the installer temporarily flashes 'File, Edit, Window..' and then switches to single item - app name.  'About...' under that menu does nothing, nor can you quit via that menu. (Enabled menu item, but doesn't do anything.)  Imagine that the splash screen is there but not visible, and possibly invisible dialog box asking if I'm sure I want to quit.

  • To attach a file just zip it up and then click on the Insert item and then "image/video/file"

    The file is from the installer software that we use and has to be decoded.  We have our own readable logs but in this case we are not getting that far.

    John

  • Ah, thanks.  Didn't spot that.  Here is zipped file.debug.txt.zip

  • Thank Jim.  We typically have to work with the vendor to decode the log.  I will let you know what we find.

  • Ok we actually heard back from InstallBuilder already.  They think it is an issue introduced by Monterey.  It impacts installers that have M1 support in them.  CCSv9 does not so it requires rosetta.

    I don't have a Monterey machine with me today but a workaround suggested is as follows ( I will try it tomorrow).

    In finder or I guess terminal would work as well.  Go to /ccs_setup_11.0.0.00012.app/Contents/MacOS

    Then run osx-x86_64

    Basically should run the x86 version of the installer instead of the Arm one.

    I will try this out tomorrow morning as I don't have an M1/Monterey machine with me today.

    John

  • This appears to have done the trick - installer running now.  Thanks for your help.

    cheers,

    Jim

  • Jim,

    I am at home now and can see the same on my M1 Monterey machine.  I just upgraded this one a few days ago.  I had been able to install CCSv11 on it fine when it was running Big Sur.  However now with Monterey I see the same installer behavior as you.  When I run the installer the normal way it does not come up but if I run the x86_64 version it is fine.  

    We are officially adding Monterey support in CCSv11.1 which will be out in Dec.  This issue will need to be addressed for that release.

    Regards,

    John

  • Great to hear.  BTW, I got one of my MSP430FR5849 CC8 projects up and running with only a few hiccups (compiler couldn't find intrinsics.h, linker couldn't find liba.c) which, compared to my efforts to get an Xcode project moving was pretty painless.  Thanks again.

    Jim

  • Good to hear that you got your projects going.

  • Then run osx-x86_64

    I just got a new M1 Pro MacBook Pro and the main installer wouldn't work (hang with no splash screen). I tried running the osx-arm installer with the same result.

    Running the x86 version works. Looking forward to the 11.1 version which will be native for the M1?

  • Hi,

    CCS is based on Eclipse IDE. For this moment does not exist naive build of Eclipse IDE for M1.

    Jan

  • Currently, it is just the installer that is native for M1.  At this time there are no set plans for rebuilding all of CCS for Arm (M1).  

    Regards,

    John

  • The workaround for installing CCS on an M1 Mac is later in this thread.  It says:

    Go to /ccs_setup_11.0.0.00012.app/Contents/MacOS

    Then run osx-x86_64

    What does it mean to "Go to /ccs_setup..." ?  There is no folder/directory on my Mac or in any download folders where I could find this.

  • Run the .dmg to start

    That will then open a window with the .app in it.  At this point you can bring up the context menu and choose to show the contents.

    That will then open a Finder window. 

    From the open /Contents/MacOS

    In that folder you will see osx-x86_64

    Run that