| ??? 11/02/04 20:23 Read: times |
#80284 - RE: Hex2Bin Pad Data Command Line Argument Responding to: ???'s previous message |
It works!!
The run-time checksum system error messages are gone!! It seems odd that specifying to size of the file to be 64k causes it to fill with 0xFF, but allowing the program to default to 64k causes it to fill with 0x00. I still am not actually passing in the pad data, but taking advantage of a characteristic of the program that causes a different pad value when the length is provided. Thanks!! |
| 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 |