Simon,
If I was not clear, my apologies... lots of RAM due to the use of SSL and not
LwIP
BR,
Noam.
From: lwip-users on behalf of
goldsi...@gmx.de
Sent: Wednesday, May 17, 2017 9:34 PM
To:
Werner Motz wrote:
Unfortunatelly I still have link errors and I cannot find a docu in the wiki
about it.
Link
DROP1264
ERR 1264
Search for "LINK_STATS_INC(link.drop);" in your project. That stats are
netif driver specific, we cannot help you there. It could just be
Werner Motz wrote:
Really (and not meant in an offensive way!), I'm with Dirk thinking you need
someone teaching you lessons on embedded programming. Or you need to pay
someone programming your devices if this is about devices you want to
sell...
---> Serious?
Yes! I can put bricks on bricks
Noam Weissman wrote:
First of all the code is still in development and secondly you need
lots of RAM.
That "lots of RAM" is a limitation of TLS, not a limitation of mbed TLS
or how lwIP uses it.
That code is still not finished though. And I have to come up with
RAM/ROM numbers once it is
Hi,
There is a base code for HTTPS in the Lwip master code that works with mbedTLS.
I have been in contact with Simon regarding this. Simon was very helpful but I
was not
able to use it.
First of all the code is still in development and secondly you need lots of RAM.
At some point I think it
Hi Sandeep,
Not directly. HTTPS means HTTP+SSL/TLS. SSL/TSL is what bring you the
encryption on top of TCP/IP and bellow HTTP. I think this is out of scope of
LwIP, the LwIP source does not enable this. But you can use some SSL/TSL
library together with lwIP to build HTTPS applications. I have
Hi all,
Does lwip support HTTPS?
Is there any example HTTPS webserver application available? I saw an HTTP
webserver example.
Thanks
Sandeep
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Hello,
by changing MEM_SIZE to 24 * 1024 my memerr disappeared.
Unfortunatelly I still have link errors and I cannot find a docu in the wiki
about it.
Link
Xmit22888
RECV10120
FW 0
DROP1264
CHKERR 0
LENERR 0
MEMERR 0
RTERR 0
PROTERR
Thank you very much for your answers.
It finally (partly) works now :)
I had a priority problem in my freertos which made the lwip init task
call too late.
I am able to send data outside of the lwip thread now.
I am still worried because in my stats I see the following problems/errors:
Link
Xmit
Marco Jakobs wrote:
The memory issue is serious. A customer was asking for VJ compression
support, tried this today and BOOM, 3kB of RAM missing.
Yes, but have you actually tested 2.0.x to see it increased?
That's not fun, that's my daily business.
You're not the only one there ;-)
Just
Werner Motz wrote:
---> passing tcp_active_pcbs is not necessary because as u already
mentioned, I could call it everywhere. I just tried to give a parameter to
the callback function.
The usage of tcpip_callback should be OK.
---> Obviously it is not good / right to call macros and functions
> In my freertos task (outside lwip) I do following:
>
> [..]
>
> tcpip_callback_with_block(WTF, tcp_active_pcbs, 0);
Why on earth would you pass 'tcp_active_pcbs'? Wherever you got that
from: tell them this is wrong and they should stop spreading such horrible
code examples!
--->
12 matches
Mail list logo