Re: [lwip-users] LwIP configuration for directing LWIP_DEBUGF to user function

Hi Yacob, Redirecting may be different from IDE to IDE. Redirecting is not only for printf. In general you should define the macro PUTCHAR or similar to some low level handling depended on your own hardware. Here are some examples I found, for KAIL: http://www.keil.com/forum/60531/

Re: [lwip-users] LwIP configuration for directing LWIP_DEBUGF to user function

Hi Yacob, In file sysy_arch.c you have an include to debug.h If you set LWIP_DEBUG you need to define LWIP_PLATFORM_DIAG LWIP_PLATFORM_DIAG is your wrapper for printing Normally this is defined in cc.h that is part of your micro porting code. Hope that helped, Noam. From: lwip-users

Re: [lwip-users] An external filesystem for httpd

Hi, I have created a separate HTTPD server based on the contribution, some input from other users and my own input. One of the changes that I made was to create a different FS structure. Instead of a link list that places each file after the other and a linked list at the end of data I created

Re: [lwip-users] LWIP never tries to send a packet?

PHY special control/ status register Offset */ #define PHY_SPEED_STATUS((uint16_t)(1 << 1)) /*!< PHY Speed mask */ #define PHY_DUPLEX_STATUS ((uint16_t)(1 << 2)) /*!< PHY Duplex mask

Re: [lwip-users] LWIP never tries to send a packet?

Hi Chris, I am not working with ST HAL, rather with the older SPL (standard peripheral library). I do not know why you needed to change the PHY driver as all the standard PHY’s that are IEEE compatible will work the same. The ST driver has two portions: 1. MDIO/MDC connectivity (SMI)

Re: [lwip-users] Problem running lwip on cortex M7 with D cache enabled

Hi, I am working with STM32F7 with LwIP 2.02 + FreeRTOS 9 D and I cache are enabled. TX/RX descriptors are hard coded inside DTCM. We have no problems for now. Most of the rest of LwIP init is as it was in older projects that used the STM32F4 I strongly suggest upgrading to LwIP 2.02 or even

Re: [lwip-users] LWIP_HTTPD_SSI_MULTIPART and concurrent HTTP requests

we do not touch tag_part ! } return RespLen; } Hope that helped :-) BR, Noam. From: lwip-users <lwip-users-bounces+noam=silrd@nongnu.org> on behalf of Noam Weissman <n...@silrd.com> Sent: Friday, November 24, 2017 4:57 PM To: lwip-user

Re: [lwip-users] LWIP_HTTPD_SSI_MULTIPART and concurrent HTTP requests

