HEXMATE Conflict Report Address Error

When HEXMATE generates a conflict report, the address of the conflict in the HEX file is sometimes not the same as the address shown in a memory window (where the data resides in memory). Take a look at the example given below.

Device Family Address in HEX File Address in Memory
Baseline 0x100 0x80*
Midrange 0x100 0x80*
PIC18 MCUs 0x100 0x100
16-bit Devices 0x100 0x80*
32-bit Devices 0x100 0x100
* For some devices, the address shown in the conflict report is twice as large as the address of the data in memory.
© 2024 Microchip Technology, Inc.
Notice: ARM and Cortex are the registered trademarks of ARM Limited in the EU and other countries.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.