Closed GoogleCodeExporter closed 9 years ago
Hello,
I am getting all the time:
$ ./stm32flash /dev/ttyS0
stm32flash - http://stm32flash.googlecode.com/
Serial Config: 57600 8E1
read_byte: Success
stm32flash: stm32.c:90: stm32_read_byte: Assertion `0' failed.
Aborted
Original comment by hector.o...@gmail.com
on 15 Dec 2010 at 1:51
I no longer have the original bin_to_c.sh script, all it did however was
convert the stmreset.bin to a const char array in stmreset_binary.c. If you are
willing to re-write it feel free.
As for the failure to flash, I believe this has been corrected, please try the
latest release.
The aborted error could be because the board needs a power cycle to reset it
back to the boot loader auto baud detection routine.
Original comment by ge...@spacevs.com
on 26 May 2011 at 5:08
Hello,
I also keep getting the following message:
$ ./stm32flash /dev/ttyS0
stm32flash - http://stm32flash.googlecode.com/
Serial Config: 57600 8E1
read_byte: Success
stm32flash: stm32.c:90: stm32_read_byte: Assertion `0' failed.
Aborted
However, I believe I have the latest version.
Now, does this program communicate with the stm32 vl discovery as-is? If not,
how would I get it to work with the discovery board?
Thanks in advance,
Vaati
Original comment by ecthil...@gmail.com
on 1 Jun 2011 at 4:24
I do not have a stm32 v1 descovery, nor am I familiar with it, but it does
follow the official ST bootloader protocol as documented in:
http://code.google.com/p/stm32flash/source/browse/trunk/protocol.pdf
The assertion is due to a failure to read from the device, does the official ST
flash loader work? If so, can you please run the program with gdb and provide a
backtrace, eg.
gdb ./stm32flash
set params /dev/ttyS0
r
>> Wait for the assertion <<
bt
Thanks.
Original comment by ge...@spacevs.com
on 2 Jun 2011 at 11:19
[deleted comment]
I got this error when i had connected my RX/TX wrong.
Serial Config: 57600 8E1
read_byte: Success
stm32flash: stm32.c:90: stm32_read_byte: Assertion `0' failed.
Aborted
try to switch the wires for RX and TX. It worked for me ;)
Original comment by anton.fo...@gmail.com
on 1 Jul 2011 at 3:42
Was a wiring issue, closing
Original comment by ge...@spacevs.com
on 4 Oct 2011 at 2:39
Original issue reported on code.google.com by
hector.o...@gmail.com
on 9 Dec 2010 at 4:22