MSP430F5359: About the BSL scripter and the COM port number (windows)

Davide Tallone

Prodigy 10 points

Part Number: MSP430F5359

Hi.

I have a custom board running a MSP430f5359, that can and is upgraded via BSL_Scripter.

It all works fine as long as the COM port number is different than "1".

When the COM1 is selected, the following error show up in the command prompt after running the EXE file.

Fullscreen

1
2
MODE 5xx UART 9600 COM1 PARITY
        set_option: Parametro non corretto
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

MODE 5xx UART 9600 COM1 PARITY
        set_option: Parametro non corretto

"Parametro non corretto" is Italian for "Incorrect parameter".

Below is the script file run by the BSL_scripter

Fullscreen

1
2
3
4
5
MODE 5xx UART 9600 COM1 PARITY
VERBOSE
MASS_ERASE
RX_PASSWORD
RX_DATA_BLOCK Firmware.txt
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

MODE 5xx UART 9600 COM1 PARITY
VERBOSE
MASS_ERASE
RX_PASSWORD
RX_DATA_BLOCK Firmware.txt

Can anyone help me figure out what need to be written in the script file to use the COM1 (if it is possible at all)?

Davide

over 3 years ago

0 Brandon Fisher94 over 3 years ago

TI__Mastermind 28070 points

Hi Davide,

This could be similar to the issue seen in this thread: https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/511956/using-the-bsl-scripter-on-a-pc-running-windows-i-m-having-trouble-with-the-mode-command

Can you attempt this on another PC as a quick check? You should be able to use COM1 that way as long as your hardware can support that 9601Hz Baud Rate.

Best Regards,
Brandon Fisher

0 Davide Tallone over 3 years ago in reply to Brandon Fisher94

Prodigy 10 points

Thanks Brandon

You're right, it does look simililar.

I've launched the updater on two different computers, all' equiped with a native serial and both run ended with the usual error.

Instead, when using a computer with no native RS232, but with a USB to RS232 adapter set to be COM1, the error disappear.

So the problem seems to be the custom baud rate of the BSL, incompatible with the motherboard RS232.

I'll search for the sources of the BSL_Scripter, and see if the solution in the post you've linked can fix my issue.

I'll come back here with updates when ready.

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430F5359: About the BSL scripter and the COM port number (windows)