[U-Boot] Run a standalone application on a core other than 0

[Scott Wood]

On 07/08/2013 12:22:03 PM, João Fernandes wrote:
> Thank you Scott. On a somehow related question, when I use "cpu X  
> release"
> to run some code on a core other than 0, the changes to memory made  
> by cpu
> X are not made visible globally. I believe this is connected with  
> WIMGE
> bits - as soon as disable L1 and L2 it works fine - am I correct? If  
> so,
> does core 0 have 0x00000000 - 0x3FFFFFFF and 0x40000000 - 0x7FFFFFFF  
> TLB
> entries marked as cache coherent, or do I also have to set them for  
> it?

You need to set the M bit in all TLB entries that reference memory that  
is shared.  U-Boot already does this, but perhaps the code you're  
running on the secondary CPU does not?  Is U-Boot still running on core  
0 at that point?

Also be sure you're using the proper memory barriers to ensure that  
changes are seen in the right order.

-Scott