From: Sunny Chan <sunny_chan@usa.net>
To: Wolfram Kattanek <wolfram.kattanek@imms.de>,
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: Fri, 02 Mar 2001 09:54:00 -0000 [thread overview]
Message-ID: <5.0.2.1.0.20010302174735.026285a8@pop.netaddress.com> (raw)
In-Reply-To: <983271628.3a9b88cc5b49f@imp.imms.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]
Hello Wolfram,
At 11:00 27/02/2001, Wolfram Kattanek wrote:
>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:
I just wondering: how come there is only extra 32k available? I thought AEB
rev C has 256K flash (0x4000000 - 0x403ffff), and the first 16K is not
available (for Angle and Bootstrap loader)? Is there something wrong with
the way eCos setup the memory map?
I need as much RAM/ROM as possible because I am trying to build a MP3
player with (possibly) a Bluetooth stack. We are trying to decode it on the
board, then play the decoded data through the PC's sound card. As a result
I need to put almost all the code onto the flash and use the RAM as scratch
pad/storage.
Right now I am trying to see whether I can "ROM" a "hello world" apps - to
see how to ROM an application.
>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".
Once I have flash the application onto the ROM, how would you run it? using
the "go" command?
+---------------------------+---------------------------------+
|Sunny Chan also Sunny Computer Laboratory |
|Computing (MEng) Year 4 | "Power of Computing is yours" |
|Imperial College, London | http://www.sunnycomputer.co.uk |
+-------------------------------------------------------------+
email: sunny_chan@usa.net ICQ UIN: 2110678 mobile: 07887 704088
next prev parent reply other threads:[~2001-03-02 9:54 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
2001-03-02 9:54 ` Sunny Chan [this message]
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=5.0.2.1.0.20010302174735.026285a8@pop.netaddress.com \
--to=sunny_chan@usa.net \
--cc=ecos-discuss@sources.redhat.com \
--cc=sysc97@doc.ic.ac.uk \
--cc=wolfram.kattanek@imms.de \
/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).