| ??? 02/07/05 10:07 Read: times |
#86733 - More on Intel Hex - gaps! Responding to: ???'s previous message |
Andy Neil said:
The Intel Hex format encodes each byte as two characters, and adds some extra overhead as well Also, an Intel Hex file can skip "gaps" in your code; eg, if your project has just a few bytes of code at low addresses, and just a few at high addresses, the Hex file need only contain those few bytes but you will need a PROM big enough for the highest address - so the required PROM size could be much bigger than the Hex file size. This is why code generated by the Keil free evaluation won't fit in devices with less than 2K of ROM - because it shifts all the code up to addresses from 2K onwards! http://www.keil.com/demo/limits.htm |
| Topic | Author | Date |
| Finding out the ROM limit | 01/01/70 00:00 | |
| Tools? | 01/01/70 00:00 | |
| More on Intel Hex - gaps! | 01/01/70 00:00 | |
| k vs K | 01/01/70 00:00 | |
| Apples & Pears! | 01/01/70 00:00 | |
| Thanks | 01/01/70 00:00 | |
| Err..., no | 01/01/70 00:00 | |
| Forgot to ask - LST file? | 01/01/70 00:00 | |
| d51 | 01/01/70 00:00 | |
| Need clarification | 01/01/70 00:00 | |
| More Clarification Needed! | 01/01/70 00:00 | |
| Info | 01/01/70 00:00 | |
| More Clarification Needed! | 01/01/70 00:00 | |
| Yes | 01/01/70 00:00 | |
| Unlikely | 01/01/70 00:00 | |
| suspect | 01/01/70 00:00 | |
| Info | 01/01/70 00:00 | |
| Got there at last! | 01/01/70 00:00 | |
| Got it :D | 01/01/70 00:00 | |
| Too big! | 01/01/70 00:00 | |
| Thanks | 01/01/70 00:00 | |
| 7 days | 01/01/70 00:00 | |
| I suggest this | 01/01/70 00:00 | |
| something amiss | 01/01/70 00:00 | |
| the whole LST file | 01/01/70 00:00 | |
| LST file | 01/01/70 00:00 | |
| and the story is | 01/01/70 00:00 | |
| well.... | 01/01/70 00:00 | |
| 7 days well spent! | 01/01/70 00:00 | |
| of course it does | 01/01/70 00:00 | |
| Noted | 01/01/70 00:00 | |
| so | 01/01/70 00:00 | |
hexmap | 01/01/70 00:00 |