Hi everyone,

trivial question:

I am developing a bootloader for an ASIC chip. The bootloader should make it possible to download the intel-hex file to the chip flash memory and also to read the flash contents back to the intel-hex file.

I am using InteHex-80 format. I have noticed that after compilation of a C project with Keil compiler the data size in the hex file is not aligned (the data length is different). Also there are jumps in the address.

For example:
:1006B700C31202FC5035900086E0FCA3E0FDA3E0E6
:1006C700FEA3E0FF90008612030D900086E0FCA3D6
:1006D700E0FDA3E0FEA3E02401FFE43EFEE43DFDD0 - data length 16 byte
:0B06E700E43CFC90008612030D809F95 - data length 8 byte
:0106F20022E5 - data length 1 byte
:10040400900064EEF0A3EFF0A3E0FCA3E0FDA3E012 - address jump to 404
:10041400FEA3E0FFEC33900066504FA3A3A3E012C9

So downloading the hex file to the Flash is no problem. But when I read the Flash contents back to the PC and I re-generate a hex file, I get a different file (I don't have memory jumps and the data lengths I align always to 16byte)

My (maybe lamer) questions are:
Is it a problem if the hex data readed back from the FLASH has different data and adress format than the original compiled one (I assume the data is always the same)?

Why does Keil not align the data length and does not sort the address numbers in the hex file?

thanx for the answer,

greetings

Attila