We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hi,
I wrote a perl program which calculates the CRC32 checksum of my .hex generated file (previously converted to binary of course). So I should just have to write it back to my .hex file at a fixed memory address for example and test it from my boot code.
The problem I have is that I don't know if Keil linker inserts holes (not programmed bytes) in the built .hex file.
If so, my perl cksum calculation will be wrong since it does not take into account these holes. The embedded cksum code will calculate the cksum on a range of adresses including non programmed bytes (0xFF)... :-(
My questions are : - Is the linker inserting holes in the generated .hex? - If so, is there a means to force it to fill holes with a specific value in the .hex file; 0xFF for example... ;-) ?
Thank you very much for your precious help !
Pierre
PS : I found a FLASH Fill Byte field in the Output options : could it be these famous option I'm looking for ?
My mistake: a BIN file is always a verbatim record of every single byte in its address range;
The HEX file may or may not contain gaps, and it's HEX2BIN that decides what to do in any gaps.
The conversion from the Linker's output file is done by the Object-to-Hex converter: http://www.keil.com/support/man/docs/oh166/