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.

MSP430G2553: Problem communicating with MSP on Windows 10.

Part Number: MSP430G2553


Hello everyone! I'm currently using MSP430G2553 on a project of mine, but for some reason, I can't communicate with my microcontroller using my PC. I'm using IAR IDE, and when I'm going to debug using FET Debugger, it freezes at "busy: Starting debug session" and after half a minute ( it is much faster when using a non-existent COM port, so I assume it is actually identifying the MSP but for some reason can't connect to it ), an error: "Fatal error: Failed to re-initialize. Session aborted!". And a further error:

"Could not find MSP-FET430UIF on specified COM port : (Initialize) , port=HID0015:COM2, version=0xffffffff"

At first I thought it was a IAR related problem. The thing is, I installed it on my notebook, same version, and I was able to sucessfully use FET debugger using IAR. Which means, not IAR problem and not uC problem. Then, I developed a VB.Net software to send and receive data from the MSP using UART. The software worked flawlessly on my notebook. When I ran it on my PC, however, it simply froze when I sent a byte through UART. It froze until I disconnected my MSP's USB from the PC, then it instantly popped up an error message. I tried to use multiple drivers, I assume it's correctly installed ( on device manager, everything seems fine ). Tried reinstalling, messing with my motherboard settings of COM ports, no sucess. I can't even find similar cases on google.

Anyway, if anyone has any idea of what it could be the issue, I would be glad! My notebook is shared with other people in the house, and I rather program on my much faster desktop. Thanks for reading :)

  • Hi Bananabread,

    Someone in our other office has access to a Windows 10 machine and was able to reproduce a COM port issue there, but they reported this:
    "One thing I found is that when you connect the G2 LP to the PC and connect via terminal on the virtual com port within ~3s the debugger does not answer. If I wait more than 3s after the LP has been connected, I do not see any problems.
    Can you please double check if this is the same behavior?
    "
    Do you see the same thing? If you plug in the Launchpad, wait some amount of time, and only then try to connect to the COM port via UART do you still see the issue?

    Regards,
    Katie
  • Hello Katie!

    Thanks for answering, but unfortunately it didn't work. I waited but no sucess communicating with the MSP. I don't think the problem is related to Windows 10 though, I asked my friend to test it on his win10 notebook and everything worked fine. One really weird thing I found last night: If I try to debug while my Visual Basic software froze and is trying to communicate, it works! After a while it stops working, then I have to unplug and plug the MSP again, run the VB software to freeze it, and then I'm able to debug. Really, really weird.

  • Hi Bananabread,

    I asked someone on our tools team and they had the following questions:
    Do you know if the port you are using is USB3 or USB2?
    If it is USB3, could you try disabling USB3 (in BIOS) and try again to see if suddenly it starts working?
    Do you know what motherboard you are using?

    Regards,
    Katie
  • Hi Bananabread,

    Is there any update - were you able to resolve the issue? Or are you able to provide some of the above information for debugging purposes?

    Regards,
    Katie
  • Hi! Sorry for taking long to respond. Recently I found out that the problem is not the MSP430. It is something related to my motherboard/USB drivers regarding COM ports. Every COM port ( even disconnected ones ) when I try to write something, it simply freezes my application ( C# app ) forever. Unfortunately I haven't found anyone with a similar problem, so I guess there's not much anything else to do since I have no idea where to start.

    Thanks for helping.

    Best regards!

  • Hi Bananabread,

    Thanks for the update and sorry to hear you're running into a general issue with your PC like that. Hope you are able to figure it out.

    -Katie

**Attention** This is a public forum