| ??? 03/17/06 08:51 Read: times |
#112369 - A Note on HEX files Responding to: ???'s previous message |
A Hex file might contain data for only those locations that are actually programmed - it could have gaps.
A bin file cannot have gaps - so it will have to program something into every single location within its address range. Usually, hex-to-bin converters have options on what to do with "unprogrammed" bytes in the hex file... Check your options! |
| Topic | Author | Date |
| .bin image when burnt does not function | 01/01/70 00:00 | |
| why not... | 01/01/70 00:00 | |
| Too many variables | 01/01/70 00:00 | |
| Hex file tested works fine | 01/01/70 00:00 | |
| so why | 01/01/70 00:00 | |
| hex works but not the bin | 01/01/70 00:00 | |
| Their problem? | 01/01/70 00:00 | |
| could it be | 01/01/70 00:00 | |
| A Note on HEX files | 01/01/70 00:00 | |
| The reason for Intel Hex | 01/01/70 00:00 | |
| Bin file compare | 01/01/70 00:00 | |
| You need the customer to do it | 01/01/70 00:00 | |
| Why not hex | 01/01/70 00:00 | |
my very first suggestion in parallel pos | 01/01/70 00:00 |



