I use a separate utility to insert a CRC into the code image that can then be checked by run time code to verify the integrity of the code image. This is especially handy when doing in-system code updates. The actual CRC value is brought into the code via a small text include file that is then compiled and ORG'd to the correct offset in the image. First time the project is ever built this include file is hand edited to contain zero's value. A batch file is used to build the code and that runs my utility to create the CRC include file after the linker has produced a binary image with which to parse and compute upon. My normal build process for production is to always run the built twice in a row to get the correct CRC embedded into the release image. During initial code development I turn off the CRC validity checking at startup so that I can avoid having to do the double builds each time I want to test.

I'd be happy to share the C source code for this utility if you can make use of it. You could compile it in house with company owned tools to alleviate the concerns with whacky binary downloads off the web.

Michael Karas

BTW, If you need a different check code formula / algorithm my source code can be easily changed to produce a worthless sum check, a mediocre XOR check code, or some other stronger CRC algorithm.

BTW, I could probably be convinced to prepare a skeleton project that shows this CRC scheme of mine implemented as a framework to add to any other project.