From: Marc Michalewicz <marc.michalewicz@pixy.ch>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] accessing external RAM on h8s edk
Date: Thu, 02 Jun 2005 09:03:00 -0000 [thread overview]
Message-ID: <1117702984.21830.21.camel@c29.pixybugs.dyndns.org> (raw)
Hi,
after getting redboot to work, I now have problems to access the
external RAM on my H8S2329-EDK board. The internal RAM is OK, e.g.
writing bytes into it via the redboot-cmdline works.
Has anybody a clue what needs to be done to access the external RAM ?
I adapted the H8S-2357 port (from Uwe Kindler) in the way that I have
changed the initialisation-code in the "platform.inc"-file (Bit EAE in
BCRL especially, but all othere REGS according to the EDK-documentation
as well), but still no success. If it helps, here is the modified
extract from my platform.inc:
INIT_REGS_DATA(CYGARC_ABWCR, 0xF0)
INIT_REGS_DATA(CYGARC_ASTCR, 0xFF)
INIT_REGS_DATA(CYGARC_BCRH, 0xD0)
INIT_REGS_DATA(CYGARC_BCRL, 0x3C)
INIT_REGS_DATA(CYGARC_WCRH, 0xFF)
INIT_REGS_DATA(CYGARC_WCRL, 0xFD)
INIT_REGS_DATA(CYGARC_MCR, 0x00)
INIT_REGS_DATA(CYGARC_DRAMCR, 0x00)
INIT_REGS_DATA(CYGARC_RTCOR, 0x00)
INIT_REGS_DATA(CYGARC_P6DDR, 0x00)
INIT_REGS_DATA(CYGARC_PADDR, 0x07)
INIT_REGS_DATA(CYGARC_PBDDR, 0xFF)
INIT_REGS_DATA(CYGARC_PCDDR, 0xFF)
INIT_REGS_DATA(CYGARC_PFDDR, 0x80)
INIT_REGS_DATA(CYGARC_PGDDR, 0x01)
INIT_REGS_DATA(CYGARC_MSTPCRL,0x00)
Do I have to modify the linkerscripts and/or other items ? Is there any
hint in any documentation ?
Thanks for any help,
Marc
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-06-02 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 9:03 Marc Michalewicz [this message]
2005-06-02 9:57 ` Marc Michalewicz
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=1117702984.21830.21.camel@c29.pixybugs.dyndns.org \
--to=marc.michalewicz@pixy.ch \
--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).