MSP430F5529 security fuse blown message from a brand new chip - Page 1
Forum section: electronics / general

author: RoGeorge
author_rank: Super Contributor
timestamp: September 19, 2025, 05:37:51 pm
content: Tried to program for the first time a MSP430F5529https://www.ti.com/product/MSP430F5529using SpyByWire (RST+TEST+GND+3.6Vcc pins from a LaunchPad devboard), so not a standalone program debugger, and it doesn't work.The message is 'cannot communicate with device, security fuse blown'. This chip I am testing is a MSP430F5529 sample that was never powered before, a leftover sample from a 2014 project, so I doubt the chip came locked from the factory.As far as I've read, the LaunchPad devboard shouldn't even have the capability to blow the JTAG security fuse, so I don't know why the 'fuse blown' error message. All I've tried so far was to program the trivial blink LED example, and it didn't program (the LED pin seems in high Z on the oscilloscope).The setup was really sloppy from my side, 4 wires of about 2 inch, and not a proper programmer, though the Launchpad devboard should have an eZ430-FET UIF programmer/debugger on it (if I understood the docs, which docs so far are pretty confusing, mixing many interfaces and tons of acronyms spread over tens of pdf's, which means thousands and thousands of doc pages).I don't know if I properly connected the MCU, or if the fuse were blown from factory, or how to recover from this, don't even know if the MSP430F5529 (80pins) is possible to program using a LaunchPad (or a msp430-Chronos, these are the only TI devboards I have with an onboard eZ430 UIF programmer/debugger, MSP430GEXP2 LaunchPad and MSP43-Chronos).Any ideas what to try next?

author: gabiz_ro
author_rank: Regular Contributor
timestamp: September 20, 2025, 07:02:39 am
content: Have no ideea.But on MSP-EXP430F5529LP board MSP430F5529 can be programmed via USB BSL. That BSL is from factory on every chip I think.But to use it it may be required some basic schematic, resistors on usb reset lines , button to enter bsl, crystal and power connected.On MSP430GEXP2 seems to be an ez-fet debug probe, it may be work with some MSP Flasher

author: gabiz_ro
author_rank: Regular Contributor
timestamp: September 27, 2025, 09:05:02 am
content: It is a long story, sorry for that.My problem with MSP430F5528 - 9MSP-EXP430F5529LP board with MSP430F5528 as EZ-FET and MSP430F5529 as main mcu converted to EV2400 works fine until few days when somehow I managed to kill it with a single cell battery that even was discharged.Anyway, one data pin shorted to ground.MCU's are almost the same, let's use MSP430F5528 as EV2400, but in BSL mode, have other hwid instead of USB\VID_2047&PID_0200 default one this have USB\VID_2047&PID_0203, maybe to differentiate them.Fixed this by hex-patching BSL_USB_GUI from MSP430 USB Firmware Upgrade ExampleTrying flashing firmware only no result, updating BSL wasn't working, it is protected,trying to bypass that I corrupted BSL area and now is unknown device in device manager.Next step let's make MSP430F5529 as EZ-FET, enter BSL, write eZ-FET lite firmware, nothing. Then write BSL and firmware from eZ-FET lite, got it working, apparent all OK.But can't enter BSL anymore.Checked hardware, all seems OK, that's it at least I have a working eZ-FET lite.Make required connection try to connect to bricked MSP430F5528 but MSPFlasher throw error Could not set device VccCheck schematics, see that some resistors are required to divide and apply voltage to some pins, ok added that to board, still same error Could not set device VccThey say you can use EZ-FET to program other boards, disconnecting jumpers and make required connection but that may be externally powered why don't have option to ignore Vcc checks?Try to patch those checks in MSPFlasher.exe and MSP430.dll seems to be working but could not detect anythingAt this moment I'm stuck.Yesterday EV2400 arrived.Connected to Frankenstein EZ-FET but same resultMaybe hex patch gone wrong and break something else, let's try more version may I can find older one that doesn't complain about voltage.Starting from newest to older and from older to newer- 1_02_00_00 no detect but to my surprise it could restart device- skipped few newer jumped to 1_03_15_00 still Could not set device Vcc- 1_02_01_00 no detect but it could restart device- skipped few newer jumped to 1_03_00_00 still Could not set device Vcc- 1_02_02_00 no detect but it could restart deviceAnd finally 1_02_03_00, detect it fineConnected to onboard MSP430F5528, detect, read, erase, write all ok.Although sometimes report security fuse blown.Why?Who knows?That's new software era, oldies but goodies

