public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "venice" <venice.uurg@gmail.com>
To: "ecos-discuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] AT91SAM7X256--flash can not Initialise?
Date: Wed, 19 Mar 2008 09:38:00 -0000	[thread overview]
Message-ID: <6DDC3BFA6AE245E7AA557DFF6AD4216E@veniceuurg> (raw)


--------------------------------------------------
From: "Andrew Lunn" <andrew@lunn.ch>
Sent: Tuesday, March 18, 2008 5:09 PM
To: "venice" <venice.tu@live.com>; "eCos Disuss"
<ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] the freebsd stack influence the program"hello world"?

>> The correct way to do this should be:
>>
>> ecosconfig new at91sam7xek lwip_eth
>>
>> However, the resulting tree then fails to build. There was a fix to
>> realloc a while ago which changed a memcpy to a memmove and how there
>> are undefined symbols. I need to look at this and work out why.
>
> ecosconfig new at91sam7xek lwip_eth
> ecosconfig add libc_string
> ecosconfig tree
>
> should work.
>
>       Andrew
>



Actually the building packages include packages begin with "ISO ..."  , so
the libc_string package is ready in the building packages and the conflicts
are just the same as before.

/ecos-d/ecos/ecos/packages/net/lwip_tcpip/current/cdl/lwip_net.cdl, package
CYGPKG_NET_LWIP: error
    Interface `CYGPKG_NET_STACK' cannot be loaded.
    The name is already in use.
/ecos-d/ecos/ecos/packages/net/lwip_tcpip/current/cdl/lwip_net.cdl, package
CYGPKG_NET_LWIP: error
    Interface `CYGPKG_NET_STACK_INET' cannot be loaded.
    The name is already in use.
/ecos-d/ecos/ecos/packages/net/lwip_tcpip/current/cdl/lwip_net.cdl, package
CYGPKG_NET_LWIP: error
    Interface `CYGPKG_NET_STACK_INET6' cannot be loaded.
    The name is already in use.

BTW: How much memory will the lwip stack take? The at91sam7x256 has only 64k
ram and I don't know whether it's suitable for some internet applications.
Maybe I will get another arm board to develop the product. Any suggestion is
welcome, thanks!

Regards,
Venice 


-- 
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:[~2008-03-19  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19  9:38 venice [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-12 10:10 venice
2008-03-12 10:24 ` Andrew Lunn
     [not found]   ` <6B6125D574D6450EA59CE4808655B339@veniceuurg>
2008-03-12 11:29     ` Andrew Lunn
2008-03-12 11:37       ` Gary Thomas
2008-03-12 11:55         ` Andrew Lunn
2008-03-12 12:07           ` Gary Thomas

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=6DDC3BFA6AE245E7AA557DFF6AD4216E@veniceuurg \
    --to=venice.uurg@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).