From: mementux <mementux@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Illegal memory access
Date: Wed, 11 Feb 2009 20:48:00 -0000 [thread overview]
Message-ID: <2d14e2ca0902111248l903ae2bq3d2c8a67b60e11f4@mail.gmail.com> (raw)
Hi,
I've a problem loading Linux with RedBoot 2.04 [ROMRAM] on a Compex
device: when I try to execute the loaded ramdisk image I get an
"illegal memory access" error. This is the log:
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Red Hat certified release, version 2.04 - built 09:48:17, Jun 6 2007
Platform: WP18/WP188/WPM188/NP18 Development Platform (IXP4XX) BE
Copyright (C) 2000, 2001, 2002, 2003, 2004, 2007 Free Software Foundation, Inc.
RAM: 0x00000000-0x04000000, [0x0006c2b0-0x03fc1000] available
FLASH: 0x50000000 - 0x50800000, 64 blocks of 0x00020000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort
^C
RedBoot> ^C
RedBoot> load -r -b %{FREEMEMLO} openwrt-compex-2.6-zImage.mm
Using default protocol (TFTP)
Raw file loaded 0x0006c400-0x008641f3, assumed entry at 0x0006c400
RedBoot> exec
Using base address 0x0006c400 and length 0x007f7df4
** command abort - illegal memory access?
RedBoot>
If I load a smaller ramdisk image, then I can execute it correctly:
RedBoot> load -r -b %{FREEMEMLO} openwrt-compex-2.6-zImage.mm
Using default protocol (TFTP)
Raw file loaded 0x0006c400-0x00562acf, assumed entry at 0x0006c400
RedBoot> exec
Using base address 0x0006c400 and length 0x004f66d0
Uncompressing Linux.......................................................................................................................................................................................................
done, booting the kernel.
Linux version 2.6.19.2 (root@alberto-desktop) (gcc version 4.1.2) #5
Wed Feb 11 12:07:18 UTC 2009
CPU: XScale-IXP42x Family [690541c2] revision 2 (ARMv5TE), cr=000039ff
Machine: Compex WP18 / NP18A
Memory policy: ECC disabled, Data cache writeback
[... cut ...]
I think that the only difference is the size of the ramdisk images.
The first image is about 8 Mbyte big; the second image is instead 5
Mbyte big.
I successfully use the first ramdisk image on others IXP4xx-based
devices with RedBoot 2.01 [ROM]. Can it be RedBoot limit/bug? Or can
it be an hardware limit?
Have someone any suggestions?
Thanks in advance,
Albert.
--
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:[~2009-02-11 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2d14e2ca0902111248l903ae2bq3d2c8a67b60e11f4@mail.gmail.com \
--to=mementux@gmail.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).