MSP-EXP430F5529LP: no FET device found

I seem to have located another thread with the same problem after doing a more in depth search of these forums.

https://e2e.ti.com/support/microcontrollers/msp430/f/166/p/724509/2673717?tisearch=e2e-quicksearch&keymatch=reflash%20ez-fet#2673717

Is there any recommendation on action I should take?

I am located overseas so returning the boards, if this is necessary, will be costly, it would be easier to just purchase another set.

EDIT:

I have located yet another thread with similar issues...

Any recommendations while I consider how to proceed is appreciated.

If this is an enumeration issue I will attempt to attach it to some other PCs.

The two computers attempted were a Mac (MacBookPro 2015 15") OSX Mojave and a Windows 7 64-bit PC (both USB2 and USB attempted) with the same results.

It turns out that the last package I opened contained a working board, I used that board, following these directions listed below to recover the boards.

You only need to connect 3V3, GND, SBWTDIO, SBWTCK pins.
I used the command prompt MSPFlasher_1.3.20 flasher with the below command (on MacOSx Mojave.
./MSP430Flasher -b -w ./eZ-FET\ lite\ rev\ 1.10\ Release\ Package/Firmware/EZFET_LITE_Rev1_1_BSL_1_1.txt

I could not use UniFlash to do the initial flash, it would not setup correctly, the command line MSP430-FLASH was required.

Once the board was recovered I opened up UniFlash and attempted to read the chip, still connected.
UniFlash recognized the EZ-FET was corrupted and updated the firmware, required two updates, but fully recovered.

It appears there is a quality assurance issue with the flash programming of this part, 2 out of 3 of the boards I received did not function and the EZ-FET firmware needed to be recovered, thank goodness it is available.
Listing the resources used below.

EZ-FET firmware
software-dl.ti.com/.../index_FDS.html

Use the file Firmware/EZFET_LITE_Rev1_1_BSL_1_1.txt

MSP430-FLASHER, command line
www.ti.com/.../MSP430-FLASHER


UniFlash 5.0.0.2289
www.ti.com/.../UNIFLASH

I am leaving this not marking this thread solved, I would like to make sure someone from TI notices this and possibly recognizes the QA issue with the EZ-FET programming corruption. This may be marked solved once it is noticed.

Hi Allan,

Sorry to hear about your frustrating experience but glad to hear you were able to find the appropriate links to help get you up and running.

I want to add a thank you for adding the links to the tools you used to recover your boards to this posting.

Now, I am in touch with the engineer responsible for coordinating our Launch Pads and EVMs and have shared your experience.  I can assure you he does not like to hear this kind of story and will bring this to the attention of the vendor who build these for TI to prevent this happening going forward.

Ill post a resolution as soon as I hear back from him.

Hi Dennis,

Thank you very much for your quick attention to this!

I have used other LaunchPad boards CC1310, CC1350, and CC1312R1 in projects and have been very satisfied with them, never had an issue.

Since this was my first use of the MSP-EXP430F5529LP LaunchPad (or anything MSP430) I did not know what to expect, or if my development workstation was configured correctly.  I have heard very good things about the ultra-low power capabilities of the MSP430 line and am looking forward to seeing if I can integrate this into our battery operated projects.

I also want to mention that I am also very glad that the programming headers remain accessible for parts, such as the EZ-FET MCU, that normally does not require end-user service.  I am glad I was able to easily reprogram it without modification of the LaunchPad, just a few jumper connections.

The development project involves SIGFOX, which I am sad to learn that TI may have discontinued support for it.

I will be posting another thread concerning SIGFOX support to see if I can get some current information about the status of the SDK.