[SOLVED] verification of automated flashing?

max · Jan 25th 2018, 9:40am

Hi there,

i am using the J-Link Commander to flash my EFM32
I wrote a little batchfile for the commander to automate the process. A CommanderScript passes the right commands. It looks like this.

Source Code

h
log C:\flashtest/result.log
erase
loadbin C:\flashtest/myTestFW.bin, 0x00
verifybin C:\flashtest/myTestFW.bin, 0x00
r
q

So I log the process in the logfile. My Problem is, how can I detect a successful flashing/verification? Is there any line/option that I can read out to verify that the new firmware is on my board? There is an environment variable %ERRORLEVEL% but as far as i know, it only shows that the JLink.exe finished successfully, but doesn´t show the flashing/verifycation result.

A different approach I have in mind would be to add a further step to read out the FW with savebin and then make a checksum with FCIV against the myTestFW.bin file.

Do you have any other suggestion?

cheers

max

SEGGER - Nino · Jan 25th 2018, 10:35am

Hello Max,

Thank you for your inquiry.
For this case we have implemented the command line function "exitonerror".
More information can be found in the J-Link user manual (UM08001_JLink).

Best regards,
Nino

max · Jan 25th 2018, 12:07pm

Hi Nino,

thanks for your quick response. I got the exitonerror running now. It detects wrong filename, etc. and sets ERRORLEVEL to 1. However it doesnt set ERRORLEVEL to 1 if
verifybin detects a different bin file.

For example:

Source Code

loadbin C:\flashtest/myTestFW.bin, 0x00
verifybin C:\flashtest/myDifferentFW.bin, 0x00

cmd-line says:

Source Code

Verify failed @ address 0x00000004
Expected F4 read 01

Isn´t this supposed to be an error?

cheers

max

SEGGER - Nino · Jan 26th 2018, 2:47pm

Hi Max,

It is only an error if the file you want to verify does not exist.
If it is available on the harddrive it should not throw an error when opening.

Best regards,
Nino

Source Code

Source Code

Source Code

Share