??? 11/02/04 20:13 Read: times |
#80282 - Answer is wrong - gaps in Hex files Responding to: ???'s previous message |
Ijaz Ahmed said:
But if I am not wrong, it can not be Hex2bin.exe which is filling space with zeros. For example if your .hex file contains 240 bytes of code, Hex2bin.exe should generate a binary file of the size 240 bytes. How does Hex2bin.exe know that it should fill in zeros and upto what length? I'm afraid you are wrong. :-( Each record in an Intel Hex file specifies a start address. There is no requirement for adjacent hex records to be contiguous - gaps are perfectly acceptable. Binary files, on the other hand, must contain exactly one byte of file data for each byte of the memory are to be programmed. Thus, any utility to convert an Intel Hex file to a Binary file must provide some means to fill any gaps! |
Topic | Author | Date |
Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
It worked for me | 01/01/70 00:00 | |
RE: It worked for me | 01/01/70 00:00 | |
RE: It worked for me![]() | 01/01/70 00:00 | |
Answer is wrong - gaps in Hex files | 01/01/70 00:00 | |
RE: Answer is wrong - gaps in Hex files | 01/01/70 00:00 | |
More info | 01/01/70 00:00 | |
RE: Hex2Bin Pad Data Command Line Argument | 01/01/70 00:00 | |
RE: alternatives to Keil Hex2Bin | 01/01/70 00:00 |