MSP-EXP430G2: Debugger/Programmer seems to have stopped working

Bruno Silvano

Part Number: MSP-EXP430G2

Hi,

I was recently starting to use the MSP-EXP430G2 LaunchPad with the MSP430G2231 chip on Mac OS X.

I could successfully install the drivers and the Energia software. I did also successfully flashed new programs to the MSP430G2231, not only with the Energia but also by using the mspdebug on the command line.

But then I disconnected the board from my Mac for a few minutes and when I tried to use it again, it seems to have stopped working. When I connect it to the computer, it shows up as: Texas Instruments TUSB3410 Boot Device, with ID 0451:3410 (not the expected 0451:f432).

I even tried to setup everything on a Windows 10 machine. I've downloaded and installed the drivers and the Energia, but even Windows only shows up TUSB3410 Boot Device in the device manager.

It seems to me that the ez430 debugger bricked somehow. But I can tell the MSP430G2231 is still working, since every time I connect the board to the power, it runs the last flashed program.

Any ideas on what could have happened? Would you suggest any workaround to keep programming the MSP chip?

Thanks!

over 5 years ago

0 Gary Gao over 5 years ago

TI__Mastermind 32545 points

Hi Bruno

You can follow the user's guide for the ez430 more detail you can refer to the MSP Debuggers user's guide in the chapter 3.2

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

Thanks for your reply. Yes, I have already read this document. My board is definitely based on the eZ430. I have already tried reinstalling the drivers, even as administrator (on Windows). The enumeration is still failing to succeed, as my board is shown up as "TUSB3410 Boot Device" and not as the 3 devices that is said on the document. I don't know what I could try, aside from reinstalling the drivers (which I have already done).

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

Please be sure that you don't have any previous driver installed, the best option is install the latest released driver as administrator and than restart it.

By the way does this threads describe the same problem with yours? e2e.ti.com/.../608956

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

Yes, there were no drivers installed previously. And I've tried installing them exactly as you described (running as Administrator, restarting the computer).

The link you provided seems to be a different issue. Even though, after checking it out, I've tried installing the TUSB3410 driver as well, but without success.

As you can see in the image below, my MSP-EXP430G2 LaunchPad board appears only as TUSB3410 device and not as like in the image of your first answer, where it says it should be shown as USB Composite Device/MSP430 Application UART (COM205)/USB Input Device.

So, still no solution found.

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

As my known, there is some driver problem with the Mac. Can you use the Windows system in the future? And you can try the ways that we mentioned before. And try different USB port. If even not work you can give me some information of your PC and I will help you to seek the help of other teams.

BR
Gary

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

I've tried all the above on a Windows machine. Even though my primary development machine is a Mac, I would still be happy if I can get it working with Windows.

The machine I'm using is a Dell Inspiron with an Intel Core i5 3rd Gen, 2.5 GHz, 4GB of RA, running with Windows 10.

Thanks

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

I have asked the tools team they just recommend you to use the new version of the G2 Launchpad that with EZ-FET emulator on board or if you have other Launchpad that have EZ-FET that can be used to debug.

Best regards
Gary

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

This Launchpad is the only TI board that I own. That means then that I'm unable to continue using it if I don't buy a new one?
I'm afraid that by doing so, I could face the same problems again. I'm not willing to buy a new one just to try this out.

So, this doesn't solve my issue.

Best regards,
Bruno

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

Where are you live? If you are close to China I can send you a Launch pad with eZ-FET. If not, you can connect to the TI store and ask them to change a new one for you. And I will help you continue to ask the tools team for some help if possible.

Best regards
Gary

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

I live in Germany. That would be interesting.

How can I proceed with that?

Best regards,
Bruno

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

You can connect seek the help from this page www.ti.com/.../

Best regards
Gary

0 Gary Gao over 5 years ago in reply to Gary Gao

TI__Mastermind 32545 points

Hi Bruno

Due to the thread close date is coming, I will close the thread first, but you can post your questions in thread and I will help to solve this problem after close this thread.
Thanks

0 Bruno Silvano over 5 years ago in reply to Gary Gao

Prodigy 70 points

Hi Gary,

As suggested, I contacted TI about this, but they weren't able to send me a new board, as mine was ordered more then 2 years ago.

I appreciate your help on trying solving this issue.

Unfortunately, I guess there's nothing that can be done to work around this issue.
No luck in trying to learn how to use the MSP microcontrollers line. =(

Best regards,

Bruno Costa

0 Gary Gao over 5 years ago in reply to Bruno Silvano

TI__Mastermind 32545 points

Hi Bruno

Give me your email address please.

Gary

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP-EXP430G2: Debugger/Programmer seems to have stopped working