Hello priyanto,
I assume that your "raw data bytes" are a binary image of the contents of (flash/PROM/RAM) memory. A problem you may be encountering is that the first byte of the data would be assumed to commence at address 0. However, this is probably not what you require - you probably need to offset the data to start at a specific non-zero location. The simple utilities that you mention may not have the capability to provide an offset for the data, required for the S19 file.
Also note that the S19 format (and also the Intel hex format) represent all data as printable ASCII characters. So the byte value 0x01 is represented by the character sequence "01" (0x30, 0x31). However, when an S19 file is loaded, each byte value will be decoded from its two-character sequence. There may be some confusion about this.
Regards,
Mac
PS
I have subsequently done some quick tests with BIN2S19 and BIN2MOT utilities. Both seem to have the ability to provide data offset. I had no problem with BIN2S19, and it produced the expected result with the command line "BIN2S19 file.bin offset", with the offset expressed in hex.
However, I could not get BIN2MOT to produce the correct offset - but perhaps I did not correctly set up the command line options.
Message Edited by bigmac on 2006-06-22 04:22 PM