MSP430FR2522: Error: "The Debug Interface to the device has been secured"

something to add, we are using the MSP430FR2422 and MSP430FR2522 mixed, since the availability is a little tight. The additional features MSP430FR2522 offers compared to the MSP430FR2422 are not used.

Hi Daan,

Thank you for your post.

To clarify, you have never been able to flash these devices?

If the devices are truly locked somehow, you can still recover them using a BSL Mass erase. The MSP-FET tool you are using does support BSL Scripter, which you could use to attempt this. 

Best Regards,
Brandon Fisher

Daan Pendavingh said:

Is there a way to unlock the MCUs?

FR2xx can be mass erased (back to factory state) by mailbox system using SBW or JTAG interface (even it is locked / secured). This can be done by MSP430Flasher using "-e ERASE_USER_CODE". So for unlocking you don't need anything special, just use existing SBW / JTAG connection with MSP430Flasher on PC side. This should fix a problem if device is really locked.

Normally I am able to flash these devices without problems but since a month or 2 we have the MSP430FR2522s in mass production and we see significant yield loss due to these locked devices (roughly 5%). We never had this problem with the original MSP430FR2422.

I will have a look at the BSL scripter documentation. Thanks

zrno soli as far as I understand the ERASE_USER_CODE option is only available on FR4x devices:

I just tried it and indeed this works as expected, even on FR2xx devices! Sorry for the duplicate topic, is searched and found a lot of topics for the FR4xx devices but since the documentation stated it was only applicable for FR4xx

Now of course we need to know how it is possible that they come locked out of the reel. But I will take that discussion offline.. Thanks!