Re: [lwip-users] Help with LwIP Modem

Hi Sylvian, I think I actually use tcpip_input but please correct me if I'm doing something wrong this is how I add the netif: // netif_add(&netif, &laddr, &netmask, &gw, 0, arm9emac_init, arm9emac_low_level_input); // netif_add(&netif, &laddr, &netmask, &gw, 0, arm9emac_init, ethernet_input); n

Re: [lwip-users] Help with LwIP Modem

Thanks Sylvain I will try today with tcpip_input and move to use the raw api. Thanks. Sent from my iPhone > On Jul 7, 2016, at 14:35, Sylvain Rochet wrote: > > Hi Jaime, > >> On Thu, Jul 07, 2016 at 02:21:22PM -0500, Jaime Fernández wrote: >> >> Can the raw api be used with an OS or is it e

Re: [lwip-users] Help with LwIP Modem

Hi Jaime, On Thu, Jul 07, 2016 at 02:21:22PM -0500, Jaime Fernández wrote: > > Can the raw api be used with an OS or is it exclusively for none os > implementations ? That's properly documented inside lwip/doc/rawapi.txt AFAIK. It can be used, but all raw API calls must be from the TCPIP threa

Re: [lwip-users] Help with LwIP Modem

Hi Jaime, On Thu, Jul 07, 2016 at 02:21:22PM -0500, Jaime Fernández wrote: > > Typo, I meant NO_SYS = 0. You can't use ethernet_input function with !NO_SYS, this function is not thread safe and part of the lwIP "raw" API, you have to use tcpip_input instead. Sylvain signature.asc Descriptio

Re: [lwip-users] Help with LwIP Modem

Typo, I meant NO_SYS = 0. I think this is an issue with my eMac Config not lwip. I'm going to try the enet echo for the omapl138, which is part of the TI starterware. My expectation is that the eMac RX callback or interrupt should break with broadcast packets or for example if I ping the devic

Re: [lwip-users] Help with LwIP Modem

Hi, On Wed, Jul 06, 2016 at 02:01:26PM -0500, Jaime Fernández wrote: > > NO_SYS = 1, I'm using TI sysbios kernel. > My laptop NIC is configured to ip= 192.168.10.1, sm = 255.255.255.0, > gw= empty. My board netif is configure to ip=192.168.10.3, same subnet > and gw=192.168.10.1. > > I have n

[lwip-users] Assertion "unsent_oversize mismatch (pcb vs., last_unsent)"

Hallo Simon, I think now this error is caused by the driver. (See also my last question: "Problem with blackfin port") I did a change in this driver and the assertion didn't occur anymore. In the driver there was a command that caused a MEMP_POOL malloc for RX buffers in the TX-callback func

[lwip-users] Sending large files over netconn and TCP

Hello, I have a website on LwIP with list of files with possibility to download them. I'm using function: #define BUFFER_OUT16000 static BYTE archDownBuffer[BUFFER_OUT] __attribute__ ((section(".sdram"))); char archive_page[WEBSITE_BUFFER] __attribute__ ((section(".sdram"))); st

Re: [lwip-users] Assertion "unsent_oversize mismatch (pcb vs. last_unsent)"

Sandra Gilge wrote: > Hallo, Hello :-)   > Now I’m getting at heavy load the following assertion: > Assertion "unsent_oversize mismatch (pcb vs. last_unsent)" failed at line 465 > in .\src\core\tcp_out.c > [..] > Anyone an idea? Unfortunately no. Can you be absolutely sure you (or the port) don'

[lwip-users] Problem with Blackfin Port

Hallo, I'm not shure if this is the right address to ask about lwip ports. I struggling with the Blackfin port that I found in the lwip WIKI, so I had a closer look at the code and found following line in the function bfemac_tx_callback(): bfemac_alloc_rxfreequeue(); (line 381) I'm not