• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 2740 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Interface Communication Error

Avi W
Expert 1345 points
Other Parts Discussed in Thread: MSP-GANG

Hello,
I have only now arrive to a stage that I have time to fix the most annoying issue. 

I get "Interface Communication Error" once in a while.
NOT after update of the msp430-usb-debug-interface.

Another point to issue is that many times we work with 3 JTAGs at once & only 1 of them dies with this BUG.

Another test that we have done was during evaluation of the IAR this bug DOESN'T OCCURS AT ALL when using the with the IAR for MSP430. 

Moreover this happens with all our windows 7 PCs (more than 4, not all configures the same way).

Setup:

  1. PC OS -  windows 74 Ultimate
  2. CCS -  Version: 6.0.1.00040
  3. TI MSP -  MSP430F54308
  4. JTAG - msp430 usb debug interface

I've read several post about this issue like this and others (with less detail) 

The only working solutions we have at the moment:

  1. Replace the JTAG with different JTAG usually solves this. 
  2. Reset the PC. 

Both of these solution aren't OK, we would like to find the source for this issue so plz help us fix this BUG for good.

I would like to stress out that this doesn't happened after JTAG update and happens about  5-20+ times a month. 

  • 0
    TI__Guru**** 211947 points

    Hello Avi,

    I apologize for your frustration and would like to help debug your issue by any means possible. I have a few follow-up questions regarding your initial report:

    1. Is it always the same MSP-FET430UIF device that fails or is any device susceptible?
    2. Does failure only occur when multiple MSP-FET430UIF devices are connected?
    3. If you were to manually update the firmware on a faulty MSP-FET430UIF device, is the issue resolved for the moment?
    4. How long are the cables that run from the MSP-FET430UIF to the computer? Can these be shortened, and if so does this fix the issue?

    It seems to me like the computer is becoming confused between multiple device COM ports resulting in the lockout of a MSP-FET430UIF device, in which case the computer has to be restarted or a new COM port has to be used (through MSP-FET430UIF replacement or firmware update). I will pull in the Tools team to see if they can offer any more insight on this matter.

    Edit: the MSP-GANG is also available for production programming of multiple MSP devices via JTAG

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 1345 points

    Ryan hello,

    Thank you for the replay.

    1. Only the MSP-FET430UIF fails the "cc-debugger" doesn't fail when used (BUT we used it only via IAR) . 
    2. No, it happens more frequently but it is probably since the statistical nature of the issue.
    3. Since the statistical nature of the issue I can't answer with Yes or No to this Q'. Yet I tend towards NO.
    4. We use the standard cables that we received with the MSP-FET430UIF.

    Has you can see from my answers I don't see how the MSP-GANG will help.
    (unless TI will rewrite the CCS lower interface with the JTAG - again IAR doesn't has this issue like that).

**Attention** This is a public forum