CAPTIVATE-PGMR: CCS reports "No USB FET was found" and red led is on

Is this with just the CAPT-PGMR connected to USB and no target MCU connected to the CAPT-PGMR?

Do you by chance have an MSP-FET or other MSP430 Launchpad handy?

I started with the target mcu connected, then to rule out whether the problem was I removed pieces of the kid until I got to the pgmr alone. In all cases, with and without the target the symptos are the same, red led, no detection by any OS.

Unfortunately I don't have other programmers at hand, I do have some old ez430-rf2500 programmers but I guess can't be used in this case

Ok, is this a new one you just purchased?  Also, let me dig up some information on how to re-flash the ez-FET programmer chip on that board.

Hi EE LL,

Here is a way to cause the ez-FET on the CAPT-PGMR to go through a 'cold-boot' and cause a new image to be loaded.

The instructions are the same for the MSP-FET.  The MSP-FET user's guide, page 23 shows the steps, however, you will be applying this to the CAPT-PGMR. 

Basically, if you temporarily short 3.3V_LDO to the ez-FET PUR pin using a 100 ohm resistor (shown below), then connect the USB cable, wait a couple of seconds, then remove the resistor.  Next start CCS and attempt to program the target.  You should see a prompt asking if you want to recover the ez-FET.

Thanks for the assistance. We tried this procedure but didn't work.

When we plug in the usb cable the red & green LEDs remain off, while the LED4_Enum led blinks once and LED5_Pwr is on, this seems to indicate that the device is entering cold boot since we're not seeing the red led on. However in the PC we still see in device manager the "unknown USB device (Device Descriptor Request Failed)" message. When we open CCS nothing is detected and when we attempt to flash code we get the same error "No USB FET was found".

So you shorted the two points on the PCB with a 100 ohm resistor, connected the USB cable to the PC, then removed the 100 ohm resistor?

Yes, our procedure

1. Short two points via 100R resistor as indicated in the picture received

2. Connect to USB : we can see the short is taking effect because we don't see the red led anymore. The green "enum" led blinks once. The PC detects the device but shows it as "unknown USB device (Device Descriptor Request Failed)" .

3. wait 2-3 seconds

4. Remove resistor

5. Open CCS -> opens as usual, no detection of the 'cold boot' is done

6. attempt to flash a device: "No USB FET was found"

Thanks

That's very strange.  I just performed the same steps here in the lab and it worked for me.

During the process I get these messages below.  Do you?

When I clicked 'Recover' it failed, but I tried a second time, then saw this.

Then it proceeded to re-install the firmware and I was able to program a target.

If you are not seeing these then that tells me it is possibly a failure with the USB HUB device on the board.

Where did you purchase this programmer?

If through a distributer, such as DigiKey, you need to contact them for a replacement.

If you purchased directly from TI, you need to first contact our Customer Support Team and open a support request -> https://ticsc.service-now.com/csm

They will ask if you reached out for assistance from E2E and if someone from TI (that would be me) helped diagnose the issue.  Provide them with the link to this E2E posting and they will contact me to confirm.

TI CUSTOMER SUPPORT - This customer's CAPT-PGMR has a defective chip and needs to be replaced - a0272918

I don't get that far since my issue seems like a USB issue. Device manager shows

so I can't get to the point you are because I can't even pass USB enumeration.

I did purchase it from ti.com and I did submitted a support request CS0754529 even before my first post here but got no response so far other than the automatic submission confirmation.

The ez-FET programmer on this board is an MSP430F5528 and is a down-stream device from the on-board USB bub device, TUSB2046, so if the HUB chip is bad, the F5528 won't enumerate.  Let me contact our customer support team and see if we can't get this resolved.

Hi EE LL,

I spoke with the customer service folks and they should be taking care of your case.

For that reason I'm going to mark this post as resolved.
If this isn’t the case, please click the "This did NOT resolve my issue" button and reply to this thread with more information.
If this thread locks, please click the "Ask a related question" button and in the new thread describe the current status of your issue and any additional details you may have to assist us in helping to solve your issues.

Thanks, I haven't receive any response from customer service, other than a couple questions which are already answered here so I just referred them to this forum.

Hi EE LL,

I apologize for the delay.  Let me try again.  I suspect with the supply-chain issues, it may take a little longer to get these requests processed.

I'll keep you updated.

Hi EE LL,

Did you get a response from customer service regarding your return?

Unfortunately nobody has contacted me since 11/16th. Of course we already purchased a new set, but it is very disappointing the lack of response for something so simple yet so significative for a business relation. In the end this only hurts TI since this is a massive production project and my colleague already wrote a bad note about TI's CS due to this experience. I can't argue unfortunately.

Hi EE LL,

Yes, I'm sorry this has taken so long.  This is actually very unusual.  I've worked with the folks over in customer service and the response is normally immediate, once we identify and confirm the failure.  I'll ping them.