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: Running MSP430G2553 OOB Demo... using CCS ver 8.3.0... Cannot find C:\Users\XXX\AppData\Local\Texas

Part Number: MSP-EXP430G2ET
Other Parts Discussed in Thread: MSP430G2553

Tool/software: Code Composer Studio

Hello Everyone,

Basic Questions on using MSP430G2ET and its demo.  

1) Error:  "Cannot find C:\Users\XXX\AppData\Local\Texas "
2) Trouble loading/running  the OOB GUI demo
3) Inconsistent behavior with other serial termnials (Realterm)
4) ESD issues?
5) Swapping chips in/out of Launchpad, How long should power be off?  

I am a beginner at using TI microcontrollers.  The 430 series looks ideal from a
low current standpoint. I had some success using CCS at work using an older
version of CCS ver 8.3.0. 

I installed that same version at home get the error...
"Cannot find C:\Users\XXX\AppData\Local\Texas" 

From reading the forum, it would appear that although CCS ver 8 works at work,
updataing to ver 9 at home may solve the problem with (1).  I will try that. 

I have the MSP430G2ET launch pad, actually two of them.
One seems not to be recognized as a serial port. I am wondering
if these are especially sensitive to ESD? I would expect that could
be possible with a 3V6 volt limit and everything being high impedance!  

My three MSP430G2553 chips all seem to run blink LED, or the temp 
monitoring on the launchpad once they are loaded, but the connection 
to the serial terminal or OOB GUI via the USB port appears to be inconsistent.
(This is at work, where I don't have error (1).  )
Often I can't see port numbers that look appropriate. 

I have not been able to reproduce my serial terminal OOB GUI
symptoms consistently.  Which means troubleshooting is... impossible? 
Sometimes Realtem reads out, but OOB GUI does not... same board and chip.

I plan on being consistent with ESD protection, ungrading to
CCS 9.1.0, and use the Resource Explorer to load the
OOB GUI since that worked at work. I have tried installing the 
OOB GUI in a couple places and will try to uninstall all of them 
before reinstalling. Cloud vrs. local?  I am not sure which version I 
was working with, maybe both? 

I may order another launch pad board to see how it behaves.
I am using 64 bit Windows 10 at home.

I saw the advice about closing all screens and opening just *one*,
that may help resolve the serial terminal/OOB GUI issue?

Any *short* advice for newbies to this family of chips and their
supporting software is appreciated.

Thank you all for your time consideration.  



 

 

  • Hey Sandy!

    Welcome to the E2E Forums and the Launchpad ecosystem.  Sounds like you have a lot going on, so I'll give you a couple of quick pointers.  

    First, Install the latest CCS version and make sure you have selected support for the MSP430 MCUs.  This will install all the example software, headers, ect. and most importantly the serial drivers for the COM interfaces.  As you mentioned, Resource Explorer should be your main hub for example code and OOB demos.  You can access it at dev.ti.com or via CCS.  

    ESD is always a potential problem.  I don't think the boards are particularly sensitive as I've never personally actually had an issue but still best to use caution.  

    When power is removed from the launchpad, you should be able to switch the MSP430 right away.  

    Good luck as you are getting started.  Feel free to come back here, or start specific threads on any issues that arise.  

    Thanks,

    JD

  • Thank you JD!

    Re: First, Install the latest CCS version and make sure you have selected support for the MSP430 MCUs. 

    I am not sure that I did the item mentioned in boldface.  I will try  reinstalling CCS tonight and
    see if that the boldface makes more sense.  I already had the the most recent version which is 9.1.0 

    I checked both my Launch boards and I can "build", debug and run the demo on both.  I can not 
    get the TI GUI demo to run.  

    I can get Realterm to function as a serial monitor if I select the correct port by hand  AND I press the 
    switch, -  to push it into temperature mode (and out of flash LED mode) and if the baud rate is 9600.  

    I can not get the TI Demo to run.  When I do I get the following error, even though that screen (node)
    is not open.  I have seen it open, in prior iterations, but it is not open now:



**Attention** This is a public forum