Hi, For every connection the HTTP server allocates a session data structure ( http_state ). This data structure is passed to the call back functions as arg. You need to use it to differentiate between session. See inside httpd_accept: /* Allocate memory for the structure that holds the

Re: [lwip-users] httpd: how to implement AJAX

Hi, HTTPD is widely used and if you look around you can find examples from ST micro TI and other vendors. The examples that you will find are probably older versions with no POST or AJAX support but they work ! Noam. -Original Message- From: lwip-users

Re: [lwip-users] httpd: how to implement AJAX

] On Behalf Of Giuseppe Modugno Sent: Tuesday, November 14, 2017 2:42 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] httpd: how to implement AJAX Il 13/11/2017 18:04, Noam Weissman ha scritto: Yes SSID is a session ID that had been added to my own server code. So are you using a completely

Re: [lwip-users] httpd: how to implement AJAX

ething_2") == 0) { } else { // print a debug error : action unknown } Hope that helped, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Giuseppe Modugno Sent: Monday, November 13, 2017 6:09 PM To: lwip-users@nongnu.org Subject: Re: [lwip-us

Re: [lwip-users] httpd: how to implement AJAX

Hi, I am using the following technic for AJAX. Create an empty file named ajax.shtml or ajax.html and add it to your file list. Inside the file you only write one tag without anything else. For example Do not add CR or LF just the tag !!. Now when you issue an AJAX call the WEB server

Re: [lwip-users] httpd server app lwip 2.0.2 cgi

Hi, I am working with my own HTTP server that is different from the one in the contribution but uses a very similar mechanism. It took me some time to find it but you need to check: \src\include\lwip\apps httpd.h In the above file your will find more information. For every

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

reliability issue when using non-reliable network? Hi Noam, Thanks. Just increased both MEMP_NUM_PBUF to 50, MEM_NUM_TCP_PCB TO 15. I'm not sure if its harder to reproduce(longer time to run) - maybe. but it still happens.. On Tue, Nov 7, 2017 at 5:36 PM, Noam Weissman <n...@silrd.com<ma

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

Hi, Check that you have MEMP_NUM_PBUF 50 or more that MEMP_NUM_TCP_PCB is 15 or more The above may help, I think. Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Itzik Levi Sent: Tuesday, November 07, 2017 5:29 PM To: Mailing list for lwIP users

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

at 9:39 AM, Noam Weissman <n...@silrd.com<mailto:n...@silrd.com>> wrote: Hi Itzik, Ops I missed that ☺ I am attaching my own lwpopts.h I am using FreeRTOS as OS on STMF32xx micro’s. I am running several modules (SDDP, TCP terminal, HTTP, SSH etc… ) with the above settings on the s

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

is defined to 0 as you can see, and I AM using threads. I will try reducing the memory usage and look at socket examples, maybe this will help. On Nov 7, 2017 12:44 AM, "Noam Weissman" <n...@silrd.com<mailto:n...@silrd.com>> wrote: Hi Itzik, From participating the group

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

somehow, I'm new to lwip and that's why I'm here. Question is, what did I do wrong, and how to pinpoint the problem. Thanks, Itzik. On Mon, Nov 6, 2017 at 11:19 PM, Noam Weissman <n...@silrd.com<mailto:n...@silrd.com>> wrote: Hi Itzik, I see that you have defined: TCP_WND

Re: [lwip-users] Lwip tcp-stack reliability issue when using non-reliable network?

Hi Itzik, I see that you have defined: TCP_WND=(100 * TCP_MSS) TCP_SND_BUF=TCP_WND MEMP_NUM_TCP_SEG=TCP_SND_QUEUELEN If TCP_MSS is defined 536 (default) that means that your TCP_WND is 53,600 bytes ? and that is over a serial line ? How much RAM do you have?, How much RAM is defined for

Re: [lwip-users] Problem with TCP write.

org] On Behalf Of Noam Weissman Sent: 23 October 2017 13:59 To: Mailing list for lwIP users Subject: Re: [lwip-users] Problem with TCP write. Hi Gautam, First of all you are not supposed to make changes in opt.h file... For that you need to add lwipopts.h in your own code ! Have you star

Re: [lwip-users] Problem with TCP write.

. Can you please help me out if you find anything not configured properly? Regards, Gautam From: lwip-users [mailto:lwip-users-bounces+gautam.kumar=invendis@nongnu.org] On Behalf Of Noam Weissman Sent: 23 October 2017 13:32 To: Mailing list for lwIP users Subject: Re: [lwip-users] Problem

Re: [lwip-users] Problem with TCP write.

Gautam, Check err.h file ! /** Out of memory error. */ ERR_MEM= -1, You are doing something wrong in your code or did not properly defined your memory settings in lwipopts.h If you show your code, it would help. BR, Noam. From: lwip-users

Re: [lwip-users] ERR_MEM when sending large data, LWIP stats show no error

Hi Adrian, I am using the STM32F765 and do not see real any problem. The driver and low level are very similar to the F4.. There are some small changes in initializing code but there is a change in descriptors location. For some reason they force it to be on a specific section. Maybe a DMA

