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

MSP-EXP430G2 not working with CCSv6

Thaddeus Niemeyer
Intellectual 350 points
Other Parts Discussed in Thread: MSP430G2553

This post is actually a branch of an earlier post which (at the present time) is still not resolved.  That thread provides a lot of details about my configuration.

Problem:  I am unable to connect to my Launchpad MSP-EXP430G2.  I keep on getting the following message:

Error initializing emulator:
Not supported by selected Interface or Interface is not initialized

Here is some useful data:

1) I DO see my Launchpad show up in the Device Manager as a "MSP430 Application UART" under "Ports (COM LPT)".

2) I have tried various USB cables from the PC to the LaunchPad.  All give the same result.

3) There is a valid DIP chip installed on the Launchpad board in all tests.

4) I have 4 LaunchPad boards of the MSP-EXP430G2 variety.  I have cycled through all of them to eliminate a bad board as the cause. They all have this problem.

5) I have validated that my CSS project settings have the right chip.  

6) I have also tried changing the USB connection port to see if that does any good.  No luck

7) I have validated the firmware using the "LaunchPadFirmwareUpdater2.0.exe" program from TI.  This program says the firmware on the Launchpad is up-to-date.

Thad.

  • 0
    TI__Guru* 77821 points
    Hi Thad,

    Out of curiosity, what OS are you using on your computer?

    I have been unable to reproduce your issue on my PC - I have the same CCS version and tools version as mentioned in the earlier post, and am able to download and debug to MSP-EXP430G2 Launchpad with an MSP430G2553 device with no problems. I know this may sound like a pain, but I'm wondering if something could be wrong with the CCS install. To test this theory, you can actually make a parallel install of CCS (so that you don't have to uninstall your existing one in case this doesn't work) - when prompted by the CCSv6 install, you simply point it to install in a different folder. For example, instead of the default C:\ti installation location, I would make a folder and point it to install in C:\ti_clean for example, just to have a fresh install to compare.

    Regards,
    Katie
  • 0 in reply to Katie Pier
    Intellectual 350 points

    So if it is that easy ... just change the directory from c:\ti\ccsv6 to something else, then I will give it a shot this afternoon.   I was worried however that a bunch of DLLs would be copied to other locations not under the c:\ti directory.

    Thad.

    Postscript:  OS is Windows 7 (SP1) running on Dell Precision m4600

  • 0 in reply to Thaddeus Niemeyer
    Intellectual 350 points

    I have installed a new copy of the CCS software.  Launched CCSv6 and was prompted with this screen.  Last time I came to this screen, I decided to do the updates.  Should I do so now for this test?  The thing is, these software already exist on my computer under the same directories listed.

  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points
    As far as I know it will make a totally separate install - but I have moved this post to the CCS forum in case they have other feedback.

    This is actually the method I use for customer support to be able to have multiple CCS sub-versions on my machine when needed. I think you need to change the folder at the top level to not be C:\ti. If you tell it to use C:\ti\ccsv6 you'll be colliding with your current install because that already has a folder called that. So better to change the "ti" folder to something else.
  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points
    For the new products discovered, I would probably tell it no if you are trying to keep everything separate. It is actually saying that it went and found those already existing on your machine in a different directory I think. When I am trying to keep things 100% separate, I would tell this no, and then go to the App Center and have it install products from there (have it put them in your new base directory, whatever you call it, instead of C:\ti).
  • 0 in reply to Katie Pier
    Intellectual 350 points
    Sorry, how do I get to the "App Center"?
  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points
    Look under View > CCS App Center. This will give you options to find and update additional components like MSPware, that you might want. I don't think these will affect you being able to program the Launchpad however, if you want to test if that is working first.
  • 0 in reply to Katie Pier
    Intellectual 350 points

    I installed a new CSS in c:\ti2.  After doing the updates, I see some key distinctions between my old install and new install.  Some of them don't make sense to me.  Here is the old install directory listing (in c:\ti)

    01/22/2016  02:25 PM    <DIR>          .
01/22/2016  02:25 PM    <DIR>          ..
01/22/2016  02:43 PM    <DIR>          ccsv6
01/22/2016  02:43 PM             1,811 Code Composer Studio 6.1.2.lnk
01/07/2014  11:55 PM    <DIR>          Connectivity
12/30/2013  05:01 PM    <DIR>          grace
01/22/2016  09:45 AM    <DIR>          msp430
01/21/2016  11:49 PM    <DIR>          simplelink
01/21/2016  11:53 PM    <DIR>          tirtos_simplelink_2_13_00_06
01/22/2016  01:59 PM    <DIR>          xdctools_3_31_00_24_core
01/22/2016  02:41 PM    <DIR>          xdctools_3_31_01_33_core
               1 File(s)          1,811 bytes
              10 Dir(s)   8,311,832,576 bytes free

    And then the new install under c:\ti2

    01/28/2016  01:54 PM    <DIR>          .
