MSP430FR4133: what is the password file in BSL mode.

I see the point using BSL will other MSP430 devices, but don't understand for what is used (reason)  with FR4133 and TI FET Because for FR4133 JTAG fuse can be locked by JTAG, and for firmware update it can be unlocked (mass erased), updated and locked again, all of this by existing JTAG connection.

BSL password is vector area from the last firmware flashed into device.

Dear Zrno,

I dont understand your meaning.can you explain more clearly.

My customer cant use JTAG interface(assumed they are damaged).if they want to use BSL mode, how should we connect the target board?

in addition,if we want to use BSL mode, do we need used below pins?

But why costumer want to use BSL with this device?

This device can be used with SBW (only with TEST / RST connection, 2 less than BSL - pin saving), no need for full JTAG. If RST / TEST lines are damaged, there will not be possible to enter SBW, JTAG or BSL mode. This device can be completely handled by SBW, there is any advance in using BSL.

Repeat, for blowing / unblowing JTAG fuse for this device can be used SBW / JTAG, keeping downloaded firmware protected.

Hello,

For information regarding how to properly use BSL on our devices, please refer to the MSP BSL Landing page for step by step instructions of how to use the Bootloader on our MSP430 devices.

For the MSP-GANG being unable to connect to the target board, is this a custom board? Has the MSP-GANG ever been able to connect to the board or is it a new phenomena that just started happening?

-Matt

hi,Matt，

sorry for late reply.

yes, the target board is customer designed. this is a new Phenomena,before customer can write code by SW mode,but now SW mode can't  been used,so customer change to BSL mode, but it can't run normally.

now customer appear below error window,can you tell me what meaning of ERROR 23. as below.

how should i resolve the issue that programmer can't connect to target board by BSL mode?

 thanks.

Cickey  Xu

Using ERASE_USER_CODE (for example with MSP430 Flasher) by SBW / JATG interface (even device is locked / protected) should put back device in mass erased factory state. As I noted before, there is no need to mess with BSL.

Cickey,

Have you tried doing the mass erase of the user code that Zrno recommended to see if putting the device back in a mass erased factory state fixes the issue of being able to connect to it and initialize it (ERROR 23)? Is this only happening on one of your customer's boards or is it on every board?

-Matt

Dear Matt，

thank for your support and sorry for delay replying.

recently I visited customer and got the details about the issue.

the basic information as below:

customer  continually mass production by  MSP430FR4133  before March. and everything is ok; but since March,customer purchased 8k+ MSP430FR4133 ,this batch of product begin appear abnormity, which is all chips can't be write code secondly by JTAG interface, then customer try to by SW interface or BSL interface.but all method is unsuccessful.

But When customer buy some samples from Mouser, these samples all can write code many times. no matter which interface they  used.  and customer also try some chips purchased before March. the chips also can write code many times.

So customer thought these batch of chips maybe some quality issue.they want to do FA .

On the other hand, customer also want to know why appear ERROR 23,  and what meaning is the error code represent. which reason will cause appear EEROR 23.

Hi, Zrno soli,

i dont know how should use ERASE_USER_CODE, because  we cant connect to the target board by JTAG interface or SW or BSL.

Hello,

1. what is "ERASE_USER_CODE"? could you please provide us some document about operation?

2. we can not find information about "ERROR 23", could  you help to find some information about this error code?

3. if the device is secured as below checkbox  is check, can we have any method to re-program again?

thank you.

Hello,

1. what is "ERASE_USER_CODE"? could you please provide us some document about operation?

2. we can not find information about "ERROR 23", could  you help to find some information about this error code?

3. if the device is secured as below checkbox  is check, can we have any method to re-program again?

thank you.

Hello,

Thank you for your patience during this process.

According to the MSP Gang User's Guide Error 23 is a device initialization failure:

Once the security fuse is blown, the device can only be accessed through BSL. Mass erasing the device is able to be accomplished using Uniflash but if you are unable to connect to your devices then that will not allow you use the Uniflash tool to erase the device. 

From what I understand, you have successfully connected to devices from Mouser on your custom board using an MSP-Gang and then all you did was replace those devices with the devices that you ordered and confirmed that none of them are successfully connecting? Is my interpretation of your testing correct?

Best regards,

Matt

Dear Matt,

what your understand is not all correct. I should say all of the device that order since March cant be written code the second time.

Cickey,

Do you have an MSP-FET programmer that you can use to try and program one of your failing boards with a basic example code from the TI Resource Explorer? I'd like to see if you get any error when trying to program the board in CCS. Let's rule out issues with the MSP-GANG and the custom SW you are working with.

Best regards,

Matt

Hi,Matt,

My customer only have MSP Gang to debug,do we have any other method to test?

by the way ,customer photo the two kinds of normal and abnormal devices by X-Ray, find the different picture,please refer below .

By the way,consider this case,can we do FA?

Cickey Xu

Hello,

This thread has been resolved offline and the root cause was a hardware issue. Thank you everyone for your support.

Best regards,

Matt