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.
Hi,
I have tried to flash MSP430F5529(Launchpad) using BSL Scripter via USB(without MSP BSL Rocket) and it was successful. However, While flashing it using BSL Scripter via UART(using MSP BSL Rocket) didn't work out. It was showing acknowledgement error from the password unlocking itself. I have attached the script files and its output for your reference.
The above shown screenshot shows the output of flashing the chip using BSL Scripter using USB, without MSP BSL Rocket.
The above shown screenshot shows the output of flashing the chip using BSL Scripter using UART.
The UART connection was done as follows :
MSP430 ------> MSP BSL Rocket
P1.1------------>TX(1)
P1.2------------>RX(3)
SBWTCK----->TEST(7)
SBWTDIO---->RST(4)
VCC------------>VCC(6)
GND------------>GND(5)
We also tried to change the TX & RX pins connections, still had the same issue.
Kindly help me out with the following queries :
1. More information regarding the script of UART BSL Scripter and its connection from target with MSP-BSL Rocket.
2. Is it necessary to upgrade the firmware to that of UART BSL in the MSP430 chip. If yes, How to upgrade the new firmware?f
(We also tried to flash MSP430 with BSL Image provided by TI, i.e BSL.00.07.05.04.txt from the path : MSP430BSL_1_02_00_01/Released_BSL_Images/MSP430F55xx_Family/UART BSL , using UART BSL with MSP BSL Rocket. Still it showed the same No ACK error while password unlocking)
We tried to flash the MSP430F5529 with UART BSL image via standard JTAG/SBW through uniflash by enabling the BSL memory region. After that we are not able to flash the program via CCS, but an error was shown while debugging "Error connecting to the target: The Debug Interface to the device has been secured". We were also not able to get into BSL mode by pressing the BSL button.
By any chance, is the MSP430F5529 chip locked? If so, is there any way to recover the board?
Now we are not able to do anything with board!!Please help.
JTAG fuse value is stored at the end of the BSL memory, and during updating BSL by JTAG/SBW interface factory default fuse value (0xFFFF) is changed.
JTAG/SBW interface will not work because of "blown" JTAG fuse.
Pressing BSL button is irrelevant, because it is related to factory preloaded HID BSL, that is erased / overwritten with UART version.
If UART BSL image is wrong / not working than device is bricked. If UART BSL image is working fine, then JTAG fuse value can be overwritten to value 0x000 and unlocked by BSLScripter.
I think the device is bricked because we are not able to get into BSL mode to execute the UART BSL scripter. Is there any way to recover the device?
With JTAG secured and not working BSL F5xx device is bricked, without recover possibility.
Also, in our custom board, we are using MSP430F5358 & from the datasheet, we found that its default BSL is UART BSL, whereas in MSP430F5529 LP, the default BSL is USB BSL. So, in our custom board, where we are using MSP430F5358, we could invoke the MCU to BSL mode via software invocation and then run the UART BSL scripter from the test pc. So we have a few queries regarding this :
1. Is the above mentioned steps correct or are we missing any critical steps?
2. As MSP430F5358 has default UART BSL, do we have to flash the UART BSL image again through JTAG/SBW as we have done with MSP430F5529 LP? If so, will we get the same issue of bricking the MCU, we cannot risk bricking that MCU.
3. In the BSLScripter-3.4.0.2-linux64-installer, we found some examples for 5xx_USB under the path:( BSL-Scripter/ScriptExampleLinux). But we didn't find any UART examples(the script files and .txt files) for 5xx family. Where can we find the BSL Scripter that needs to be used for UART BSL flashing?
4. Which all devices can be used as the UART-to-USB communication bridge for the UART BSL Flashing? And also for these devices, should we preprogram the interface device for making it compatible for UART BSL flashing to work.
N.B: We are mainly using Linux PC for testing purpose.
1. Devices with factory preloaded UART BSL should work fine with BSL Scripter by UART interface.
2. There is no need to touch original UART BSL.
3. Scripts for USB / UART BSL are almost identical, there is only difference regarding interface / connection (USB / COMxx)...
1st line for USB Script ---> MODE 5xx USB
1st line for UART Script ---> MODE 5xx COM24
4. Try to find on e2e or other forums confirmed bridges that working with MSP430F5xx family. For example...
sustburbia.blogspot.com/.../the-great-msp430-bootloader-swindle.html
Just note that eZ-FET on your 5529LP with bricked target device (F5529) is still fully functional and can be used with any off board MSP430 target device for debugging or flashing.
Thank you for solving our queries. I have one more doubt, Is it necessary to use the BSL Transmit & Receive pins of MSP430( i.e P1.1 & P1.2) for BSL Scripter. Could we use the other available UART pins(USCI_A1 : P8.1 & P8.3) for this purpose? Will there be any configuration changes which we have to do from the software side or hardware side for this to work for UART BSL.
TI factory UART BSL can only work with pins specified in device datasheet. To use other pins and UART (UART is not used in factory version) BSL must be customized. Unfortunately, JTAG fuse is located at the end of BSL area, and TI tools will not prompt user before changing fuse value, so user must be sure that generated binary will not lock JTAG.
There are also open source firmware update tools from TI like BSL, that will not touch original BSL for example MSPBOOT.
https://www.ti.com/tool/MSPBSL -> Main Memory BSL's -> MSPBOOT
**Attention** This is a public forum