author: RoGeorge
author_rank: Super Contributor
timestamp: September 27, 2025, 08:48:26 pm
content: About the intermittent blown fuse message you see, vaguely remember reading one reply (from some other forum, don't recall where) about how the programmer SW does not distinguish between "blown fuse" and communication error (so a misleading error message). I don't remember for which version of the eZ-FET firmware (or if that was true for any version). Should be possible to check if the programmer throws a wrong error message (by looking in the programmer sources), but I'm not familiar with TI software, and didn't even try to find the sources, let alone to check for the error messages.Quote from: gabiz_ro on September 27, 2025, 09:05:02 amIs that remark about the programmer, or about the target 5529 you want to program? What is the minimum number of pins that has to be connected to a MSP430F5529 target MCU, in order to be able to program it (with the 2 wires RST and TEST interface)?Asking because I don't have any MSP430F5529 devboard, only the MSP430F5529 chip alone, and I am not sure what MUST be wired in order to program the MCU.I have connected only the DVCC1 (+3.6V pin 18), DVSS1 (GND), and a capacitor from VCORE to GND of the MCU to the eZ-FET implemented on the LaunchPad devbord, like this:Is this enough to program a MSP430F5529 using the "2 wires JTAG"?(don't know if that was the proper name for the program/debug interface I was using, talking about the 2 wires used to program/debug the MSP430G family, on my eZ-FET from the LaunchPad devboard, those "2 wires JTAG" are marked as RST and TEST)

author: gabiz_ro
author_rank: Regular Contributor
timestamp: September 28, 2025, 12:32:06 am
content: No idea if that's enough.I can test monday only with supply pins and removed crystal if works.I think Spy-Bi-Wire being more complex JTAG protocol may require that chip have proper power and clock signal.You may try to connect all power pins, crystal, usb data lines and power, resistors and button to enter BSL and see if device appear as HID device with USB\VID_2047&PID_0200 in device manager.

author: josip
author_rank: Regular Contributor
timestamp: September 28, 2025, 09:40:02 am
content: This topic is hard to read, but just to clarify some basic things...5528 and 5529 are identical devices except package/pinout.To test chip with simple blink program, it (5528/5529) can be flashed (with blink) by factory preloaded HID BSL. In this case basic parts related to USB hardware (XT2, USB lines and PUR button) must be present on board. Device can be flashed also by SBW (RESET/TEST/GND) that does not need any special parts on target device board. Device in any case must be powered by internal or external 3.3V regulator, and there must be capacitor on VCORE pin. XT2 is required for USB, and if device is not using USB (HID BSL included), can work without it. 5xx family is with internal pull up on RESET pin, and external is not needed (like with 2xx). FET master and target device must be on the same VCC.TI FETs software is not a masterpiece, and blown fuse can be reported in many cases (due some other not covers errors) even fuse is just fine. While to blow hardware fuse on 2xx flash devices 6.5 VPP is needed, in F5xx soft fuse can be blown with any VCC (1.8-3.6) because it is just value stored at memory location at the end of the BSL flash memory segment. Flashed bad code also can be reason that device can not respond any more to master SBW entry sequence and stay locked / bricked forever, even factory HID BSL (and fuse) are untouched.I have MSP-EXP430F5529LP. 5528 that is used as on board ezFET master don't have factory HID BSL. It is overwritten with ezFET code. But device can be programmed over SBW. It can be erased by SBW and factory HID BSL can be flashed, to put device back to factory state. Don't see any reason for this, but it can be done.If your target 5529 is working fine, with one pin broken, you can use any other pin that is working. There are plenty of pins on 5529 chip.

author: RoGeorge
author_rank: Super Contributor
timestamp: September 28, 2025, 03:03:39 pm
content: Quote from: josip on September 28, 2025, 09:40:02 amThat's my fault, for not knowing which is what, sorry.I want to know if a naked MSP430F5529 chip can be debugged with any of the MSP430 devboards I already have. The TI devboards I have are for various other chips. Some of them are for completely other MCU families, e.g. TMS or CC, and they have a FTDI based JTAG. Other devboards I have are for the same MSP430 family as this F5529 I want to try, yet none of the boards I have was made specifically for MSP430F5529.I don't want to buy yet another MSP430 devboard/debugger. Can I debug a 5529 with any of the TI devboars I already have?This is the MCU I want to program, an MSP430F5529:So far I've tried only the SBW mode. I didn't try programming the chip by its own BSL bootloader, because I need the debugger in the first place.These are the 2 different programmers I've tried so far, using SBW:Both of them seem to have the same kind of programmer (eZ430), and both are reporting the same error, blown fuse, either from CCS or from the command line. They do not complain about the 5529 target as unsupported.Now, I don't know why it didn't work, and what to fix:- did I wire the F5529 wrong?- is it even possible to debug an F5529 using an eZ430 and SBW, or is the F5529 unsupported by eZ430?- something else?Aside from those 2 devboards, I have a few more TI devboards I didn't try yet.One of them (for MSP430FR2433) has an embedded "eZ-FET Debug Probe Rev1.4" on its PCB (so, not an eZ430 debugger):Is this eZ-FET (from the last picture) the same programmer/debugger you have on the TI devboard for F5529? The board in the picture was made for FR2433, will it debug an F5529?