Re: [lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select.

and UDP data transfer each handled by a separate thread. BR, David On 07/09/17 07:25, Noam Weissman wrote: Hi David, Attached please find my own sys_arch files used in STM32F4xx with FreeRTOS. Hope that helps in some way. BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd

Re: [lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select.

Hi David, Attached please find my own sys_arch files used in STM32F4xx with FreeRTOS. Hope that helps in some way. BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of David Lockyer Sent: Wednesday, September 06, 2017 5:13 PM To: lwip-users@nongnu.org

Re: [lwip-users] LWIP_MPU_COMPATIBLE set to 1, but still get memory management fault in lwip_select.

Hi David, I have upgraded LwIP from 1.41 to 2.02 and only handled the sys_arch.h/c files The only thing I can remember that I had to change was the ip_addr variable definitions in my own code. Beside that I have not mad any change to the LwIP code. STM32F4 and also F7 with FreeRTOS...

Re: [lwip-users] ERR_MEM when sending large data, LWIP stats show no error

Hi Adrian, Are you using RAW, netcon or Socket API ? I think that you have set a too large window size for the mem size you have. You should not send 32K blocks in one go. You need to send smaller block, say 1K or 1.5K, check available memory of send buffer and if available send another

Re: [lwip-users] Lwip on external ram

Hi Milan, Check your system and see that the TCP stack task priority is one of the highest in the system. Check that you have a small delay or system calls in your tasks, this avoids task starvation, etc... In general LwIP 2.0x is better but if you have some basic problem in your system this

Re: [lwip-users] Lwip on external ram

Hi Milan, I am working with STM32 + FreeRTOS + LwIP for more than 6 years now. >From my own experience It works great and almost always if you have problems >it is due to not using the library properly. LwIP 1.41 is rather old and that suggest that the example you use is also a bit old. I can

Re: [lwip-users] Advice on wifi module

Hi Sergio, Murata, Microchip and all other readymade modules are a bit expensive. Around 30-45$... Some time ago I have searched for such module and finally we chose ROVING RN-171... They may have a newer one, now. ROVING module was also around $29 for small quantities but after talking

Re: [lwip-users] dhcp behaviour

Hi Max, I hope I am not confusing you or making an error here. As far as I know DHCP client is handled almost completely by LwIP. You should not worry about timers etc... I have attached my DHCP task, take a look and I hope this helps... This code is running with LwIP 1.41 BR, Noam.

Re: [lwip-users] how to set the link up

. On Fri, 7 Jul 2017, 18:52 massimiliano cialdi, <massimiliano.cia...@powersoft.it<mailto:massimiliano.cia...@powersoft.it>> wrote: On 07/07/2017 18:04, Noam Weissman wrote: > > Speed, duplex, link etc... is low level handling and the TCP stack is > not aware of that. >

Re: [lwip-users] how to set the link up

OIP */ if (netif->flags & NETIF_FLAG_UP) { netif_issue_reports(netif, NETIF_REPORT_TYPE_IPV4|NETIF_REPORT_TYPE_IPV6); } NETIF_LINK_CALLBACK(netif); } } first 'if' is always false, and I wonder why best regads Max On 05/07/2017 19:21, Noam Weissman wrote: &g

Re: [lwip-users] how to set the link up

gmx.de <goldsi...@gmx.de> Sent: Thursday, July 6, 2017 10:36 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] how to set the link up Have you read about the "not meant offensive" part? Seriously, this project lives from people getting involved and sharing improvements!

