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.

CCS/MSP430FR59691: BSL is not responding

Part Number: MSP430FR59691
Other Parts Discussed in Thread: MSP-FET

Tool/software: Code Composer Studio

Hello ! 

I have a problem regarding the BSL. 

The MSP430 is definitely entering the BSL Mode, because the BSL I2C Address is acknowledged. I used the software entry, not the hardware entry.

But unfortunately the BSL never sends a response. For example i tried the command Tx BSL Version , which should work without sending the password. 

but as you can see there is no response, although the address was acknowledged.

  • Hello Martin,

    The TX BSL Version command is password protected and fails if the password has not been sent. You also do not appear to be sending the correct checksum values, CKL and CKH. I recommend that you review the BSL User's Guide (SLAU550) and use the MSP-FET alongside the BSL-SCRIPTER tool to evaluate the MSP430FR59691 BSL solution.

    Regards,
    Ryan
  • Thank you, the checksum values were not correct and now i get the a answer when sending the TX BSL Version command.

    The next problem is that i can´t unlock the BSL. I tried to send the default password (0xFF 32 times) , the MSP executes the mass erase and when i send the password again, mass erase is done again.

    I also tried the BSL-Scitper tool and i got this

     

  • Getting the correct TX BSL version command answer is a good start, make sure you are using the exact same packet as shown in Section 4.4.3.2 of SLAU550. The unknown ACK value from the BSL-Scripter indicates an incorrect connection between the MSP-FET and target device. VCC (MSP-FET pin 2), GND (9), TEST(8), RST(11), SDA(12), and SCL(10) should all be connected with pull-up resistors on SDA/SCL and a 47 kOhm pull-up and 1/2.2 nF pull-down on RST.

    Regards,
    Ryan
  • Thank you once again. I found the mistake by myself. It wasn´t just a wrong checksum it was also a wrong length byte. I mixed up decimal and hexadecimal . What a shame...

    But know everything works correctly.

**Attention** This is a public forum