author: RoGeorge
author_rank: Super Contributor
timestamp: September 29, 2025, 07:20:05 am
content: Tried to program the same F5529 again yesterday, this time from CCSv7.4.0, and using SBW of the 'eZ-FET Debug Probe Rev1.4' present on the MSP-EXP430FR2433 devboard (last picture from the previous post).It didn't work, same message but with different words than it was in CCSv5. CCSv7 error is:QuoteNext time I'll try to program the F5529 by its ownUSB BSL (instead of SBW), but before trying that I'll have to solder the chip on something. The pins of that F5529 hanged with wire wrap are very thin. By comparison with the chip's pins, the wrapping wire appears as rigid as a crowbar, threatening to break the F5529's terminals.Couldn't find any breakout board for the 5529 footprint, so I guess I'll have to improvise.

author: josip
author_rank: Regular Contributor
timestamp: September 29, 2025, 10:46:30 am
content: This 2 TI SBW programmers (both on one picture) are not based on 5528 eZFET master. They are related to F/G2xx devices, and F5xx family by TI software is not supported by this SBW programmers. However, they can work with F5xx family using msp-debug.ezFET from EXP430FR2433 based on 5528 can work as FET master with any MSP430 SBW device. On board jumpers between FET master / and FR target must be remove, and SBW lines (SBWTDIO, SBWTCK, 3.3V and GND) from FET master male headers should be connected to off board target device. There is no need for USB on 5529 target and 5V are not used, internal regulator also.If 5529 fuse is blown for real, and factory HID BSL is untouched, than device can be unlocked by BSL, but in this case around 5529 must be populated USB related parts.Anyway don't leave chip in air becase it will lose pins fast. Fix it on protoboard, similar as I did long time ago with 5510. You don't need to connect all pins like I did, only few of them. USB (including BSL) was working just fine on my protoboard.

author: gabiz_ro
author_rank: Regular Contributor
timestamp: September 29, 2025, 01:05:39 pm
content: Tested now, both crystals, removed.On board part of 5529 remained only resistors on USB datalines and bsl-pur and capacitors.SBW-JTAG works.Code:C:\ti\MSP430Flasher_1.2.3>MSP430Flasher.exe -n Unknown -r [Firmware Output.txt,MAIN]* -----/|-------------------------------------------------------------------- ** / |__ ** /_ / MSP430 Flasher v1.2.3 ** | / ** -----|/-------------------------------------------------------------------- ** Evaluating triggers...done* Checking for available FET debuggers:* Found USB FET @ COM285.* Initializing interface on TIUSB port...done* Checking firmware compatibility:* FET firmware is up to date.* Reading FW version...done* Reading HW version...done* Powering up...done* Accessing device...done* Reading device information...done* Dumping memory from MAIN into Firmware Output.txt...done*/* ---------------------------------------------------------------------------* UseCase : MSP430Flasher.exe* Arguments : -n UNKNOWN -r [Firmware Output.txt,MAIN]* Warning: Default options used due to incomplete argument list.* ----------------------------------------------------------------------------* Driver : loaded* Dll Version : 30301004* FwVersion : 0* Interface : TIUSB* HwVersion : E 2.0* Mode : AUTO* Device : MSP430F5529* EEM : Level 7, ClockCntrl 2* Read File : Firmware Output.txt (memory segment = MAIN)* VCC ON : FALSE* ----------------------------------------------------------------------------* Powering down...done* Disconnecting from device...done** ----------------------------------------------------------------------------* Driver : closed (No error)* ----------------------------------------------------------------------------*/Make sure you connect right.SBWTCK to to pin 70 Test/SBWTCKSBWTDIO to pin 76 RST/SBWTDIO3V3 to pin 18 DVCC1, 50 DVCC2GND to GND

author: RoGeorge
author_rank: Super Contributor
timestamp: September 30, 2025, 02:20:25 pm
content: Thank you both, that was very helpful info.I guess the errors I am seeing are caused by signal integrity, those 5 soldered wires were really lousy. The improvised wiring was only to check if a Launchpad for MSP430G can program an MSP430F. At that point I didn't even know there are so many programmer flavors, or about the BSL. Now I know for sure I have at least one programmer able to program an F5529 (the programmer included in the Launchpad for FRAM chips, MSP430FR2433). So I'll have to properly solder the chip on a PCB.The pins pitch in this MSP is much smaller than I would like it to be for a hand-made wiring. It will take many hours of looking through the microscope.The finest I've hand-wired so far on a perf-board was a FTDI, much easier and with way fewer pins: