Problem with LwIP and MicroBlaze

I am trying to make a webserver on my ML401 development card and I use BSB to generate my hardware.

When I try to "Generate libraries and BSPs" I get the error: //////////////////////////////////// ERROR:MDT - ERROR FROM TCL:- lwip () - child process exited abnormally while executing "exec bash -c "cd src;make all \"COMPILER_FLAGS=$compiler_flags\" \"EXTRA_COMPILER_FLAGS=$extra_compiler_flags\" >& logs"" (procedure "::sw_lwip_v2_00_a::execs_generate" line 51) invoked from within "::sw_lwip_v2_00_a::execs_generate 40121220" //////////////////////////////////////

My version on EDK is 8.101 and ISE is 8.102

My Ethernet component looks like this in my MHS FILE: ///////////////////////////////// BEGIN opb_ethernet PARAMETER INSTANCE = Ethernet_MAC PARAMETER HW_VER = 1.02.a PARAMETER C_DMA_PRESENT = 1 PARAMETER C_IPIF_RDFIFO_DEPTH = 32768 PARAMETER C_IPIF_WRFIFO_DEPTH = 32768 PARAMETER C_OPB_CLK_PERIOD_PS = 10000 PARAMETER C_BASEADDR = 0x40c00000 PARAMETER C_HIGHADDR = 0x40c0ffff BUS_INTERFACE SOPB = mb_opb PORT OPB_Clk = sys_clk_s PORT PHY_rst_n = fpga_0_Ethernet_MAC_PHY_rst_n PORT PHY_crs = fpga_0_Ethernet_MAC_PHY_crs PORT PHY_col = fpga_0_Ethernet_MAC_PHY_col PORT PHY_tx_data = fpga_0_Ethernet_MAC_PHY_tx_data PORT PHY_tx_en = fpga_0_Ethernet_MAC_PHY_tx_en PORT PHY_tx_clk = fpga_0_Ethernet_MAC_PHY_tx_clk PORT PHY_tx_er = fpga_0_Ethernet_MAC_PHY_tx_er PORT PHY_rx_er = fpga_0_Ethernet_MAC_PHY_rx_er PORT PHY_rx_clk = fpga_0_Ethernet_MAC_PHY_rx_clk PORT PHY_dv = fpga_0_Ethernet_MAC_PHY_dv PORT PHY_rx_data = fpga_0_Ethernet_MAC_PHY_rx_data PORT PHY_Mii_clk = fpga_0_Ethernet_MAC_PHY_Mii_clk PORT PHY_Mii_data = fpga_0_Ethernet_MAC_PHY_Mii_data END ///////////////////////////////////////////////

Is there anyone that can have an idea what might be the problem?

Raymond

Reply to
Raymond
Loading thread data ...

It should be a path trouble. The compiler doesn't find the files. I had it in a custom version of lwip: 1.01.a But if you use lwip 2.00.a with eternet or ethernet lite core it should not appear. Check lwip configuration into:

Software Platform Setting OS and Libraries expand lwip tree

Marco

Reply to
Marco T.

Hi Marco.

And thanks for answering :)

I can't find any path options here? (It maybe that I overlook something). What should I look for in the configuration settings?

Is it possible to download a new version of LwIP (like a custom LwIP) and use that in stead? By the way, I use lwip 2.00.a

Raymond

Reply to
Raymond

There aren't newer version of lwip. I use a custom version because ll_temac is not supported by xilinx official version 1.00.a and 2.00.a.

Which ethernet core are you using? Ethernet and ethernet lite cores are fully supported.

In any case it seems a configuration trouble. Check if you have configured every parameter into: Software Platform Setting -> OS and Libraries -> lwip tree (expand it) You can compare all parameters into oslib_rm.pdf

If you environment varaible Xilinx_EDK is set to C:\EDK try changing it to C:\EDK\

Marco

Reply to
Marco T.

Hi Marco.

I tought that I could use LwIP without any OS. Think I have read that someplace but could not find it again now. I don't know yet what the error is, but it might be that LwIP needs the xilkernel (I don't know yet). I have some interrupt in my work now and I am going to have to take up the thread again in the next week.

Do you know if the LwIP needs an OS of any kind (as spoken, I thought that it supported OSless systems). My system is now without OS. If it needs an OS I will maybe consider Linux instead of xilkernel.

Raymond

Reply to
Raymond

I'm sure it can run stand alone. If you go to

formatting link
and then to the design resource center there is an example application under the Xilinx v4fx12 mini-module called something TEMAC example. It is an embedded webserver that is run from scratch on top of lwip. I've just tried it today on my evm.

-Clark

Reply to
Anonymous

Hi

This example (xapp807) don't use the LwIP stack. It use the uIP stack, free also.

Reply to
David

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.