• Locked Locked
  • Replies 3 replies
  • Subscribers 119 subscribers
  • Views 2870 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Strange behaviour of cache

qwerty ytrewq
Note: This was originally posted on 19th November 2011 at http://forums.arm.com

Hi!

I have a Cortex a9 based board (currently only 1core is active another one is waiting for its time to come into a play).
My simplified caching routine in pseudo code looks like this:

Cache(set of parameters){
if(cache_op1)docache_op1();
if(cache_op2)docache_op2();
....
if(cache_opn)docache_opn();
}
An example of cache operation:
     mov  r0, #0
     mcr  p15, 0, r0, c7, c5, 0    ; I cache
     mcr  p15, 0, r0, c7, c5, 6    ; BP
     DSB
     ISB
     bx   lr

The system hangs at some point...
But when I include a delay (several thousands of CPU cycles) it gets stable and works just fine:
Cache(set of parameters){
if(cache_op1)docache_op1();
if(cache_op2)docache_op2();
....
if(cache_opn)docache_opn();
Delay();
}
Disabling/enabling L2 cache doesn't seem to affect the system. So I think it is related to L1 cache.

Having delay in this function isn't acceptable because of performance  issues and frankly speaking I don't know how long it should be delayed  for in every particular case.
I suspect that some caching operations need time to complete. Is there a  mechanism in ARM to ensure that caching operation is complete? I  thought it was done by using the DSB instruction... But it is either  ignored or used for a completely different purpose. If there is no such  mechanism then how should it be handled? I mean if the program continues  to execute while hardware operation is not finished. Otherwise I cannot  explain my workaround with delay.  Any ideas are welcome.

Thanks
Parents
  • Note: This was originally posted on 22nd November 2011 at http://forums.arm.com

    Can you explain more why "It is not possible to separate caching functions from each other"? From my perspective:
    {
    if(cache_op1) {docache_op1(); delay();}
    if(cache_op2)docache_op2();
    }
    It this works fine, then change it to
    {
    if(cache_op1)docache_op1();
    if(cache_op2) {docache_op2(); delay()}
    }
    If this does not work ,then you can know that docache_op2() is probably the reason to cause the problem and then focus on it.

    It may not be the reason to cause your problem here, but when you perform some operations such as "invalidate/flush/clear all I-Cache D-Cache", I'd suggest you lock all the interrupts.
Reply
  • Note: This was originally posted on 22nd November 2011 at http://forums.arm.com

    Can you explain more why "It is not possible to separate caching functions from each other"? From my perspective:
    {
    if(cache_op1) {docache_op1(); delay();}
    if(cache_op2)docache_op2();
    }
    It this works fine, then change it to
    {
    if(cache_op1)docache_op1();
    if(cache_op2) {docache_op2(); delay()}
    }
    If this does not work ,then you can know that docache_op2() is probably the reason to cause the problem and then focus on it.

    It may not be the reason to cause your problem here, but when you perform some operations such as "invalidate/flush/clear all I-Cache D-Cache", I'd suggest you lock all the interrupts.
Children
No data