Re: [lwip-users] how to set the link up

] how to set the link up Noam Weissman wrote: > THANKS for pointing this out !!!. > > I am using the code I sent for several years and was not aware of that :-( I must say now I'm a little bit shocked. You already pointed out lwIP has threading requirements on this list more than once. And stil

Re: [lwip-users] how to set the link up

ist for lwIP users Subject: Re: [lwip-users] how to set the link up Hi, On Wed, Jul 05, 2017 at 04:55:24PM +, Noam Weissman wrote: > > My DHCP task calls dhcp_start and wait for an IP. If there is a > timeout the task will assign a static default IP. You can do something > sim

Re: [lwip-users] how to set the link up

task to poll PHY link status (and speed, to switch on/off speed led), and another task to manage ip assignment. These task should be under application layer. I do not know if it's a good idea. best regards Max On 05/07/2017 16:40, Noam Weissman wrote: Hi Sylvian, THANKS for pointing this ou

Re: [lwip-users] how to set the link up

05/07/2017 13:59, Noam Weissman wrote: > >>From what I have seen the KSZ8081RNACA is an IEEE compliant PHY... that > >>means that the driver is standard. > > > >You need to read PHY_BSR register (1) and check bit 3 ... this is the link > >status. This is w

Re: [lwip-users] how to set the link up

:02 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] how to set the link up On 05/07/2017 13:59, Noam Weissman wrote: > >From what I have seen the KSZ8081RNACA is an IEEE compliant PHY... that > >means that the driver is standard. > > You need to read PHY_BSR register (

Re: [lwip-users] Porting lwIP to ERIKA enterprise RTOS

Hi Josip, The files I sent you should not be compiled with your OS. You must modify them to suit your needs. I am not familiar with ERIKA so I cannot help in that. BR, Noam. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of

Re: [lwip-users] Porting lwIP to ERIKA enterprise RTOS

Hi Josip, I would suggest taking a sys_arch files for FreeRTOS and modify it I have attached my own sys_arch files used with LwIP 2.0x and FreeRTOS I have started creating my own sys_arch files for LwIP 1.41 but after finding a well written set I have used it instead. The files were

Re: [lwip-users] how to set the link up

Hi, >From what I have seen the KSZ8081RNACA is an IEEE compliant PHY... that means >that the driver is standard. You need to read PHY_BSR register (1) and check bit 3 ... this is the link status. This is what I am doing in a task. The reason for doing the above is that a PHY with RMII has no

Re: [lwip-users] lwip complex example

Hi, If you use RAW API it is not thread safe, if you use Socket API it is OK. No problems running multiple modules with mixed API if you follow the rules. I am running devices with several modules in RAW API + Socket API. BR, Noam. -Original Message- From: lwip-users

Re: [lwip-users] A new users request for help with sending TCP Packets on Demand

Hi, First of all great that you have been able to leap to 2.xx  Keeping the connection open or not depends on your own needs. So there is no simple reply to that. As for buffering, it depends on your system design. Do you have an OS or are you running without an OS, do you have sufficient

Re: [lwip-users] internet over PPP and NAT issue

can't upgrade the version. there wifi code depends on the LWIP . From: lwip-users <lwip-users-bounces+asaf=roadtracktelematics@nongnu.org<mailto:lwip-users-bounces+asaf=roadtracktelematics@nongnu.org>> on behalf of Noam Weissman <n.

Re: [lwip-users] internet over PPP and NAT issue

Hi Asaf, I can suggest upgrading to LwIP 2.02 The porting is not complicated and the benefits are significant. I find that LwIP 2.02 Is better and has smaller footprint. Good luck, Noam W. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Asaf Manasse Sent:

Re: [lwip-users] A new users request for help with sending TCP Packets on Demand

Hi, I would suggest upgrading to lwip 1.41 and take a look at this: http://download.savannah.nongnu.org/releases/lwip/ http://lwip.wikia.com/wiki/Raw/TCP Raw/TCP | lwIP Wiki | Fandom powered by Wikia lwip.wikia.com Initialization Edit. lwip_init() must be

Re: [lwip-users] Simultaneous GET requests to HTTP Server

search a possibility to accelerate the communication. I just want to give the possibility to the user to work with the default settings of the browser (that means 6 parallel connections for Firefox). Simeon On 16.6.2017 г. 14:18 ч., Noam Weissman wrote: Hi Antonio, RAW mode API is meant

Re: [lwip-users] Simultaneous GET requests to HTTP Server

Hi Antonio, RAW mode API is meant to be used in systems without an OS or if you use an OS in one task, dedicated to TCP stack. Sure one connection is handled at a time because you have one micro that is able to run only one command at a time. Using threads actually worsen the situation

Re: [lwip-users] Building mbedtls using LWIP library :: Handshake takes too long

<lwip-users-bounces+gonga=kth...@nongnu.org<mailto:lwip-users-bounces+gonga=kth...@nongnu.org>> on behalf of Noam Weissman <n...@silrd.com<mailto:n...@silrd.com>> Sent: Thursday, June 8, 2017 15:09 To: Mailing list for lwIP users Subject: Re: [lwip-users] Building mbedtls us

Re: [lwip-users] Building mbedtls using LWIP library :: Handshake takes too long

Hi, Do you use any external SDRAM or just the M3 own memory ?... If you do not have any extra RAM I do not see how you can run HTTPS.. you need around 100-200K RAM to run HTTPS for one page. The estimate is based that your page hase one or more JS files, one or more images, one or more CSS

Re: [lwip-users] LwIP 1.41 select does not return ?

it0...@gmail.com - “ The greater part of progress is the desire to progress. ” — Seneca From: lwip-users <lwip-users-bounces+arpit.a=alumni.iitg.ernet...@nongnu.org> on behalf of Noam Weissman <n...@silrd.com> Sent: Wednesday, May

Re: [lwip-users] LwIP 1.41 select does not return ?

select does not return ? Noam Weissman: >Were is the semaphore released ? In "event_callback()", if I remember correctly. Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users lwip-u

Re: [lwip-users] LwIP 1.41 select does not return ?

nesday, May 31, 2017 4:30 PM To: Noam Weissman; lwip-users@nongnu.org Subject: Re: [lwip-users] LwIP 1.41 select does not return ? Hi Noam, OK, cool. It sounds like you're on top of the whole raw/netconn thing. I was really checking to see whether you'd failed to start the tcpip thread, or some

Re: [lwip-users] LwIP 1.41 select does not return ?

. From: lwip-users <lwip-users-bounces+noam=silrd@nongnu.org> on behalf of Tim Cussins <timcuss...@eml.cc> Sent: Wednesday, May 31, 2017 1:43 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] LwIP 1.41 select does not return ? Hi Noam, On Wed, May 31, 2017, at 11:11 AM, N

