Intel HEX output format needed

Intel HEX output format needed

[DavidGriffith]

The code to do this is extremely simple. I'm looking at adding an -f flag to indicate what sort of hex format to use. For instance: minipro -p "M27C256B @DIP28" -r foobar.hex -f i8 for Intel I8HEX.

[chenz]

Maybe it would be better to go the Unix way and implement piping, and leave format conversion to external tools, ie srecord (http://srecord.sourceforge.net/).

EDIT: by "piping", I don't mean shelling out to a conversion tool, but to simply implement reading/writing from/to stdin/stdout. This would also require a cleanup that I was already about to suggest for #113 - keep stdout clean of any log messages (ie print those to stderr), and reserve stdout for the actual output of the operation.

[elosha]

It would be fine if both piping (for extension and unixability) and few most common formats worked.

Why I think some hex formats should be put directly into minipro: The purpose of those formats is to provide targets & programmers with a checksummed code image, so why reject that. "srecord" as a mighty editing and conversion tool retains its legitimation.

@DavidGriffith: Just a guess, probably most people will be happy if the very commong Intel Hex (.hex) and Motorola S-record (.S) are understood, right? One can recognize those two by filename extension (no binary image will be called foobar.hex), so -f should be an override flag, I suggest.