Using Keil Hex file for programming

>After reading thu http://www.keil.com/support/docs/1584/ i created a python
>which turns the hex file to c sructure

I don't know why you are doing this. A hex file is text and two hex files can be compared with a text editor to see if they are identical. If the hex file comes from different sources (programmer or MDK), you might have to convert it. However, there are free tools available to convert files to any format with many options. Please see:
http://www.keil.com/support/docs/274.htm (convert to binary file)
http://www.keil.com/support/docs/2218.htm (convert to C compatible constants)

Please send an example of the code differences in the support case you have opened.

>After reading thu http://www.keil.com/support/docs/1584/ i created a python
>which turns the hex file to c sructure

I don't know why you are doing this. A hex file is text and two hex files can be compared with a text editor to see if they are identical. If the hex file comes from different sources (programmer or MDK), you might have to convert it. However, there are free tools available to convert files to any format with many options. Please see:
http://www.keil.com/support/docs/274.htm (convert to binary file)
http://www.keil.com/support/docs/2218.htm (convert to C compatible constants)

Please send an example of the code differences in the support case you have opened.

.HEX file do not have to be linear, or describe all memory. You'd do better converting each to a binary image for the ROM(s) in question and doing a binary compare. If you normalize the files you might be able to do a diff/compare, but if you understood the data and what it is describing you'd appreciate there are more effective ways to do that.

The Keil tools send programming code into RAM, and then send blocks of binary data in to RAM, and execute the programming code. They don't send the .HEX or .AXF files directly.

Hi,

Thank you for the links actually I looked for these kind of tools but then wrote them..
Now I verified with my program again and after reading the KEIL programming process I reset my module before creating the dump from within my design, so that I was not running with debugger, and now indeed the Keil output and memory dump look identical.

I also dumped from within the Keil using the save command and received the same file.

So I think we can close the support case

Thank you