From: John Dallaway <john@dallaway.org.uk>
To: Valentin BOUSSON <ml-ecos@belphegor.eu>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: STM32F4 Discovery + LwIP
Date: Tue, 25 Mar 2014 10:04:00 -0000 [thread overview]
Message-ID: <53315497.4040903@dallaway.org.uk> (raw)
In-Reply-To: <53313DCE.8030104@belphegor.eu>
Hi Valentin
On 25/03/14 08:26, Valentin BOUSSON wrote:
> Today, I have a problem to set up *LwIP* on my *STM32F4DISCOVERY* with
> the standard extension board.
> (http://www.st.com/web/catalog/tools/FM146/CL1984/SC720/SS1462/PF255417)
>
> I tried a lot of thing, as using the default configuration for eCos,
> adding packages "Ethernet common drivers" and "LwIP stack". No confilct
> appears, but an the stack doesn't seem to work at all.
At minimum, you will need to add the CYGPKG_DEVS_ETH_PHY and
CYGPKG_DEVS_ETH_CORTEXM_STM32 hardware packages to the
"stm32f4discovery" target description record in packages/ecos.db.
Actually, it would be preferable to create a new target description
record for STM32F4-Discovery with STM32F4DIS-EXT.
You might also be necessary to modify the the hal_system_init() function
in the STM32F4-Discovery platform HAL to setup the ethernet hardware.
Compare with the hal_system_init() function from the STM32x0G platform HAL.
With these changes in place, you should be able to create a new eCos
configuration for lwIP based on the eCos "lwip_eth" packages template.
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:[~2014-03-25 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 8:28 [ECOS] " Valentin BOUSSON
2014-03-25 10:04 ` John Dallaway [this message]
[not found] ` <CABmKEG8rHJqwf_PQp1ZH9e=fgwbK4hFOWJhv1SqaO6nBWQh1tA@mail.gmail.com>
2014-03-25 12:34 ` [ECOS] " Jerzy Dyrda
2014-03-25 15:25 ` John Dallaway
2014-03-25 18:32 ` Jerzy Dyrda
2014-04-08 12:37 ` Valentin BOUSSON
[not found] ` <53466671.3050304@bousson.com>
[not found] ` <CABmKEG-1LBOsLy+44rCQrmFhmEVyKJffxJ3uscF6uSGGkUW7mg@mail.gmail.com>
2014-04-10 13:20 ` Valentin BOUSSON
[not found] ` <CABmKEG_ONPDk26UXzXxPLd==DDKMe7eGdX3FGWABgiffh_wGjQ@mail.gmail.com>
2014-04-11 15:00 ` Valentin BOUSSON
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=53315497.4040903@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=ml-ecos@belphegor.eu \
/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).