Thank Simon,
Yes, there are more changes in sockets.c, and the similar event handler
should be added in my_callback. I mean, that LWIP_ASSERT can be ignore.
Maybe I can provide the modification later, thanks.
Best Regards,
Bernard Xiong
2017-02-16 4:01 GMT+08:00 goldsi...@gmx.de <gol
ack;
however, there is a ASSERT to check the callback in lwip_accept function:
LWIP_ASSERT("newconn->callback == event_callback", newconn->callback
== event_callback);
In the next lwIP version, can it be removed from lwip_accept? thanks.
Best Regards,
Bernard Xiong
http://www.r
oh,
I will communicate with authors in historical version to fix license issue.
Thanks.
2016-11-19 22:56 GMT+08:00 sg :
> How does its GPL licnese fit with lwips BSD license?
>
> Simom
> cont...@rickeyworld.info wrote:
>>
>> Hi All,
>>
>>
>>
>> This
to tell the different version:
#if ( (LWIP_VERSION) < ((2U << 24) | (0U << 16) | (0U << 8) |
(LWIP_VERSION_RC)) )
...
#endif
And the lwIP 2.0.0 RC2 version is OK. Any update? Thank you.
Best Regards,
Bernard Xiong
___
lwip-users ma
Hi Dimax,
It seem the DHCP server respond with DHCP_NAK. You can use wireshark
to analyze packet.
Regards,
Bernard Xiong
2015-05-19 14:04 GMT+08:00 Dimax dimax.m...@gmail.com:
Hi,
I faced a problem with DHCP client in lwip 1.4.1 with one specific
router (not sure what exactly it's type
Hi Abdallah,
You can use BSD socket interface to make a TCP or UDP server. This is my
code for TCP server, but with Chinese comments:
https://github.com/RT-Thread/rt-thread/blob/master/examples/network/tcpserver.c
Regards,
Bernard Xiong
2015-05-18 23:34 GMT+08:00 Abdallah Aguerzame
Hi Simon,
What's these changes on IPv6? Is there some change wish list for lwIP
1.5.0? Thanks.
Best Regards,
Bernard Xiong
2015-05-08 20:36 GMT+08:00 Simon Goldschmidt goldsi...@gmx.de:
Sergio R. Caprile wrote:
The current git head has many bug fixes, no new experimental stuff
afaik
implementation in RT-Thread
RTOS:
https://github.com/RT-Thread/rt-thread/tree/master/components/net/lwip_nat
Best Regards,
Bernard Xiong
2015-05-09 12:00 GMT+08:00 Eason u9411...@gmail.com:
Hi Simon, I have some questions.
I add the second interface(struct netif* xnetif_1) by using
netif_add
planning to improve it because we should use it in our Wi-Fi start kit
board. Thanks.
Best Regards,
Bernard Xiong
2015-02-05 0:20 GMT+08:00 Simon Goldschmidt goldsi...@gmx.de:
Sylvain Rochet wrote:
lwIP does not have NAT support, there was a task about it but it didn't
materialise.
I
lwIP's, then submit it to
lwIP. Thanks.
BTW, we also port lwip-head to the RT-Thread RTOS for dual IPv4/v6 stack.
Welcome for testing too.
https://github.com/RT-Thread/rt-thread/tree/master/components/net/lwip-head
Best Regards,
Bernard Xiong
2015-02-05 20:43 GMT+08:00 Sylvain Rochet grada
as a network interface. However, this WiFi driver
has no WPA/WPA2 feature.
Best Regards,
Bernard Xiong
http://www.rt-thread.org
2013/12/12 Daniel Doron dan...@identytech.com
You can also check out www.connectone.com
Daniel.
-Original Message-
From: lwip-users-bounces+daniel
You can compare the format of packet between lwIP and packet generator.
2013/12/12 Fu Chiao Chang zector1...@gmail.com
I use lwip-1.4.1 on stm32f407.
When the lwip sends a UDP packet bigger than MTU, wireshark receives a
smaller UDP packet and a Fragmented IP Protocol packet.
But my
lwIP supports this feature if you enable:
IP_FRAG: Fragment outgoing IP packets if their size exceeds MTU.
IP_REASSEMBLY: Reassemble incoming fragmented IP packets.
2013/10/20 xunqinglai mrmousta...@163.com
hi, guys, it is said in Design and Implementation of the lwIP TCP/IP
Stack that lwip
We define two macro:
#define netifapi_netif_set_link_up(netif) netifapi_netif_common(netif,
netif_set_link_up, NULL)
#define netifapi_netif_set_link_down(netif)netifapi_netif_common(netif,
netif_set_link_down, NULL)
And then call it in any thread but not in ISR.
Regards,
Bernard Xiong
Hi Dimax,
The driver is almost the same as the driver in lwIP 1.3.2, 1.4.0, 1.4.1 ...
Regards,
Bernard Xiong
~~
RT-Thread - An open source RTOS from China.
https://github.com/RT-Thread/rt-thread
http://www.rt-thread.org
~~
2013
Thank you very much.
We will porting it to RT-Thread as soon as possible.
BTW, which version the IPv6 feature will be enable officially?
Best Regards,
Bernard Xiong
2012/12/18 Simon Goldschmidt goldsi...@gmx.de
Hi all,
Nearly three months after tagging the git repositories for the 1.4.1
applications. There are also a WIFI shield, therefore, lwIP will be
used in ART board.
Regards,
Bernard Xiong
~~
RT-Thread - An open source RTOS from China.
http://en.rt-thread.org
http://www.rt-thread.org
~~
2012/5/24 Sylvain Rochet
Hi Sylvain,
I'm a developer of RT-Thread RTOS. The application can be executed by
rt_module_open(app.mo) function.
The ART board (https://github.com/RTGUI/ART) will use this mechanism
to execute multi-arduino programs.
Regards,
Bernard Xiong
~~
RT-Thread
BSD socket
APIs.
NOTE: RT-Thread Application will be dynamic linked when running.
Thank you.
Regards,
Bernard Xiong
~~
RT-Thread - An open source RTOS from China.
http://en.rt-thread.org
http://www.rt-thread.org
~~
2012/5/24
= (u32)ETH_DMA_IT_RBU;
}
if ((status ETH_DMA_IT_TBU) != (u32)RESET)
{
ETH_ResumeDMATransmission();
ETH-DMASR = (u32)ETH_DMA_IT_TBU;
}
...
}
Regards,
Bernard Xiong
~~
RT-Thread - An open source RTOS from China.
http://en.rt
AM, Kieran Mansley kie...@recoil.org wrote:
On 28 Jan 2012, at 19:15, Sylvain Bernard wrote:
I've seen a couple old posts on a similar issue but no mentions on a
possible cause/resolution. Any idea?
note: the lwip stack is running in a single-threaded environment (no OS)
The normal
Hi all, I've got a system running a connection-less tcp client which
periodically opens/sends/closes some telemetry to a backend.
On occasion, when a connection failure occurs (link/server is down), the
following open connection that succeeds (server/link is back online) will
result in its tcb
On Sun, Mar 13, 2011 at 7:21 AM, Simon Goldschmidt goldsi...@gmx.de wrote:
Kieran Mansley kie...@recoil.org wrote:
Note that this includes the driver clashing with the rest of the stack
when it passes up a received packet; it should be calling netif-input()
(and this should probably be set
I am trying to debug a tcp error I have with lwip, I have attached a log of
the errors created when
I turn on the TCP_RST_DEBUG debug zone.
These errors occur when serving up a web page ( the 1st few seconds of
loading the page seem fine in Wireshark, but then I get these reset errors
..)
Can
Hi Kieran,
Replies in-line below.
Just to be sure: which end is running lwIP? I think it's 192.168.0.100
(the http server)
That is correct.
A few things:
- everything looks mostly fine for the first 10 seconds or so of the
trace.
- then I can see the server making increasing
If you're finding the debugging too slow, you could just turn on the
LWIP_STATS code, and then after loading your page get your device to print
out the totals. This should show which resources are running out allowing
you to fine tune it without the overhead of frequent printfs slowing
think?
Cheers,
Bernie
On Fri, Mar 4, 2011 at 10:42 AM, Bernard Mentink bment...@gmail.com wrote:
If you're finding the debugging too slow, you could just turn on the
LWIP_STATS code, and then after loading your page get your device to print
out the totals. This should show which resources
a part ..
PS: I am not complaining ... just confused, as a newcomer, I just can't find
anything ... it's all over the place.
Cheer,
Bernie
On Fri, Mar 4, 2011 at 6:39 PM, Simon Goldschmidt goldsi...@gmx.de wrote:
Bernard Mentink bment...@gmail.com wrote:
I's ok, found it ... (again
of these
--
With debugging turned on, the page won't load at all, so it looks like my
debugging is interferring with the stack ..
Anyone have any other suggestions?
Cheers,
Bernie
On Tue, Mar 1, 2011 at 10:14 PM, Kieran Mansley kie...@recoil.org wrote:
On Tue, 2011-03-01 at 11:11 +1300, Bernard Mentink wrote
a quick howto going from 1.3.2 to 1.4.0 would be great ..
Cheers,
Bernie
On Tue, Mar 1, 2011 at 6:54 PM, Simon Goldschmidt goldsi...@gmx.de wrote:
Bernard Mentink bment...@gmail.com wrote:
I am trying to upgrade from version 1.3.2 to version 1.4.0. I notice
quite a difference around the timers
Hi All,
I have just ported lwIP to LPC17xx processor family combined with the QP OS.
What I have tested is UDP and ping works. To test TCP I have included a web
server. The page sort of loads, but very slowly and doesn't finish .. also
after
the webpage action, pings and UDP no longer work ...
Hi There,
I am trying to upgrade from version 1.3.2 to version 1.4.0. I notice quite a
difference around the timers, is there any documentation on how to implement
the timers for the new version?
In the older version (I am using NO_SYS=1) I periodically called tcp_tmr()
etharp_tmr() etc from my
, 2011 at 6:54 PM, Simon Goldschmidt goldsi...@gmx.de wrote:
Bernard Mentink bment...@gmail.com wrote:
I am trying to upgrade from version 1.3.2 to version 1.4.0. I notice
quite a difference around the timers, is there any documentation on how to
implement the timers for the new version
a
2nd time, the stack does not respond. I have to reset the lwIP uP to get
things working again.
Anyone know what might be the issue here ... it seems to be ARP specific now
Cheers,
Bernie
On Sat, Feb 19, 2011 at 9:47 AM, goldsi...@gmx.de goldsi...@gmx.de wrote:
Bernard Mentink wrote:
Yes
On Mon, Feb 21, 2011 at 10:13 AM, Bernard Mentink bment...@gmail.comwrote:
Hi there,
I have it mostly working now, except for one remaining issue.
From the 1st run of the lwIP stack when the stack receives an ARP request,
it handles it normally and I can send/receive data between lwIP
Hi Simon,
Yes, I am using DMA. Can you please elaborate on how to invalidate the cache
lines, I havn't had much to do with dma to date ..
Many Thanks,
Bernie
On Fri, Feb 18, 2011 at 7:12 PM, Simon Goldschmidt goldsi...@gmx.de wrote:
Bernard Mentink bment...@gmail.com wrote:
I have found
Hi All,
I have just ported the lwIP stack to the NXP LPC17xx family combined with QP
OS and have it mostly working except for ARP.
What works is:
1. udp_send(), udp_sendto() etc .. I han't tried tcp yet ..
2. I can ping the stack fine.
3. Receive sort of works .. explain shortly ..
To test, I
been replied to, that it takes
5..10 seconds for the receive callback to be called.
Any idea's
Cheers,
Bernie
On Fri, Feb 18, 2011 at 8:33 AM, Bernard Mentink bment...@gmail.com wrote:
Hi All,
I have just ported the lwIP stack to the NXP LPC17xx family combined with
QP OS and have it mostly
Hi all,
Does anyone have a port to this family of micros? I guess I am just wanting
the eth_driver.c and eth_driver.h files ...
Many Thanks,
Bernie
--
You always have believers and scepticts.. A True inventor is always a
believer..
___
lwip-users
, Bernard Mentink wrote:
Hi all,
Does anyone have a port to this family of micros? I guess I am just
wanting the eth_driver.c and eth_driver.h files ...
Many Thanks,
Bernie
--
You always have believers and scepticts.. A True inventor is always a
believer
.
Regards,
Richard.
+ http://www.FreeRTOS.org
Designed for Microcontrollers. More than 7000 downloads per month.
+ http://www.SafeRTOS.com
Certified by TÜV as meeting the requirements for safety related systems.
On 03/02/2011 20:57, Bernard Mentink wrote:
Hi There,
Yes, I do have uIP
41 matches
Mail list logo