mitchd/stm32sprog

Automatically exported from code.google.com/p/stm32sprog

stm32sprog's Issues

Investigate use of GO command to run firmware

It might be possible to use the GO command to run the user's firmware after 
writing.  Determine whether this is possible and, if so, implement it.

Original issue reported on code.google.com by [email protected] on 6 Dec 2010 at 2:44

Extra ACK at beginning of first read operation

It looks like I'm forgetting to check for an ACK somewhere, so it's being left 
in the input buffer until the verify operation chokes on it.  I'm currently 
working around this by discarding a byte at the beginning of the first read.

Original issue reported on code.google.com by [email protected] on 7 Dec 2010 at 1:32

Serial abstraction layer

Create a serial communication abstraction to hide platform specific code.

Original issue reported on code.google.com by [email protected] on 8 Dec 2010 at 12:14

Improve IO error handling

Values returned by `read()` and `write()` are currently ignored.  This has not 
yet been a problem in practice, but it would be nice to do The Right Thing, and 
might prevent problems in untested scenarios.

Original issue reported on code.google.com by [email protected] on 6 Dec 2010 at 2:42

Add support for Intel HEX files.

Allow the user to specify an Intel HEX format file with the `-w` argument.  The 
software should do its best to automatically detect files of this format.  It 
should also be possible to manually specify Intel HEX or other formats.

Original issue reported on code.google.com by [email protected] on 8 Dec 2010 at 12:08

Add support for Motorola S-record files.

Allow the user to specify an SREC format file with the `-w` argument.  The 
software should do its best to automatically detect files of this format.  It 
should also be possible to manually specify SREC or other formats.

Original issue reported on code.google.com by [email protected] on 8 Dec 2010 at 12:09