Arm Cortex: L1 cache Write-through

28-Nov-2024

In general, for a real-time observation of the variables these must be written in the data memory and not, for example, only held in the cache, since cache memory is not visible to the debugger. If you want the "cached only" variables to be seen by the debugger, you will need an EVE script or an INI file to enable L1 Cache Write-through. This configures the microcontroller to propagate writes of variables cached in the L1 cache also to the memory.

The debugger has no access to the contents of the cache memory, the only way to observe its contents by debugger is by forcing it to write through any changes directly from the cache memory to the SRAM locations, which are accessible by the debugger.

The example below shows how the debugger sees variables in the memory:

Without Write-through

With Write-through

Cache value
Memory value
Cache value
Memory value
0x00000000
0x000000E7
0x00000000
0x00000000
0x00000001
0x000000E7
0x00000001
0x00000001
0x00000002
0x000000E7
0x00000002
0x00000002


Solutions

Provided EVE script (Cypress Traveo II)

This solution is specific to Cypress Traveo II devices. You can use the provided EVE script to enable L1 Cache Write-through. The script sets the FORCEWT bit of the CM7_CACR register. 

Execute Hardware | Scripts | Enable CacheWriteThrough




The effect of the script is reset if the microcontroller goes through any kind of a reset and the variables being cached only will no longer be visible in the real-time Watch Window.



Custom INI file (Any Cortex M7 device)

1. Create an Enable_L1_Cache_WriteThrough.ini file and copy it into your winIDEA Workspace folder. The content of the INI file should be:

A CACR L 4 // set FORCEWT

2. Go to Hardware | CPU Options | Reset |  Initialization before programming | Initialize.

3. Select Custom in the dropdown menu.

4. Click on the arrow button and select the Default initialization file, or copy and paste the file name into the Scripts field.

5. Click the arrow button to return to the menu. Select Add from workspace folder and select the INI file.




6. Go back to Hardware | CPU Options | Reset and carry out the following:

  • Disable Reset CPU after download (Invalidates initialization), otherwise  Cache Write-through will be invalidated.
  • Enable Initialization before Debug session | Initialize | Same as Programming
  • Enable Initialization at Attach | Initialize | Same as Debug



More resources in winIDEA Help


    Was this answer helpful?