Look up tables, Flash or SRAM?
Simply defining the table without a const keyword will cause the table to be copied from Flash to RAM when your program starts up; e.g.

const short ax [] = { 1, 2, 3, 4 };      // stays in Flash
short bx [] = { 5, 6, 7, 8 };            // starts in Flash, copied to RAM


You can verify this behavior with the following two lines of code:

bx[0] = ax[0];    // allowed, since you are modifying a RAM variable
ax[0] = bx[0];    // not allowed, ax is const 


I checked this out using the IAR compiler for the STM32F10 family.  I don't know what CCM is, sorry.

It's not uncommon for embedded programmers to define a large initialized table, forgetting the const keyword, and then wonder why they are running out of RAM.