some binaries can not be flashed and a slight changes in code it flashes again

[GoogleCodeExporter]

Trying to flash using 0.3 version sometimes end with output as follows

stm32flash -v -w release.bin /dev/rfcomm1 -b 921600
stm32flash 0.3

http://stm32flash.googlecode.com/

Using Parser : Raw BINARY
Serial Config: 921600 8E1
Version      : 0x22
Option 1     : 0x00
Option 2     : 0x00
Device ID    : 0x0410 (Medium-density)
- RAM        : 20KiB  (512b reserved by bootloader)
- Flash      : 128KiB (sector size: 4x1024)
- Option RAM : 16b
- System RAM : 2KiB

Wrote and verified address 0x08006d00 (99.09%) Failed to write memory at 
address 0x08006d00

Resetting device... Got NACK from device on command 0x31
failed.

And if I changing code slightly it's flashed without issues!
In case I cannot flash some particular binary with stm32flash I use STM Flash 
Loader Demonstrator. It works without problems but requires me to boot into the 
windows.

As for 0.4 version it doesn't work at all with /dev/rfcomm1 as I describet in 
other issue 69 (https://code.google.com/p/stm32flash/issues/detail?id=69).

Original issue reported on code.google.com by Ali.Tli...@gmail.com on 23 Feb 2015 at 11:16

[GoogleCodeExporter]

The same behaviour was detected with ftdi uart-usb converter and at differnet 
baudrates starting from 9600. So the issue is not about rates or interface 
used. The issue is only about particular binary. Unfortunatley I can't attach a 
binary because it is a commercial property. But may be issue is similiar with 
issue 62. Allthough the program output is different there but it is also 
depends of particular binary.

Original comment by Ali.Tli...@gmail.com on 23 Feb 2015 at 11:50

[GoogleCodeExporter]

by the way my host is Ubuntu linux 14.10 3.16.0-29-generic

Original comment by Ali.Tli...@gmail.com on 23 Feb 2015 at 11:53

[GoogleCodeExporter]

What is the size of the file?

Original comment by lists.to...@gmail.com on 24 Feb 2015 at 8:49