Actually there is no overlapping between IOCM and DDR. The IOCM region addre4sses are: PARAMETER C_BASEADDR = 0xc0a00000 PARAMETER C_HIGHADDR = 0xc0a1ffff And the DDR addresses are: PARAMETER C_MEM0_BASEADDR = 0x00000000 PARAMETER C_MEM0_HIGHADDR = 0x0fffffff Furthermore, if such a conflict existed, the synthesizer would have identified it.
-----Original Message----- From: Stephen Neuendorffer [mailto:[EMAIL PROTECTED] Sent: Monday, May 19, 2008 6:59 PM To: mojtaba; linuxppc-embedded@ozlabs.org Subject: RE: Instruction OCM The traps are down there in low memory. trap 700 is probably the one that deals with MMU exceptions. My guess is your OCM region is overlapping with the DDR memory containing that code. Steve > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:linuxppc-embedded- > [EMAIL PROTECTED] On Behalf Of mojtaba > Sent: Monday, May 19, 2008 8:17 AM > To: linuxppc-embedded@ozlabs.org > Subject: Instruction OCM > > Dear all, > > I cannot run Linux when I have an instruction OCM in my design but, without instruction OCM > everything is fine. I tried to do some debugging. It seems that the Linux memory management unit has > a problem with that. After entering the MMU initialization phase, it suddenly jumps to address > 0x00000700 it get stuck there. Is there anybody who have tried a design with instruction OCM? Do I > need to do special configuration for the Linux kernel? > > Regards, > > Mojtaba This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
