AnsweredAssumed Answered

l1_data_A always in l1_data_B

Question asked by daniele on Mar 22, 2013
Latest reply on Mar 25, 2013 by daniele

We're using uClinux 3.0.8-ADI-2011R1 on BF537 on a custom board.

 

We're developing in KernelSpace and, according to: http://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:on-chip_sram&s[]=l1&s[]=data

we're using

__attribute__ ((l1_data))

 

Now, data are put in SRAM L1 DATA B

 

But for our process, we need to allocate also in L1 DATA A

__attribute__ ((l1_data_A))

 

Nothing is put in L1 DATA A

 

This is the output from /proc/sram:

 

--- SRAM Scratchpad     Size   PID State    

ffb00008-ffb01000       4088     0 FREE     

--- SRAM L1 Data A      Size   PID State    

ff8018a0-ff804000      10080     0 FREE     

--- SRAM L1 Data B      Size   PID State    

ff900000-ff902f8c      12172    88 ALLOCATED

ff902f8c-ff908000      20596     0 FREE     

--- SRAM L1 Instruction Size   PID State    

ffa02ca8-ffa036a0       2552    88 ALLOCATED

ffa036a0-ffa0c000      35168     0 FREE 

 

This is the output from dmesg:

Blackfin L1 Data A SRAM: 16 KB (9 KB free)

Blackfin L1 Data B SRAM: 32 KB (32 KB free)

 

We set for Kernel DCache.

 

We tried both static and alloc without success.

 

Regards,

Daniele.

Outcomes