Re: [lwip-users] LwIP 1.41 select does not return ?

_ From: lwip-users <lwip-users-bounces+arpit.a=alumni.iitg.ernet...@nongnu.org> on behalf of Noam Weissman <n...@silrd.com> Sent: Wednesday, May 31, 2017 4:49 PM To: Tim Cussins; Mailing list for lwIP users Subject: Re: [lwip-users] LwIP 1.41 select does not return ? Hi Tim, I a

Re: [lwip-users] LwIP 1.41 select does not return ?

that lwip_select is not 100% BSD compliant as CypherBridge code is ? Thanks and BR, Noam. From: Tim Cussins <timcuss...@eml.cc> Sent: Wednesday, May 31, 2017 1:57 PM To: Noam Weissman; Mailing list for lwIP users Subject: Re: [lwip-users] LwIP 1.41 selec

[lwip-users] LwIP 1.41 select does not return ?

Hi All, I am trying to run a CypherBridge uSSH server demo on STM3240-Eval board. The original code was designed for ST discovery board with the same micro. The original code uses FreeRTOS 6.01 and LwIP 1.32 .. I am using a base project that is used for testing. This base project uses

Re: [lwip-users] Raw api + multiple TCP Connections

oam=silrd@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Monday, May 22, 2017 4:10 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] Raw api + multiple TCP Connections Noam Weissman wrote: > If you use Lwip 1.41 the tcp_accepted function should accept the > SERVER pcb and not the new

Re: [lwip-users] Raw api + multiple TCP Connections

Jan see his code. He was trying to compare listening port with working port -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Jan Menzel Sent: Monday, May 22, 2017 4:00 PM To: lwip-users@nongnu.org Subject: Re: [lwip-users] Raw api +

Re: [lwip-users] Raw api + multiple TCP Connections

Hi, First of all read the lwip readme and every document you can find. Check the echo server example and see how it is written. 1. If both servers are the same write functions and simply pass parameters. You do not need to copy and paste the same code. Use the arg parameter in the call backs

Re: [lwip-users] Raw api + multiple TCP Connections

