Offset command line option ignored
Intel Hex or Motorola Hex file converter
Brought to you by:
jpelletier
From user reviews:
'My program starts at 0.0D00, and ends at 1.FFFE. The program seems to detect that and reports those as last and first address, but the BIN file it makes does seems to start at 0.0000. with in byte 0.0000 the data that is supposed to be at 0.0D00 I tried to give an offset with -s 00D00, but it does not seem to do anything different. Too bad, because it does fill in the padding nicely with FF, or what I tell it to pad with.'
It would work as expected with -s 0000 instead of -s 0D00. Bin file will begin at 0.0000 with 0.0000 to 0.0CFF padded, code at 0.0D00 to 1.FFFE.
Last edit: Jacques Pelletier 2015-02-26