Obviously the CRC value will need to be stored in an area that is not part of the computation. I am using a CRC to verify EEPROM data in our STM8S is valid. My implementation is similar to the one at the URL below but uses only 8 bits and stores constant lookup table in code to save RAM and CPU time. However, the application does all of the calculation and verification (at run time).

http://www.lammertbies.nl/comm/info/crc-calculation.html

I have not yet tried to have the linker / toolchain automatically add this to the output file though. In another post I was told that Raisonance is hoping to release a new software version this month that will have better support for things like not erasing the EEPROM section during programming. Perhaps there will be more options for this as well.

In the mean time, what you might be able to do is locate a variable in non-volatile code or data space (Flash/EEPROM) and reference it in your code.

unsigned char at 0x4000 programmed_crc;

Then at build time, you could have a custom script run that generates the CRC and writes it to the fixed location in the output file. Or perhaps you could even copy and paste it with a hex editor, though that is less automated.

HTH