Maintaining Cache Coherency

The MPLAB® XC32 C compiler’s runtime start-up code enables the cache and configures it for the highest performance (write-back with write allocation). This requires you to manage any potential cache coherency issues.

Any time two resources on a device depend on the same block of memory, you have to control access to that memory to ensure it isn’t simultaneously being changed by one and used by the other. A memory “ownership” flag can be created and used for this purpose.

In addition to controlling access to shared memory, you are also responsible for maintaining cache coherency.

There are 3 ways to achieve this:

1) Completely disable cache

2) Enable cache but disable ability to cache shared data

3) Enable cache and manage cache coherency for shared data

© 2017 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.