From: Elad Yosef <elad.yosef@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: pbuf_alloc failures with LwIP
Date: Sun, 17 Jun 2012 13:36:00 -0000 [thread overview]
Message-ID: <CAOFa9c2ji1ghADBu+eRyAUntbnVRhwc8oPhXA5mQUM6GK=PoEw@mail.gmail.com> (raw)
In-Reply-To: <4FDD9F6C.7030905@dallaway.org.uk>
Hi all,
The good news:
I have managed to build new image with the new packages specified.
The bad news:
I can't see the TCP + ETH threads in the threads list and fails to ping.
Can anyone guide me how to bring-up the LwIP properly?
Elad
On Sun, Jun 17, 2012 at 12:12 PM, John Dallaway <john@dallaway.org.uk> wrote:
> Hi Elad
>
> On 17/06/12 07:28, Elad Yosef wrote:
>
>> I'm using multiple threads in my application.
>> The SYS_ARCH_PROTECT is not enabled at all.
>> How do I enable it?
>> Is it enabled in the current CVS version?
>> Does the current LwIP in CVS is compatible with ecos-3.0? In yes I
>> would consider upgrading LwIP package only
>
> You should be able to use lwIP 1.3.2 from eCos CVS with your eCos 3.0
> release repository just by copying packages/io/eth/current/ and
> packages/net/lwip_tcpip/current/ into your eCos 3.0 repository. Any
> _new_ eCos configurations will then use the "current" versions of these
> packages rather than the "v3_0" versions. Any _previous_ eCos
> configurations will continue to use the "v3_0" packages.
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
--
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 prev parent reply other threads:[~2012-06-17 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 20:40 [ECOS] " Elad Yosef
2012-06-13 15:47 ` Michael O'Dowd
2012-06-14 4:43 ` Elad Yosef
2012-06-14 14:37 ` Michael O'Dowd
2012-06-17 6:28 ` Elad Yosef
2012-06-17 9:12 ` [ECOS] " John Dallaway
2012-06-17 13:36 ` Elad Yosef [this message]
2012-06-18 10:17 ` Michael O'Dowd
2012-06-17 14:25 ` Elad Yosef
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='CAOFa9c2ji1ghADBu+eRyAUntbnVRhwc8oPhXA5mQUM6GK=PoEw@mail.gmail.com' \
--to=elad.yosef@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.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).