public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001429] LPC1766-STK "address 0x10008d9c of */redboot.elf section .bss is not within region ram"
Date: Thu, 22 Dec 2011 06:02:00 -0000 [thread overview]
Message-ID: <20111222060110.A1F2E2F7800E@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001429-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001429
--- Comment #2 from scott <hbyu.1986@gmail.com> 2011-12-22 06:01:04 GMT ---
(In reply to comment #1)
> LPC 1766 has small RAM resources. In addition, RAM being fragmented in two
> blocks makes it even more difficult. You could try to decrease some memory
> demand (buffers, etc) but I'm afraid that RAM is too low to run Redboot with
> networking.
>
> I hope this helps.
> Ilija
Thanks for Ilija's reply. I understands that.
Do you have some example to test Ethernet without redboot?
Or how can I test the Ethernet without redboot?
Thanks for your help.
Hailee
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-12-22 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 13:45 [Bug 1001429] New: " bugzilla-daemon
2011-12-21 16:10 ` [Bug 1001429] " bugzilla-daemon
2011-12-22 6:02 ` bugzilla-daemon [this message]
2011-12-22 7:45 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-12-21 13:45 [Bug 1001429] New: " bugzilla-daemon
2011-12-21 16:10 ` [Bug 1001429] " bugzilla-daemon
2011-12-22 6:02 ` bugzilla-daemon
2011-12-22 7:45 ` bugzilla-daemon
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=20111222060110.A1F2E2F7800E@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@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).