MSP432-DEBUGGERS: BSL Scripter command line behaviour

Paul Bar

Part Number: MSP432-DEBUGGERS
Other Parts Discussed in Thread: MSPBSL

Hi All,

I am using the BSL Scripter 3.2.1 in a .bat script. The problem I have is that when the script exit I need to be able to check if the programming was successful.

Right now I have

call BootViaTi\BSL-Scripter.exe BootViaTi\Tmp\script.txt
IF %errorlevel% NEQ 0 (
    echo Error while executing TI script
    echo Exiting...
    exit /B 0
)

However, the BSL-Scripter will always return %errorlevel% = 1 no matter if the script was a success or not.

Any way to get the right exit command?

over 7 years ago

0 Paul Bar over 7 years ago

Intellectual 375 points

I meant that I have the following

call BootViaTi\BSL-Scripter.exe BootViaTi\Tmp\script.txt %1
IF %errorlevel% NEQ 0 (
    echo Error while executing TI script
    echo Exiting...
    exit /B 0
)

I had forgotten the %1 at the end. It is there and it does not change a thing

0 Chris Sterzik over 7 years ago in reply to Paul Bar

TI__Guru 68021 points

Paul,
I have quickly looked through the source code found in the tool (C:\MSPBSL_Scripter_win\SourceCode) and I do not see where this message is defined. I have reached out to one of my colleagues for help.

Chris

0 Paul Bar over 7 years ago in reply to Chris Sterzik

Intellectual 375 points

Do you have any news on that?

0 Chris Sterzik over 7 years ago in reply to Paul Bar

TI__Guru 68021 points

Paul,
Unfortunately no. The BSL should return '0' but then throw an exception if an error occurs (as opposed to an integer). The issue is trying to reproduce this in the context of a batch file. I will post again Tuesday for an update, if there is no update before then.
Chris

0 Chris Sterzik over 7 years ago in reply to Paul Bar

TI__Guru 68021 points

Paul,

We were able to recreate the issue and it is a bug in the scripter tool. I have filed a bug against the tool and the team will work to revise.

Regards,

Chris

0 Paul Bar over 7 years ago in reply to Chris Sterzik

Intellectual 375 points

Thanks for the feedback.

Right now I am getting around this bug by placing all the output message in a text file. I then filter the text file and check for the "error" keyword. Not the most elegant and efficient solution, but right now it works.

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP432-DEBUGGERS: BSL Scripter command line behaviour