Jump to content
Sign in to follow this  
n9rkd

Could not communicate with FET error = 35

Recommended Posts

So, this is my first foray into using the msp430.  I am working on an WSPR beacon project.  Essentially, I have the code and the project materials.  I got the TI-LaunchPad MSP-EXP430G2 that came with MSP430G223 and it uploads the sample "Blink" that are provided in the Energria software.  When I replace the '223 with the chip I need M430G2553.  Trying to upload the same sample I get the following error:

 

Could not communicate with FET (error = 35)

ihex: error on line 43

MSP430_Run: Could not read Enhanced Emulation Module register (error = 20)

 

I could not find much info for error 35.  Is the MSP-EXP430G2 not compatible for the '2553?  Is there an update / library I need to get?  

 

Thanks for the help.  Chris

Share this post


Link to post
Share on other sites

There are a couple of things to watch for when using the 2553 on the version 1.4 board. One is the jumper configuration for the 2553 as shown at the bottom of this page: 

 

http://energia.nu/pin-maps/guide_msp430g2launchpad/

 

The other is the possible need for a firmware update for the 1.4 board to support the newer chips (well newer in terms of what was available when the 1.4 board came out).  The wiki update page is here:

 

http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update

Share this post


Link to post
Share on other sites

I don't think it's firmware unless it's *really* ancient.  I've been using a 1.4 LP with the 2553, and my 1.4 LPs are from 4/2011 and have never had a firmware update.  It predates the G2553.  The only thing that I have to do on mine is swap the UART TX/RX pins if I wish to use the backchannel.

 

What OS are you using?  Can you communicate instead with the MSP430 Flasher?  http://processors.wiki.ti.com/index.php/MSP430_Flasher_-_Command_Line_Programmer?DCMP=MSP430&HQS=Other+OT+msp430flasher

Share this post


Link to post
Share on other sites

My 1.4 boards needed the update but I can't remember when I got them. Since the OP may have boards of an unknown vintage it seemed worth mentioning just in case.  The crossover UART jumper pins for the 2553 seems like a more likely culprit especially since the non 2553 chip works fine on the same board.

Share this post


Link to post
Share on other sites

Not sure.  Did the original LaunchPad MSP-EXP430G2 ever get support for the newer tilib / MSP Debug Stack V3?  I've not updated the emulator on mine, so it's still running the old original ez430-rf2500 firmware.

 

The Spy-bi-wire will work even with the UART pins disconnected, but you cannot use the backchannel for UART communications.  Should program just fine though.

Share this post


Link to post
Share on other sites

My vote goes for the firmware update being needed - there's some more links here with more details: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/364413/1281328.aspx#1281328

 

Some of the Rev 1.4 launchpads will need updates, others won't, depending on how old they are and which firmware they had: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/97931/364901.aspx

 

The fact that he was able to program another part (and I'm guessing the other part was the G2231 that came with the older launchpads even though he just said "G223" in this post) that is a G2xx1 device and so would be programmable without an update. This makes me highly suspect it is just needing the firmware update: http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update

 

@zborgerd:

 

I don't think it's firmware unless it's *really* ancient.  I've been using a 1.4 LP with the 2553, and my 1.4 LPs are from 4/2011 and have never had a firmware update.  It predates the G2553.  The only thing that I have to do on mine is swap the UART TX/RX pins if I wish to use the backchannel.

 

What OS are you using?  Can you communicate instead with the MSP430 Flasher?  http://processors.wiki.ti.com/index.php/MSP430_Flasher_-_Command_Line_Programmer?DCMP=MSP430&HQS=Other+OT+msp430flasher

The firmware update got implemented when G2xx2 were coming out I believe, but when we did the update we made sure the firmware would support both G2xx2 and G2xx3. So there are 1.4 launchpads that predate G2xx3 that would still have support for it. There are more details in one of the links I put above, from when the firmware update was first being released about which LPs are affected.

 

-Katie

Share this post


Link to post
Share on other sites

My vote goes for the firmware update being needed - there's some more links here with more details: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/364413/1281328.aspx#1281328

 

Some of the Rev 1.4 launchpads will need updates, others won't, depending on how old they are and which firmware they had: http://e2e.ti.com/support/microcontrollers/msp430/f/166/p/97931/364901.aspx

 

The fact that he was able to program another part (and I'm guessing the other part was the G2231 that came with the older launchpads even though he just said "G223" in this post) that is a G2xx1 device and so would be programmable without an update. This makes me highly suspect it is just needing the firmware update: http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Firmware_Update

 

 

That explains it.  My SN falls after the range that Adrian mentions in the post about the update, and was manufactured / shipped right after that.  Thanks for the info!

Share this post


Link to post
Share on other sites

Yeah that last link zborgerd was my post on the e2e site.  Yes, it was a firm ware update.   So, apparently crossing the vcc into the tx pins instead of crossing the rx tx is not a good thing to do on the Rev 1.4 board.  The good news is the new Rev. 1.5 board won't have that issue anymore.  Oh well, it was only a $9.99 mistake, that is actually quite cheap for me.   

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...