This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430F4152: Whether security fuse is blown

Genius 5840 points
Part Number: MSP430F4152
Other Parts Discussed in Thread: MSP-GANG, MSP-TS430PM64A, , UNIFLASH, MSP430F2619

Hello,

When my customer tries to access JTAG with a firmware update after mass production, the tool denies access.
The error when writing MSP-GANG and CCS is as follows.

MSP-GANG:

CCS:

1.Is the device secured?(security fuse is blown?)

2.If yes, is my understanding correct that the device cannot be unlocked forever? ??

3.Are there any other possible reasons why JTAG access is denied?

Regards,

U-SK

  • 1. Maybe. I don't understand why in MSP-GANG GUI there is red for connection, but green for erase (how it can do erase if there is no connection?). Also this CCS window doesn't help to clarify situation.

    Master JTAG / SBW device can connect to target device, and than check if fuse is blown (device secured) or not. Don't understand why is this so complicated, that someone in TI office  for years can't implement reach error report in software, that user can without any doubts, read what is wrong with setup.

    2. In F4xx family there is real fuse that is blown by applying 6.5V from master device, and there is no reverse like with F5xx that have software value inside flash related to fuse state. If fuse is really blown than SBW / JTAG is locked forever. However, BSL should work.

    3. Yes, but easiest way is to do mass erase by BSL if it is (connection) enabled on PCB. With mass erased target device and reliable connection, master JTAG / SBW device should work OK with target if fuse is not blown.

    EDIT: Don't know if (for your F4xx)  there are factory calibration values inside info memory, so please check device datasheet to be sure. Because there is possibility that connecting to BSL with wrong BSL password (vector) all memory including info memory with calibrated data will be erased.

  • Hello,

    Sorry for my rate reply.

    As you advised, I would like to make sure whether security fuse is blown by doing mass erase via BSL.

    So I am running MSP-BSL(rocket) and BSLDEMO in latest BSL-Scripter_3.4.0, but "Synchronization failed" occur.

    In hardware environment, I am connect MSP-BSL and MSP-TS430PM64A as follows.

    [MSP-BSL]        [MSP-TS430PM64A]

    1_TX           -----       52_P1.1

    2_TCK        -----       JP9_pin2

    3_RX          -----       53_P1.0

    4_RST        -----       JP5_pin2

    5_GND       -----       J5_pin2

    6_Vcc         -----       JP2_pin1

    In software environment, first of all, driver of MSP-BSL is install and my pc seems to recognize MSP-BSL properly.

    After that, BSLDEMO is executed as following.

    C:\ti\BSL-Scripter\DEPRECATED\BSLDEMO\BSLDEMO>BSLDEMO.exe -tRocket -cCOM10

    But following error was appeared.

    MSP430 Bootstrap Loader Communication Program (Version 2.03 - 2019)
    Mass Erase...
    ERROR: Synchronization failed!
    Device with boot loader connected?

    Just in case, I added -s0 and -d and ran it, but the result did not change.

    What are the possible causes?
    Could you tell me how to Mass erase MSP430F4152 with MSP-BSL?

    Regards,

    U-SK

  • Hi U-SK,

    It looks like the path or the scripter you are using has been "DEPRECATED". You might try running a newer version. You can also find specifics on how the BSL (and BSL commands) should work for this device here:

    https://www.ti.com/lit/ug/slau319ae/slau319ae.pdf

    Hope this helps.

    BR,
    Leo

  • Hi Leo,

    Thank you for your reply.

    I have already read slau319ae document.

    But I think there is no information about BSLDEMO and MSP-BSL.

    Where is BSLDEMO of newer version in the folder "BSL-Scripter"?

    I think execution file "BSLDEMO.exe" is only located in the folder "DEPRECATED".

    What's wrong with my environment and procedures?

     

    Regards,

    U-SK

  • Hi U-SK,

    It's not clear to me why this isn't working. I believe the same functionality should also be integrated into Uniflash. Can you try a mass erase with Uniflash?

    BR,
    Leo

  • Hi Leo,

    Thank you for your reply.

    I have tried to do mass erase by uniflash.

    But following message is appeared.

    [2021/6/4 16:31:09] [INFO] MSP430: MSP430F4152(Bootloader)
    [2021/6/4 16:31:09] [INFO] MSP430: ..... Invoking the bootloader .....
    [2021/6/4 16:31:09] [INFO] MSP430: Opening COM PORT is successful!
    [2021/6/4 16:31:09] [INFO] MSP430: Change baud rate to 9600 baud to start bootloader communication
    [2021/6/4 16:31:11] [ERROR] MSP430: Response byte for sync command from bootloader is not received!
    [2021/6/4 16:31:11] [ERROR] MSP430: [ERROR_MESSAGE]File format is not supported!

    I selected the file to write first and pressed the Load Image button with the password blank.

    I have tried to select both ti-txt and hex format but the format error seems to occur.  

    Is there possible cause?

    Regards,

    U-SK

  • Hi U-SK,

    This is indicating either a problem with the UART communication or the invocation command. Can you post a picture of the setup you are using here? Is this still using the MSP-BSL rocket?

    BR,
    Leo

  • Hi Leo, 

    Thank you for your reply.

    Yes, I'm using MSP-BSL Rocket.

    My understanding is following: 

    1_TX           -----       52_P1.1

    2_TCK        -----       57_TCK

    3_RX          -----       53_P1.0

    4_RST        -----       58_RST

    5_GND       -----       J5_pin2

    6_Vcc         -----       JP2_pin1

    [Device Manager]

    [Uniflash]

    Regards,

    U-SK

  • Hi U-SK,

    I've ordered some samples for testing. Have you tried communicating with more than one device? 

    BR,
    Leo

  • Hi Leo,

    Thank you for your advice.

    I have MSP430F2619, so I've tried it as same way, but same error is appeared.

    [2021/6/7 15:23:16] [INFO] MSP430: MSP430F2619(Bootloader)
    [2021/6/7 15:23:16] [INFO] MSP430: ..... Invoking the bootloader .....
    [2021/6/7 15:23:16] [INFO] MSP430: Opening COM PORT is successful!
    [2021/6/7 15:23:16] [INFO] MSP430: Change baud rate to 9600 baud to start bootloader communication
    [2021/6/7 15:23:18] [ERROR] MSP430: Response byte for sync command from bootloader is not received!
    [2021/6/7 15:23:18] [ERROR] MSP430: [ERROR_MESSAGE]File format is not supported!

    Regards,

    U-SK

  • Hi U-SK,

    If you look at the schematic in section B.23 of https://www.ti.com/lit/ug/slau278ah/slau278ah.pdf - you'll see that the BSL header can be used to connect to the BSL rocket with a few resistors(populated or unpopulated based on how the device is powered).  Can you try connecting the rocket through this header?  You'll need to solder some male header pins into the target board.

    BR,
    Leo

  • Hi Leo,

    Thank you for your reply.

    If I need to mount connectors and resistors, I also need to get the parts and it takes a lot of time.

    According to the schematic, both seem to have similar connections, but why should I connect the MSP-BSL from the connector?

    Regards,

    U-SK

  • Use BSLDEMO2.EXE Win CLI. This is a typical line for flashing blink.txt firmware file (just change COM port number and use your txt file). If connection is correct it should work. You can also use G2 LP (slaa535) instead of BSL Rocket.

    BSLDEMO2.exe -cCOM7 -m1 +epvrw blink.txt

  • Hi zrno soli,

    Thank you for your reply.

    Where is BSLDEMO2.exe you mentioned located?

    I have tried to "BSLDEMO.exe" included in latest BSL Scripter folder.

    C:\ti\BSL-Scripter\DEPRECATED\BSLDEMO\BSLDEMO>BSLDEMO.exe -cCOM10 -m1 +epvrw test.txt
    MSP430 Bootstrap Loader Communication Program (Version 2.03 - 2019)
    Number of mass erase cycles set to 1.
    Mass Erase...
    ERROR: Synchronization failed!
    Device with boot loader connected?

    But error is still remained.

    Connection is same as above thread.

    1_TX ----- 52_P1.1

    2_TCK ----- 57_TCK

    3_RX ----- 53_P1.0

    4_RST ----- 58_RST

    5_GND ----- J5_pin2

    6_Vcc ----- JP2_pin1

    Is there something wrong with the connection in my environment?

    Regards,

    U-SK

  • Hi Leo,

    Thank you for your reply.

    I downloaded BSLDEMO2.exe from the following and tried it with the same connection.

    http://www.flyingcampdesign.com/msp430-bsl-programmer.html

    But same error is displayed as a result.

    C:\ti\BSL-Scripter\DEPRECATED\BSLDEMO2\EXE>BSLDEMO2.exe -cCOM10 -m1 +epvrw test.txt
    MSP430 Bootstrap Loader Communication Program (Version 2.00)
    Number of mass erase cycles set to 1.
    Mass Erase...
    ERROR: Synchronization failed!
    Device with boot loader connected?

    Is there any possible reason?

    Regards,

    U-SK

  • Hi U-SK,

    I am waiting to receive some samples. Once I have these, I will test on my side to see if I can reproduce your issue.

    BR,
    Leo

  • Hi Leo,

    Thank you for your cooperation.

    When can you start your test?

    I have to tell my customer whether the device's security fuse is blown by Friday, June 18th, Japan time next week.

    Regards,

    U-SK

  • Hi U-SK,

    I should receive the samples by Monday.

    BR,
    Leo

  • Hi Leo,

    Thank you for your reply.

    I'm looking forward to your test result!

    Regards,

    U-SK

  • HI U-SK,

    Sorry for the delay on this. I'll test these soon.
    BR,

    Leo

  • Hi U-SK,

    I've tested a new device with the MSPGANG here and can confirm that I was able to erase and program it. When I blew the fuse on the device, I got the same fail connect through the MSP Gang so can verify that the behavior that you are seeing indicates that the fuse has been blown on the device. When I tried to mass erase with BSLDEMO2, this failed.  It's not clear to me why the BSLDEMO2 failed, but I can confirm that it doesn't work independent of whether the fuse is blow or not.

    BR,

    Leo

  • Hi Leo,

    Thank you for your reply and testing.

    I may be able to see it on MSP-GANG when I go to the office.

    It's very helpful for me if you tell me the detailed procedure.

    By the way, could you tell me how to mass erase via BSL using MSP-BSL Rocket?

    I have only MSP-BSL and MSP-TS430PM64A now.

    And I have both new and defective MSP430F4152 devices.

    Does it mean that BSL communication is not possible with BSLDEMO2 or MSP-BSL?

    Regards,

    U-SK

  • Hi U-SK,

    I don't have a lot of experience with these older tools - so it might just be that there's something which isn't clearly documented.  I'll continue to look into the MSP-BSL demo issue to see if I can find more information.

    BR,

    Leo

  • Hi Leo,

    Thank you for your reply.

    I'm also looking forward to your advice about MSP-BSL Rocket.

    And just in case, could you tell me the procedure in detail how to mass erase via BSL by using MSP-GANG?(GUI, command line, connection, etc)

    Regards,

    U-SK

  • Hi U-SK,

    From the MSPGANG user's guide, it looks like you need to connect GND, Vcc, BSL-Tx, BSL-Rx, RST, TEST or TDI from the JTAG connector to your BSL lines. You should then be able to select BSL and hit the Erase button.  Let me know if this doesn't work.

    BR,

    Leo

**Attention** This is a public forum