??? 11/02/04 20:18 Read: times |
#80283 - RE: Answer is wrong - gaps in Hex files Responding to: ???'s previous message |
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. Very right. Thanks for the logical information. |
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 |