"security fuse has been blown" error

This question is not answered

on Apr 11 2012 07:04 AM

Hello everybody,

We are using MSP430F5438 microcontroller with CCS V5.1 compiler. Previously, debugging ( using JTAG = MSP-FET430UIF ) was working fine. Now, when I was trying to communicate with microcontroller through JTAG, I got the error "Security fuse has been blown". After that microcontroller seems to be locked and I was unable to communicate through JTAG. How can I unlock the Microcontroller and resume the debugging with JTAG?

Thanks in Advance.

All Replies

Posted by old_cow_yellow

on Apr 11 2012 09:41 AM

Guru25715 points

Most likely, the "security fuse" (which is actually the contains of certain locations in the protected BSL-Flash) is not "blown". The Tool Chains have lots of problems and the error message may be totally wrong.

In the rare case when the "security fuse" is accidentally "blown" (and the error message was actually correct), the rest of BSL is probably accidentally altered too. Thus BSL will not work either and that chip is locked for good.

Posted by Jens-Michael Gross

on Apr 11 2012 11:02 AM

Guru139970 points

old_cow_yellow
In the rare case when the "security fuse" is accidentally "blown" (and the error message was actually correct), the rest of BSL is probably accidentally altered too. Thus BSL will not work either and that chip is locked for good.

Due to silicon bug, teh BSL area of the 5438 (non-A) as well as the JTAG fuse, cannot be user-programmed and therefore cannot be blown at all.
So the problem mos tliekly is a code that resets teh MSP before the JTAG has time to attach.

Using 4-wire JTAG instead of SBW protocol, a parallel port FET instead of an USB one, or a dedicated flashing software such as Elprotronic's free "lite FET-Pro430" software may make the MSp accessible. Or attach to the BSL and mass-erase the MSP. And don't flash the same software again - first figure out what's happening and fix it. :)

_____________________________________
Before posting bug reports or ask for help, do at least quick scan over this article. It applies to any kind of problem reporting. On any forum. And/or look here.
If you cannot discuss your problem in the public, feel free to start a private conversation: click on my name and then 'start conversation'. But please do so only if you really cannot do it in a public thread, as I usually read all threads. And I prefer to answer where others can profit from it (or contribute to it) too.

Posted by Vijayalakshmi Chavan

on Apr 12 2012 00:40 AM

Prodigy20 points

Thanks.

My problem is solved by mass erase using BSL .