MSP430FR5969: BSL-scripter tool not working with MSP-FET

Hi Ryan,

Thanks for your response. I will connect board power to VCC_TARGET and try.

Sorry I forgot to attach the console screen shot showing the error message - attaching  below.

Regards,

Jay

Hi Ryan,

Now strangely, if I run the bsl-scripter multiple times the MASS_ERASE command seems to be working after several trials. The ACK_ERROR_MESSAGE is appearing always - even when the MASS_ERASE works.

Regards,

Jayaraj

Jay,

I already told you that this is expected behavior as the MSP will not give an expected response after its main memory has been erased. What's important is that the device can be accessed and written to afterwards, which depends on the RX_PASSWORD, RX_DATA_BLOCK, and SET_PC commands.

Regards,
Ryan

Ryan,

The problem with mass erase in my case is that it is not working consistently - it works only after several attempts (I know this since a program was loaded into the FRAM via JTAG). Your point regarding the error message on MASS_ERASE is noted.

After a successful mass erase when I try to write a program via BSL I'm still getting the same ACK_ERROR_MESSAGE on all the commands. After mass erase I am using the default password - I've copied the password command/default password file from the zip you provided.

I am attaching the screen shots of the password command and the RX_DATA_BLOCK command's error message. Although the actual code size is more than 10KB only 314 bytes were written.

Script:

MODE FRxx UART 9600 COM4
VERBOSE
RX_PASSWORD password_wrong.txt
DELAY 2000
RX_PASSWORD password_default.txt
RX_DATA_BLOCK program.txt

Thanks,

Jay

Password command output:

RX_DATA_BLOCK command output:

Sending the default password should return successfully, if this never happens then a connection issue could still be present.

Regards,
Ryan

Jayaraj Poroor said:

Part Number: MSP430FR5969

I'm not able to get BSL-scripter tool work with MSP-FET to program my MSP430FR5969 board.

MSPFlasher and CCS are working fine on the board via MSP-FET's JTAG. Spy-bi-wire using Launchpad is also working fine on the board.

BTW, why you need BSL at all? FR5969 can be locked and unlocked (mailbox mass erase) by SBW / JTAG.

Thanks for your response.

For code protection I was thinking of locking out JTAG (lock without password) and then using BSL to mass erase in case I need to reprogram (which also resets the JTAG lock).

Of course I can set the JTAG password instead of locking it out - but JTAG does not seem to have the BSL security feature of automatically erasing the memory in case of invalid password attempt. This seems to be a good deterrent against brute force attack.

Jayaraj Poroor said:

Thanks for your response.

For code protection I was thinking of locking out JTAG (lock without password) and then using BSL to mass erase in case I need to reprogram (which also resets the JTAG lock).

Of course I can set the JTAG password instead of locking it out - but JTAG does not seem to have the BSL security feature of automatically erasing the memory in case of invalid password attempt. This seems to be a good deterrent against brute force attack.

On new FRAM devices JTAG / SBW can be locked without password (05555h, 05555h), and than unlocked by JTAG / SBW with erase by mailbox / boot code. There is no reason to mess with BSL.

Check TOTAL ERASE option for FR58x FR59x FR68x FR69x (01B1Bh) and USER CODE ERASE for FR2xx FR4xx (01A1Ah) on MSP-Flasher or flashing tool that you are using.

If this works then this is the best option. I locked the JTAG without password (MSPFlasher -f option). Then when I tried the ERASE_TOTAL option I'm getting the error "The debug interface to the device has been secured."  (screenshot attached).

As mentioned in the original post, I'm using MSP430FR5969.

Jayaraj Poroor said:

If this works then this is the best option. I locked the JTAG without password (MSPFlasher -f option). Then when I tried the ERASE_TOTAL option I'm getting the error "The debug interface to the device has been secured."  (screenshot attached).

As mentioned in the original post, I'm using MSP430FR5969.