• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 538 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.

CCS/MSP-EXP430G2ET: Can't connect to MSP430G2533 from cloud version of CCS

Andrew Johnson
Prodigy 50 points
Part Number: MSP-EXP430G2ET
Other Parts Discussed in Thread: MSP430G2553

Tool/software: Code Composer Studio

I have a MSP430G2553 connected through this launchpad.  On the cloud version of CCS, running through Chrome, I cannot load a program to the board.  It builds ok but when I run it I get the following error:

Needless to say, power cycling didn't work.  The initial TI Cloud Tools page shows the launchpad connected (apologies for the image size):

In frustration, I downloaded and the offline CCS, set that up and was able to build and run the program via that.  I really didn't want to do that though, but I suppose it is a workaround - I did have to change the target configuration first, but the target configuration on the cloud version matches.  I'm guessing that it is to do with some interaction being denied between the remote server and my Mac - although I've tried with the firewall turned off.

I'm using MacOS Mojave 10.14.3, Chrome 72.0.3626.121.  The plug-in is enabled and it isn't set for incognito.

Thanks

Andrew

  • 0
    TI__Guru**** 162305 points
    Andrew,

    I have setup the same board on my Mac to try to reproduce. My device detection screen looks the same as yours.

    When I import an example from Resource Explorer to CCS Cloud I just get the option to Run and not Debug. Which causes some warning bells for me. I then get the same error as you.

    I think this may be a case where the old G2553 LaunchPad is being supported and not the new one. We were supposed to swap that around so that the new one was supported and not the old but it doesn't look like it has happened yet. I will get some more info.

    Regards,
    John
  • 0 in reply to JohnS
    Prodigy 50 points
    Thanks John, that would be great.

    I too tried an example from Resource Explorer and got the error. IIRC, reading some stuff, Mac OS doesn't support debug but does support loading, and it supports the new -ET boards but not the old ones. It is supported in the standalone version of CCS, but I don't know about debugging, not tried that and I would presume they are the same build, more or less?

    I think the cloud and standalone versions both use Node? It could be a configuration issue with incoming messages (from the web) but I don't know anything about Node.

    Regards

    Andrew
  • 0 in reply to Andrew Johnson
    TI__Guru**** 162305 points
    Our Cloud tools are less flexible than our Desktop tools. Today they basically assume a debug connection based on the device selected. In general for LaunchPads this works fine. Unfortunately for G2553 we have 2 different LaunchPads and the debug hardware on them is different.

    For Windows both the new and old G2 LaunchPads are supported in the Cloud. For Mac and Linux we were using a different software stack to support the old G2 and it just supported Flashing and running the device. With the new G2 LaunchPad it is supported by our proper stack on Linux and Mac. The problem is that the Cloud tools when they see G2553 is in use on Linux or Mac use the special stack for the old LaunchPad which doesn't work on the new one. The tools are supposed to change to assume the new LaunchPad (which means the old one will no longer be supported on Linux/Mac). I will get an ETA on when that is happening.

    John
  • 0 in reply to JohnS
    TI__Guru**** 162305 points
    Looks like the change for this are all done and it is just waiting for deployment to the Cloud. Current ETA is 2 weeks.

    Regards,
    John
  • 0 in reply to JohnS
    Prodigy 50 points
    Thanks John, that's good news.