Hello Valentin, On Tuesday 25 of March 2014 10:04:07 John Dallaway wrote: > 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. And you have to add some pins configuration due to fact that STM32F4DISCOVERY board doesn't any network interface. In packages/hal/cortexm/stm32/stm32f4discovery/current/include/plf_io.h please add such lines: //============================================================================= // Custom Ethernet pin mappings #define CYGHWR_HAL_STM32_ETH_MII_TX_EN CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, 11, 11, PUSHPULL, NONE, AT_LEAST(50) ) #define CYGHWR_HAL_STM32_ETH_MII_TXD0 CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, 12, 11, PUSHPULL, NONE, AT_LEAST(50) ) #define CYGHWR_HAL_STM32_ETH_MII_TXD1 CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, 13, 11, PUSHPULL, NONE, AT_LEAST(50) ) In packages/devs/eth/phy/current/cdl/phy_eth_drivers.cdl add missing PHY chip: cdl_option CYGHWR_DEVS_ETH_PHY_LAN8720A { display "SMSC LAN8720A" flavor bool default_value 0 compile -library=libextras.a LAN8720A.c description " Include support for SMSC LAN8720A" } and finally add new PHY i.e LAN8720A.c into directory -> packages/devs/eth/phy/current/src if you will have additional problems please ask I have already brought up network interface on STM32F4DISCOVERY + DM-STF4BB (AFAIK this is original name of base board from Embest, now as I see it's called STM32F4DIS-BB). Best regards, jerzy 2014-03-25 13:30 GMT+01:00 Jerzy Dyrda : > Hello Valentin, > > > On Tuesday 25 of March 2014 10:04:07 John Dallaway wrote: > >> 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. > > > And you have to add some pins configuration due to fact that > STM32F4DISCOVERY board > > doesn't any network interface. > > > In packages/hal/cortexm/stm32/stm32f4discovery/current/include/plf_io.h > please add such lines: > > > //============================================================================= > > // Custom Ethernet pin mappings > > > #define CYGHWR_HAL_STM32_ETH_MII_TX_EN CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, > 11, 11, PUSHPULL, NONE, AT_LEAST(50) ) > > #define CYGHWR_HAL_STM32_ETH_MII_TXD0 CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, 12, > 11, PUSHPULL, NONE, AT_LEAST(50) ) > > #define CYGHWR_HAL_STM32_ETH_MII_TXD1 CYGHWR_HAL_STM32_PIN_ALTFN_OUT( B, 13, > 11, PUSHPULL, NONE, AT_LEAST(50) ) > > > In packages/devs/eth/phy/current/cdl/phy_eth_drivers.cdl add missing PHY > chip: > > > cdl_option CYGHWR_DEVS_ETH_PHY_LAN8720A { > > display "SMSC LAN8720A" > > flavor bool > > default_value 0 > > compile -library=libextras.a LAN8720A.c > > description " > > Include support for SMSC LAN8720A" > > } > > > and finally add new PHY i.e LAN8720A.c into directory -> > packages/devs/eth/phy/current/src > > > if you will have additional problems please ask I have already brought up > network interface on > > STM32F4DISCOVERY + DM-STF4BB (AFAIK this is original name of base board from > Embest, now > > as I see it's called STM32F4DIS-BB). > > > > Best regards, > > jerzy > > > > 2014-03-25 11:04 GMT+01:00 John Dallaway : > >> 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 >> >