So there are two separate servers with each handling one connection, correct ? So what is the problem ? Every server should have its own pcb and every connection has its own separate pcb You are doing something wrong, check your code. From: lwip-users

Re: [lwip-users] Raw api + multiple TCP Connections

Hi, Do you mean two connections that you initiate from your device to two different IP's or two connections in a server ? Your question is not clear ? Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Werner Motz Sent: Monday, May 22, 2017 1:29 PM

Re: [lwip-users] HTTPS support in lwip

Hi Simon, Is there a way to limit the number of concurrent HTTP connection, say to one ? If this can be done we may be able to run HTTPS with an overhead of about 40K for SSL/TLS BR, Noam. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On

Re: [lwip-users] HTTPS support in lwip

2017 9:34 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] HTTPS support in lwip 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

Re: [lwip-users] HTTPS support in lwip

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

Re: [lwip-users] DHCP fails ?

esday, May 9, 2017 10:11 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] DHCP fails ? Noam Weissman wrote: > I have a simple link task that checks the PHY for link, reads it. If > link is up it starts the DHCP task and wait for address. > > If link is down the DHCP task i

[lwip-users] DHCP fails ?

HCP task will work fine Just to point out that this setup works for several years on several devices and never had any problems Am I missing something ?? Thanks and BR, Noam. [cid:image001.jpg@01D26A92.68494F10] Noam Weissman Software Engineer SILORA R p: +972-4-9554915 m: +972-52-5786135

Re: [lwip-users] Building mbedtls using LWIP library

To: lwip-users@nongnu.org Subject: Re: [lwip-users] Building mbedtls using LWIP library Noam Weissman wrote: > I strongly suggest upgrading to LwIP 1.42 as a minimum. As far as I > know there were many fixes from 1.40 to 1.42 1.42? That version doesn't even exist... > [..] the mbedTLS us

Re: [lwip-users] Building mbedtls using LWIP library

Hi Shruthi, As a continuation to Jan mail... I am using mbedTLS 2.42 + LwIP 2.02 and it works for me... after some straggling :-) I strongly suggest upgrading to LwIP 1.42 as a minimum. As far as I know there were many fixes from 1.40 to 1.42 mbetTLS has a net_socket.c+h file that is the

Re: [lwip-users] Transfer Mibs of data over TCP

esday, April 4, 2017 12:30 AM To: Mailing list for lwIP users Subject: Re: [lwip-users] Transfer Mibs of data over TCP Hi, On Mon, Apr 03, 2017 at 01:43:44PM +, Noam Weissman wrote: > Hi, > > Why not use the RAW API server that is in the contribution ? > > I am not using it becau

Re: [lwip-users] Transfer Mibs of data over TCP

Hi, Why not use the RAW API server that is in the contribution ? I am not using it because am using my own modified code that was created before the current version. As far as I know it works nicely and many are using it ☺ I have no problems accepting a large file 1MB… never had to accept a

Re: [lwip-users] PolarSSL and mbedTLS

m. BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Noam Weissman Sent: Thursday, March 16, 2017 5:58 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] PolarSSL and mbedTLS Simon, I am not saying that LwIP has bugs because I am no

Re: [lwip-users] heap problem with chrome

Hi, I am not familiar with netconn API but I will try.. Every browser implements the protocol a bit differently. The data fields in the HTTP may not be In the same order and sometimes (IE) are very long… That leads to problems when your code Is very optimized and unexpected. I found that on

Re: [lwip-users] heap problem with chrome

Hi Mohamed, Part of the LwIP contributions you have working HTTP servers. Have you used one of these or created something of your own ? What is the API that you are using: RAW, Netcon or Socket ? BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of

Re: [lwip-users] PolarSSL and mbedTLS

return( 1 ); } return( 0 ); } Jan On 15.03.2017 20:30, Noam Weissman wrote: Hi Simon, I have triad debugging my code and added : #define LWIP_DEBUG LWIP_DBG_ON #define SOCKETS_DEBUG LWIP_DBG_ON Strange that with this switches on I am

Re: [lwip-users] PolarSSL and mbedTLS

