• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 80 subscribers
  • Views 616 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR6989: Debug Interface Secured - Unable to flash in bootloader.

Wui Fan Lim
Prodigy 30 points
Part Number: MSP430FR6989
Other Parts Discussed in Thread: MSP-FET,

I've been using MSP430FR6989 in my project for a long time and I always have no issue flashing the bootloader and firmware image, via Spi-By-Wire. However, recently I encountered a problem when trying to flash bootloader, where the error "Debug Interface Secured" occurred. The MSP430 chips that I used are brand new and I encountered this "debug interface secured issue" in a few of them. Please advise what could be the cause of this issue and how to resolve it.

For your infomation, I've tried to use the ERASE_TOTAL command but it doesn't work. Apparently, the debug port was locked and I was not allowed to input any command. Also, I've seen other forum post that suggested to do a MASS ERASE. However, my MSP430 did not even have a bootloader loaded, so I was unable to execute the MASS ERASE.

Please help and thanks in advance!

  • 0
    Guru 34693 points

    ERASE_TOTAL is able to put FR device back to factory state, but not to unsecure / reset JTAG fuse value. Device mass erase and JTAG fuse unlock operation can be done only by BSL (that is factory preloaded to any FR device by default and can not be modified / erased). 

  • 0 in reply to zrno soli
    Prodigy 30 points

    Hi zrno,

    I've tried to execute a MASS ERASE via BSL Scripter, to solve the "debug interface secured issue". The content of script.txt are as follow:

    ////////////////////////////////////////////////////////////////////////////////////

    MODE msp430frxx UART COM4
    VERBOSE
    DELAY 2000
    MASS_ERASE
    DELAY 2000
    REBOOT_RESET
    DELAY 2000

    /////////////////////////////////////////////////////////////////////////////////////

    Where COM4 is the application UART port of the MSP-FET Flash Emulation Tool that I used. However, the MASS ERASE failed and the error was "Unknown ACK Value". May I know if any of my step above are wrong? Thank you.

  • 0 in reply to Wui Fan Lim
    Guru 34693 points

    Connect target device with MSP-FET...

    And for BSL scripter use this script...

    C:\ti\BSL-Scripter\ScriptExampleWindows\FRxx_uart\script_FRxx_uart.txt

    Wrong BSL password should trigger mass erase. It is explained in attached pdf.

    bsl.pdf

  • 0 in reply to zrno soli
    Prodigy 30 points

    Hi zrno,

    I've connected my MSP-FET to the target device accordingly and run the script as suggested using BSL scripter. However, I am still receiving the "Unknown ACK Value" error. The "debug interface secured" issue is still there. Please advise.

    Thank you.


  • 0 in reply to Wui Fan Lim
    TI__Mastermind 39750 points

    First please check if you use msp430fr6989 or msp430fr69891 and they have different BSL interface as below

     

    And if you have logic analyzer like Saleae, you can capture the signals on the communication bus and put it here.

  • 0 in reply to Gary Gao
    Prodigy 30 points

    Hi Gary,

    I am using msp430fr6989, and my pin connection are as per the Table 6-6. I am sorry that I do not have a logic analyzer. What I can check and retrieve is the communication between the MSP-FET and the MSP430, seems like MSP430 is not replying to the MSP-FET (no "reads"):

    //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    Writes:

    000201: 2023-04-04 15:22:51.6345039 +1.0109724

     

     80 21 00 11 FF FF FF FF FF FF FF FF FF FF FF FF

     FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

     FF FF 00 00 91 FB

    €!..ÿÿÿÿÿÿÿÿÿÿÿÿ

    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

    ÿÿ..‘û

     

    000205: 2023-04-04 15:22:54.6493494 +2.0186054

     

     80 21 00 11 FF FF FF FF FF FF FF FF FF FF FF FF

     FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

     FF FF FF FF 9E E6

    €!..ÿÿÿÿÿÿÿÿÿÿÿÿ

    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

    ÿÿÿÿžæ

     

    000209: 2023-04-04 15:22:55.6567207 +0.0096794

     

     80 24 00 10 00 44 00 81 00 00 24 B1 13 94 00 0C

     93 02 24 B1 13 00 00 0C 43 B1 13 6C 00 B1 13 98

     00 32 D0 10 00 FD 3F 64 CF

    €$...D...$±.”..

    “.$±....C±.l.±.˜

    .2Ð..ý?dÏ

     

    000213: 2023-04-04 15:22:56.6505205 +0.0033186

     

     80 14 00 10 80 FF 00 FF FF FF FF FF FF FF FF FF

     FF FF FF FF FF FF FF 79 15

    €...€ÿ.ÿÿÿÿÿÿÿÿÿ

    ÿÿÿÿÿÿÿy.

     

    000217: 2023-04-04 15:22:57.6632228 +0.0062260

     

     80 DA 00 10 C6 FF 00 1A 44 1A 44 1A 44 1A 44 1A

     44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 1A

     44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 1A

     44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 1A 44 00

     44 2A 14 40 18 1A 42 5C 01 40 18 B2 40 80 5A 5C

     01 8F 00 00 00 9F 00 00 00 13 24 89 00 00 00 88

     00 00 00 0C 3C 0C 09 7F 4C 5F 06 00 18 5F 4F 00

     00 A9 00 04 00 0D 09 4F 13 A9 00 04 00 D9 08 F2

     23 7A C2 3A D0 08 5A 40 18 82 4A 5C 01 8F 00 00

     00 9F 00 00 00 09 24 8A 00 00 00 03 3C 6A 13 AA

     00 04 00 9A 00 00 00 FA 23 28 16 10 01 F1 03 B2

     40 80 5A 5C 01 92 C3 30 01 D2 D3 04 02 D2 E3 02

     02 B1 40 10 27 00 00 91 83 00 00 81 93 00 00 F6

     27 FA 3F 03 43 1C 43 10 01 03 43 FF 3F 83 9A

    €Ú..Æÿ..D.D.D.D.

    D.D.D.D.D.D.D.D.

    D.D.D.D.D.D.D.D.

    D.D.D.D.D.D.D.D.

    D*.@..B\.@.²@€Z\

    ....Ÿ....$‰...ˆ

    ....<..L_..._O.

    .©.....O.©...Ù.ò

    #zÂ:Ð.Z@.‚J\...

    .Ÿ....$Š....<j.ª

    ...š...ú#(...ñ.²

    @€Z\.’Ã0.ÒÓ..Òã.

    .±@.'..‘ƒ..“..ö

    'ú?.C.C...Cÿ?ƒš

     

    000221: 2023-04-04 15:22:58.7517743 +0.0075907

     

     80 06 00 16 00 44 00 20 00 FE 3B

    €....D. .þ;

     

    000225: 2023-04-04 15:22:59.7540431 +0.0038001

     

     80 04 00 17 00 44 00 42 0F

    €....D.B.

     //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    Reads:

    000204: 2023-04-04 15:22:52.6307440 +0.9960996

      

    000208: 2023-04-04 15:22:55.6470413 +0.9975599

      

    000212: 2023-04-04 15:22:56.6472019 +0.9903843

      

    000216: 2023-04-04 15:22:57.6569968 +1.0063635

      

    000220: 2023-04-04 15:22:58.7441836 +1.0079592

      

    000224: 2023-04-04 15:22:59.7502430 +0.9983809

    //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

    In a normal case, I will flash a crypto-bsl into the MSP430FR6989. Initially, I thought that the reason I failed to execute MASS ERASE is because there is no BSL. However, zrno mentioned that there is a BSL that is factory preloaded to any FR device by default and cannot be modified / erased, which I also agree. Please advise if there is anything else that I can try to fix the issue of "debug interface secured".

    Thank you.

  • 0 in reply to Wui Fan Lim
    TI__Mastermind 39750 points

    There is a ROM based BSL in MSP430 and as you use MSP430FR6989 that should be use a UART interface.

    The MSP-FET will ouput a signal as below to trigger the device into BSL mode

    If you connect the correct hardware signals and there is nothing on the UART RX pin that means the BSL is disabled. If the device's JTAG and BSL are locked both it will not be accessed any more.

  • 0 in reply to Gary Gao
    Prodigy 30 points

    As far as I know, MSP-FET has 2 ports, i.e the MSP debug interface (COM 5 in my case) and MSP Application UART1 (COM 4 in my case). When trying to execute a MASS ERASE, the COM port I selected was COM 4. In this case, will the MSP-FET still output a signal to trigger the device into BSL mode (I believe this should be COM 5)?

    Ehm, I am also curious on why would a brand new chip has its JTAG and BSL both locked?

    Thank you.

  • 0 in reply to Wui Fan Lim
    TI__Mastermind 39750 points
    Wui Fan Lim said:
    MSP Application UART1 (COM 4 in my case).

    Should be this port.

    Wui Fan Lim said:
    new chip has its JTAG and BSL both locked

    A new chip should not be locked. There must be something wrong with your hardware connection or operations on PC.

**Attention** This is a public forum