[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] Using different start address for System. map
On Mon, Nov 16, 2009 at 6:21 PM, Naser Khosro Pour
> But the problem is that these processors use a shared memory and should have access to whole memory. The only thing is that I want that their images start from different addresses (ex: 0x3000 0000 for Microblaze_0 and 0x3100 0000 for Microblaze_1) while the memory of both is 0x3000 0000-0x3FFF FFFF!
Paulo's answer is correct - use the PARAMETER
MAIN_MEM_START=0x31000000 on the second instance
You have to give each Linux system its own private memory space,
otherwise chaos will result. Because it's not true SMP, the kernels
will be completely independent, and must have total control over their
own memory space.
If you want some of the memory to be shared, you'll need some special
tricks (or most likely, hacks) to achieve that - it's not a
functionality that the Linux kernel will help you with.
The simplest and least portable way will be to hard-code some pointer
offset into your application code, and devise your own scheme for
handshaking and synchronisation around access to that region.
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663 f: +61-7-30090663
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/