_block( const mbedtls_net_context *ctx ) [...] switch( errno ) { #if defined EAGAIN case EAGAIN: #endif #if defined EWOULDBLOCK && EWOULDBLOCK != EAGAIN case EWOULDBLOCK: #endif return( 1 ); } return( 0 ); } Jan On 15.03.2017 20:30, Noam Weissman wrote: &g

Re: [lwip-users] PolarSSL and mbedTLS

- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Friday, March 10, 2017 10:36 AM To: lwip-users@nongnu.org Subject: Re: [lwip-users] PolarSSL and mbedTLS Noam Weissman wrote: > I get a read error inside lwip_recvfrom funct

Re: [lwip-users] PolarSSL and mbedTLS

large data blocks (>~ FRAGMENT_LENGTH) will not be possible. Jan On 12.03.2017 10:05, Noam Weissman wrote: > Hi Jan, Simon... > > > > I have found a solution that seems to work J... > > > > A college of mine working on the server side pointed m

Re: [lwip-users] lwip 1.4.1 -> 2.0.1: problem with dhcp

Hi Markus, As a skeleton there is no change. Maybe you need wait until you have a link Or that your driver takes longer to finish initializing. BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of markus.l...@gmx.ch Sent: Tuesday, March 14, 2017 4:08

Re: [lwip-users] lwip_select never returns value > 0

Hi, Try using: tv.tv_sec = 1; tv.tv_usec = 0; It works for me BR, Noam. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of pekez Sent: Tuesday, March 14, 2017 2:19 PM To: Mailing list for lwIP users Subject: [lwip-users] lwip_select

Re: [lwip-users] Upgrading from 1.4.x to 2.0.2

Hi Jeff, Here are the changes I made: Create a structured project and under LwIP leaf create: Api Core IPv4 Netif In 1.41 you have file named timers.c that collide with timers.c from FreeRTOS... I changed the file name but in 2.xx it was changed from timers.c to timouts.c so there is no need

Re: [lwip-users] lwIP 2.0.2 released

Great, Thanks for all the hard work :-) BR, Noam. -Original Message- From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Simon Goldschmidt Sent: Monday, March 13, 2017 2:41 PM To: lwip-users@nongnu.org; lwip-de...@nongnu.org Subject: Re: [lwip-users]

Re: [lwip-users] PolarSSL and mbedTLS

to be working. Thanks for everyone that puts their inputs :) If I will have an update I will update the group. BR, Noam. From: lwip-users [mailto:lwip-users-bounces+noam=silrd@nongnu.org] On Behalf Of Noam Weissman Sent: Sunday, March 12, 2017 12:39 AM To: Mailing list for lwIP users Subject: Re

Re: [lwip-users] PolarSSL and mbedTLS

Hi Simon, with SSL there is a read for 5 bytes record header and then reading the data itself as a whole or in parts (inside lwip_recvfrom). My module is a single task that has a state machine. When the state is in OPEN state it blocks for 1 second on select, if select is returning with a

Re: [lwip-users] PolarSSL and mbedTLS

_ From: lwip-users <lwip-users-bounces+noam=silrd@nongnu.org> on behalf of goldsi...@gmx.de <goldsi...@gmx.de> Sent: Saturday, March 11, 2017 9:34 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] PolarSSL and mbedTLS Noam Weissman wrote: I am not ignoring the fact that

Re: [lwip-users] PolarSSL and mbedTLS

Simon Goldschmidt <goldsi...@gmx.de> Sent: Friday, March 10, 2017 10:35 AM To: lwip-users@nongnu.org Subject: Re: [lwip-users] PolarSSL and mbedTLS Noam Weissman wrote: > I get a read error inside lwip_recvfrom function. > [..] > If anyone has any ideas on what more to check or te

Re: [lwip-users] SSH - Raw API

Hi Sergio, Embedded Linux uses lots of RAM and is much more complicated from FreeRTOS. Even is we eventually will add external RAM, say 16-32M or more I still prefer the FreeRTOS [] . As for all the apss that are running in the device its a a must, system requirements. I am sure that