01/28/2016  01:54 PM    <DIR>          ..
01/28/2016  01:54 PM    <DIR>          ccsv6
01/28/2016  01:54 PM             1,820 Code Composer Studio 6.1.2.lnk
01/28/2016  01:52 PM    <DIR>          msp430
01/28/2016  01:51 PM    <DIR>          tirtos_c2000_2_12_01_33
01/28/2016  01:52 PM    <DIR>          tirtos_msp43x_2_14_03_28
01/28/2016  12:09 PM    <DIR>          xdctools_3_31_00_24_core
01/28/2016  01:51 PM    <DIR>          xdctools_3_31_01_33_core
               1 File(s)          1,820 bytes
               8 Dir(s)   8,305,692,672 bytes free

    See any problems here?  Meanwhile, I will start doing my tests with the new CCS install ...

  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points
    Hi Thad,

    As far as I know, nothing really looks amiss - all that the differences mean I think is that you maybe haven't installed support for some things yet (e.g. grace, simplelink and TI-rtos for simplelink). You can always add these components at a later date.
    -Katie
  • 0 in reply to Katie Pier
    Intellectual 350 points

    Ok, so the good news is:  Launchpad boards are working again.  I'm very happy about that!  Even more, the MSP-FET430UIF also appears to be working again with my own boards.  (I will however reply to the thread for that separately).

    That said,, I'm getting the following screen pop up.  But the App Center says that MSPWare is up-to-date???  I'm a bit worried that MSPWare_2_40_00_37 includes DLLs and drivers, so by installing those, I might just screw up my installation.  Since the installation appears to have been the problem, I really want to have a firm answer to this before proceeding.  

  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points
    Great! Wish I had thought of the fresh install sooner.

    Again, I would only add things discovered in C:\ti2 just to avoid confusion with your two installs, so just the 3rd item in the image above. When you start CCS you can uncheck the search for new products box if you want it to not come up like this for you every time.

    For MSPware (2.40.00.37 is the same version I have installed), this includes:
    -driverlib (this is not device tool drivers and has nothing to do with programmers, but rather is simply a library of APIs that you can use in your application code).
    -code examples for MSP devices
    -documentation/links for MSP devices
    -other code libraries for MSP devices that you may want to use (USB library, SMBUS library, touch libraries, etc)
    -If you want, in your file system before you make any selection in the above pop up, you could examine the release notes and manifest found at C:\ti2\msp430\MSPWare_2_40_00_37 in manifest.html and release_notes.html.

    You can use Launchpad without MSPware installed at all in fact - but MSPware has included examples for Launchpad.

    The "driver" type files for MSP430 launchpads and other emulators are found actually not in MSPware - rather they are already installed with your base MSP430 CCS. You can find some at
    C:\ti2\ccsv6\ccs_base\emulation\drivers\msp430
    and
    C:\ti2\ccsv6\ccs_base\DebugServer\drivers (here you'll see MSP430.dll for example)

    MSPware shouldn't have anything to do with emulation on MSP430 devices - it isn't even tied to adding support for new MSP430 devices - that stuff is all within the base CCS.
  • 0 in reply to Katie Pier
    Intellectual 350 points
    OK, getting closer, but not .... quite .... there .... <groan>

    What's not working now is communication with my SensorTag Devpack. I have been successful in stepping through code with this, but now it appears to be broken. Device shows up as XDS110 Class Application/User UART under Devices.
  • 0 in reply to Thaddeus Niemeyer
    Intellectual 350 points

    More data:   I get the following message:

    Error connecting to the target:
(Error -600 @ 0x0)
A required dynamic library could not be located.
The library isn't on the search path.
(Emulation package 6.0.14.5)

    I'm worried that the tirtos_simplelink_2_13_00_06 directory did not get properly installed.  I copied this from my c:\ti installation to c:\ti2, and then let CCSv6 find it there.  I then let it install. 

    Can you recommend a procedure to do a proper install here?

  • 0 in reply to Thaddeus Niemeyer
    Intellectual 350 points

    Ok, was able to figure out the problem here:  For some reason, my new install had changed the debugger from "Texas Instruments XDS110 USB Debug Probe" to "Texas Instruments XDS100v3 USB Debug Probe [Default]"  Wonder Why?  Anyway, it's now stepping through the SensorTag code just fine.

    Side note: the preferred Devpack firmware used by CCSv6 is different than the one required by "SmartRF Flash Programmer 2".  Each of these programs insists on uploading its own version of the firmware to the DevPack.  My DevPack has a sticker saying it is Rev:1.3.0 if that helps.

    Thanks for all your help on this one Katie.

    One last question:  Can I now un-install my original CCSv6 without fear that it will affect my new installation?  

    Thanks

    Thaddeus.

  • 0 in reply to Thaddeus Niemeyer
    TI__Guru* 77821 points

    Hi Thad,

    I don't know much about the other packages like simplelink since I only really support and work with MSP devices - you might have to ask in one of the forums related to that part.

    For uninstalling original CCSv6 - I think if you use the uninstaller you should be ok uninstalling it, since it should be a completely independent CCS install. I've uninstalled previous versions before on my machine (as I mentioned I typically am maintaining a couple of independent versions like this for customer support) without having issues in the past. However, again I can only really speak to my experience with MSP - I don't know how other things might be affected.

    Regards,

    Katie

  • 0 in reply to Katie Pier
    TI__Guru**** 173310 points

    Katie Pier said:
    For uninstalling original CCSv6 - I think if you use the uninstaller you should be ok uninstalling it, since it should be a completely independent CCS install.

    Hi Thad,

    As Katie mentioned, now that you have a working version of CCS in c:\ti2, you can uninstall your previous installation in c:\ti. To uninstall, you can simply delete the entire directory. Any updates or additional add-ons that you may need in the future, you can get from CCS App Center or Help->Check for Updates for your current installation.

  • 0 in reply to AartiG
    Intellectual 350 points
    Yes I decided to play it safe and just delete the directory /wo using uninstaller. Probably would not have done any harm, but I don't want to risk it. Turns out, there were a couple of absolute path links in a few of my projects, but those were easily remedied. Retested everything and all is in order.

    Thanks again for all the help!
    Thaddeus.