public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Wolfram Kattanek <wolfram.kattanek@imms.de>
To: Sunny Chan <sysc97@doc.ic.ac.uk>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos: Increase the size of ROM available on AEB-1
Date: Tue, 27 Feb 2001 03:01:00 -0000	[thread overview]
Message-ID: <983271628.3a9b88cc5b49f@imp.imms.de> (raw)
In-Reply-To: <5.0.2.1.0.20010226194945.02361ed8@pop-ug.doc.ic.ac.uk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

> Hello,
> 
> I am trying to use eCos to build a fairly large application to be placed in 
> ROM - however the default memory map for AEB-1 is rather small (32k) - now 
> I am trying to increase the available ROM available for building the image 
> - which file should I change? I have looked at 
> platform/hal/arm/aeb/version/cdl/hal_arm_aeb.cdl, which points me to some 
> header file - however it say it is calculated - where does it calculate 
> from? Can anyone shed some light on it?

The cheapest and fastest solution would be using another 32k of the AEB flash
ROM which gives you a total of 64k flash (don´t know if that's enough for
"a fairly large application"). I have a AEB revision C where the memory area
between 0x4010000 and 0x4017fff is available (be sure to check this with the AEB
monitor command "rommodules"; otherwise some "side effects" could happen like
overwriting the AEB monitor or Angel). When using the standard memory map from
eCos only the area between 0x4018000 and 0x401ffff (=32k) is available. In order
to use the additional flash area you have to do the following:

In the files
   packages/hal/arm/aeb/current/include/pkgconf/mlt_arm_aebC_rom.ldi
   packages/hal/arm/aeb/current/include/pkgconf/mlt_arm_aebC_rom.h
you have to change ROM adresses from 0x4018000 to 0x4010000 and ROM length from
0x8000 to 0x10000.

In the file
   packages/hal/arm/aeb/current/include/plf_stub.h
you have to change the reset entry from 0x4018000 to 0x4010000.

After downloading your application image into RAM (monitor command "download
c000") you have to use the command "flashwrite 4010000 c000 10000".

Wolfram
--
Wolfram 'L.A.' Kattanek     Institut fuer Mikroelektronik- und
Email:       LA@imms.de     Mechatronik-Systeme (IMMS) gGmbH     
Tel: +49 3677 / 6783-55     Langewiesener Str. 22
Fax: +49 3677 / 6783-38     98693 Ilmenau / Germany

-------------------------------------------------
This mail sent through IMP: imp.imms.de

  parent reply	other threads:[~2001-02-27  3:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 11:49 Sunny Chan
2001-02-26 12:27 ` Jonathan Larmour
2001-02-27  3:01 ` Wolfram Kattanek [this message]
2001-03-02  9:54   ` Sunny Chan
2001-03-03  3:07     ` Wolfram Kattanek
2001-03-03  3:41       ` Sunny Chan
2001-03-03  3:52         ` Wolfram Kattanek

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=983271628.3a9b88cc5b49f@imp.imms.de \
    --to=wolfram.kattanek@imms.de \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=sysc97@doc.ic.ac.uk \
    /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).