MSP430F2274 BSL Error

Hi Roman, 

   This error is strange, as the BSL included in the 2274 is "older".  I suspect the PC application is incorrectly reporting this error.  Could you provide more information:

1) The version of the PC application being used

2) The command being send (the command line parameters entered)

3) The text file, or information about it (specifically the address ranges being written)

Correction: The BSL included in the 2274 is not "older".

Hi Lane,

thanks for your comments!

1) The version of the PC application being used

=> Free MSP430 Programming Utility Version 1.6.1007

2) The command being send (the command line parameters entered)

      => First of all the erase comand and then blank check device memory. See also including files ( .doc + .txt )!

3) The text file, or information about it (specifically the address ranges being written)

  => Please see including files!

THANK'S

Roman

>Free MSP430 Programming Utility Version 1.6.1007

I see, my apologies.  I'm not familiar with this application at a low level to know exactly what BSL commands are failing.  Perhaps contact the developer, as this might be something to ask them.

However, in order to check that the device is working correctly for erase/program, I would try using the BSLDEMO2.exe application included in the zip file with SLAU265.  Look in the BSL zip file under: BSL_Files\Deprecated\BSLDEMO\EXE

Hi Lane,

I just tried to work with your BSLDEMO2.exe application and I get every time the error message:

ERROR: Synchronization failed!

Device with boot loader connected?

But my PC is connected with my test board (MSP430F2274) and COM1

Have you any idea what I do wrong?

My be you have other BSL tool (more comfortable)?

Thanks

Roman

Hi,

   I realize this is an older thread, but I just wanted to follow up and see if the issue is resolved, or if you have any additional information.  From my side, it apepars to be an issue with BSL invoke, so I would double check your hardware, and BSL signals... probing the device at the pins to be 100% sure the invoke and UART commands are being received correctly.

Hi, I am getting the same error when trying to invoke BSL on my msp430F2274, I have checked the com port and connections, but I am able to load normal with my jtag. I need to use BSL for this:

...\slaa535a\LPAD_BSL_INTERFACE\TestScripts\Exe>BSLDEMO2.exe -cCOM16 -m1 +epvrw HeaterBSL.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?
----------------------------------------------------------- Press any key ...

Tom,

I remember creating batch file to do firmware update on MSP430F2274 using the BSLDEMO2.exe in the SLAA535 application note.

The batch file and other collateral files can be downloaded in the following link: http://www.ti.com/lit/zip/slaa535.

Hi Leo,

You can see from my post that I already am using the bsldemo2.exe from slaa535?? 

It is not working, giving me the same error and I have checked all my pin connections.

Tom,

you were right, sorry for that. Have you tried to check the BSL connections? The SLAA535 app note lists also the pin used for MSP430F2274 (RST, TEST, P1.1 - BSL TX, P2.2 - BSLRX). Can you see that your interface generating the RST TEST signal for BSL invokation? One basic thing you can try to check is that when BSL successfully invoked, the BSL TX pin (in this case P1.1 for the F2274) will be pulled up.

Leo,

I can get it to work with an old BSL Scripting Application 1.01... (so the hardware/pins are correct)

But the slaa535 says to use BSLDEMO2 as shown above and I get the same error...

the old bsl script uses these commands in script.txt:

// BSL VERSION 2.02 - 2.13 on MSPF22XX
RTS_INVERT
INIT_COMM ROM COM4
INVOKE_BSL
TX_BUFFER_SIZE
RX_PASSWORD Password.txt
ERASE_SEGMENT 0x8000
RX_DATA_BLOCK myLed1.txt
CLOSE_COMM
DELAY 20000

the new bsl_script app v 1.06 does not recognize the above commands.

Hi Tom,

I have never used the BSL Scripting Application 1.01 before. However it works, I don't see why it shouldn't work with the SLAA535A launchpad solution as long as you are working with 9600 baud, since the Launchpad only works as UART bridge.

Leo,

I am using the compiled source for bsldemo2 and it fails at:

if (bslSync() != ERR_NONE)
{
return(ERR_BSL_SYNC);
}

what else would cause this if the uart is connected properly??