From: Sergey Temerkhanov <temerkhanov@yandex.ru>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Instruction OCM
Date: Mon, 19 May 2008 22:53:22 +0400 [thread overview]
Message-ID: <4831CCA2.6000107@yandex.ru> (raw)
In-Reply-To: <012401c8b9c3$74b947c0$5e2bd740$@com>
mojtaba wrote:
>
> 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
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Address 0x700 means invalid opcode exception.
If instruction OCM is same as data OCM (I think it's so) then any MMU
mapping is not applicable to this region at all as OCM controller
decodes virtual addresses bypassing any MMU mappings.
In your situation MMU maps virtual address of OCM to physical address
containing some random data and CPU tries to execute it. So you get
invalid opcode exception.
next prev parent reply other threads:[~2008-05-19 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 15:17 Instruction OCM mojtaba
2008-05-19 16:58 ` Stephen Neuendorffer
2008-05-20 8:31 ` mojtaba
2008-05-19 17:59 ` Koss, Mike (Mission Systems)
2008-05-19 18:53 ` Sergey Temerkhanov [this message]
2008-05-20 9:19 ` mojtaba
2008-05-20 11:11 ` Temerkhanov
2008-05-20 21:26 ` Stephen Neuendorffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4831CCA2.6000107@yandex.ru \
--to=temerkhanov@yandex.ru \
--cc=linuxppc-embedded@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.