Re: [lwip-users] Telnet - Raw API

Hi Sergio, Long time :-) ... Yes I am aware of what you wrote. Inside the recvfrom function this is actually what the function is doing... copying in parts from the chained buffers until it gets all the data it needs. LwIP has sufficient RAM (22K) and PCB's (80) so it should be ok ?

Re: [lwip-users] PolarSSL and mbedTLS

n what more to check or test please respond. BR, Noam. From: lwip-users <lwip-users-bounces+noam=silrd@nongnu.org> on behalf of Noam Weissman <n...@silrd.com> Sent: Friday, March 3, 2017 5:50 PM To: lwip-users@nongnu.org Subject: Re: [lw

Re: [lwip-users] Telnet - Raw API

Hi Nick, I will answer you next week, I have a minimal telnet server but it is not exactly what you need, you will have to change it to suit your need. Please write to my work mail n...@silrd.com and we will continue from there. BR, Noam. From: lwip-users

Re: [lwip-users] PolarSSL and mbedTLS

between mbedtls and lwip. One last advice: carefully check your stack >> usage. mbedtls uses lots of function pointers which Keils static call >> graph analysis can not see and does not warn about. >> >> Jan >> >> On 01.03.2017 14:01, Noam Weissman wrote: >>> H

Re: [lwip-users] PolarSSL and mbedTLS

nd a little bit with errno in the interface > between mbedtls and lwip. One last advice: carefully check your stack > usage. mbedtls uses lots of function pointers which Keils static call > graph analysis can not see and does not warn about. > > Jan > > On 01.03.2017 1

Re: [lwip-users] PolarSSL and mbedTLS

t; on behalf of goldsi...@gmx.de <goldsi...@gmx.de> Sent: Thursday, March 2, 2017 11:24 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] PolarSSL and mbedTLS Noam Weissman wrote: Same problem with either 1.41 or 2.01 tested on both Up to now, EWOULDBLOCK is based on netconn ca

Re: [lwip-users] PolarSSL and mbedTLS

lrd@nongnu.org> on behalf of goldsi...@gmx.de <goldsi...@gmx.de> Sent: Thursday, March 2, 2017 8:54 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] PolarSSL and mbedTLS Noam Weissman wrote: > lwip_recvfrom is called. > > Inside this function there is a do <>

Re: [lwip-users] PolarSSL and mbedTLS

s read() is called in a non-blocking way. mbedtls default interface layer does some checking on the socked to detect if data is available and/or the read() call would block. I had to play a little bit around with errno to get it working. Jan On 01.03.2017 23:19, Noam Weissman wrote: &g

Re: [lwip-users] PolarSSL and mbedTLS

ain up pbufs until a block is complete and can be rehashed and decrypted. I'd willing to assist in implementing this. Jan On 01.03.2017 21:46, Noam Weissman wrote: > Hi Simon, > > > Yes it may be an issue, any ideas or a change in the settings I placed > here earlier ? &g

Re: [lwip-users] PolarSSL and mbedTLS

wip. One last advice: carefully check your stack > usage. mbedtls uses lots of function pointers which Keils static call > graph analysis can not see and does not warn about. > >Jan > > On 01.03.2017 14:01, Noam Weissman wrote: >> Hi, >> >> >> >&

[lwip-users] PolarSSL and mbedTLS

are not correct ?? A second question for Simon or anyone that can assist. I tried to set LWIP_DEBUG to 1 and my total used RAM (compiler) dropped about 30K ?? Why is that ?... I understood that debug should take more RAM not Less ? Thanks, Noam. [cid:image001.jpg@01D26A92.68494F10] Noam Weissman

Re: [lwip-users] TCPIP and MAC thread task priorities

Of Sylvain Rochet Sent: Monday, February 27, 2017 2:25 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] TCPIP and MAC thread task priorities Hi, On Mon, Feb 27, 2017 at 11:50:26AM +, Noam Weissman wrote: > Hi All, > > This comes from my own experience with STM micro that h

  1   2   3   >