public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Syed Ismail" <ismail.riyaz@dyansys.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Memory layout
Date: Thu, 10 Apr 2008 21:35:00 -0000	[thread overview]
Message-ID: <20080410190845.42817.qmail@pro-237-182.rediffmailpro.com> (raw)


Hello
 I have an arm based mx31 freescale processor. Using patches from freescale, i was able to create redboot image ang with minor configuration changes it worked. Now i have a few questions.

1. The image is a romram image. Loads from nor flash and executes in ram. The ram is an sdram at physical addr 0x80000000, virt addr mapped to 0x0. I now want use a ram at a different physical address. What changes do i do?

2. What does this do

X_ARM_MMU_SECTION(0x800, 0x000,   0x80,  ARM_CACHEABLE,   ARM_BUFFERABLE,   ARM_ACCESS_PERM_RW_RW); /* SDRAM */
    X_ARM_MMU_SECTION(0x800, 0x800,   0x80,  ARM_CACHEABLE,   ARM_BUFFERABLE,   ARM_ACCESS_PERM_RW_RW); /* SDRAM */
    
Should i add the new ram physical address here? What is ARM_CACHEABLE and BUFFERABLE? Does the above write into registers of processor or is it only a table used by redboot code?

3. As a general query, is it possible to load and execute images like redboot from a PSRAM.

Thanks

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2008-04-10 19:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 21:35 Syed Ismail [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-10-29 14:13 [ECOS] memory layout Syed Ismail
2007-10-29 14:18 ` Andrew Lunn
2003-10-08 14:29 [ECOS] Memory Layout James Yates
2003-09-18  7:31 [ECOS] Memory layout Matthieu.GIRARDIN
2002-11-18 19:44 [ECOS] memory layout AL Chane
2002-10-30  9:55 Schumacher, Gordon
2002-11-04 20:37 ` Jonathan Larmour
2002-10-30  1:09 AL Chane
2002-10-30  4:52 ` Chris Garry
2002-04-10 18:23 [ECOS] Memory layout Agarwal, Lomesh
2002-04-10 18:18 Agarwal, Lomesh
2002-04-11 18:03 ` Jonathan Larmour
2002-04-10 15:31 Agarwal, Lomesh
2002-04-10 17:39 ` Jonathan Larmour
2002-04-10 14:01 Agarwal, Lomesh
2002-04-10 15:22 ` Jonathan Larmour
2002-04-07 16:14 Agarwal, Lomesh
2002-04-10 13:51 ` Jonathan Larmour
2001-04-18  2:01 [ECOS] Memory Layout james chen
2001-04-18  5:24 ` Gary Thomas
2001-04-18 18:05   ` james chen
2001-04-19  5:12     ` Gary Thomas
2001-04-19 17:37       ` james chen
2001-04-19 17:48         ` Gary Thomas
2001-01-23 22:51 [ECOS] memory layout Natarajan, Mekala (CTS)
2001-01-23 23:46 ` Jesper Skov

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=20080410190845.42817.qmail@pro-237-182.rediffmailpro.com \
    --to=ismail.riyaz@dyansys.com \
    --cc=ecos-discuss@ecos.sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).