What will be included in the checksum calculation?
Generally speaking: “All bytes in the application that must be downloaded to the target, will be part of the checksum calculation.” The simplest way of get knowledge about this is to turn on “checksum calculation” + “map file” in the options for XLINK. Then look at the end of the .map file to see which ranges in which memory that will be included in the checksum calculation. Please note that DATA will normaly not be included in the checksum calculation, but that XDATA (and some other segment types) can be included besides the CODE segment type. If other segment types (than CODE) are included, then you can exclude those segment types. (The example for EWAVR has the -J option set up in such a way that XDATA is not included in the checksum calculation.) Checksum calculation in the application The supplied examples show how to use the CRC16 checksum calculation. In the C source of the application you need to add the actual generic C source to calculate the same checksum value as XLINK prod
