HTTP communication using uIP/lwIP.

arvimg wrote on Friday, March 03, 2017:

Hello !

i already have a socket, tcp/ip connection using uIP between my ARM7 LPC2387 and a server. Now I want to make the communication over HTTP protocol and then with HTTPS . Data collected by the sensors are processed by LPC2387 which further needs to be sent to server for further analysis.

Please help me with guidance steps and code lines.

thanks

heinbali01 wrote on Friday, March 03, 2017:

Hi Arvind, FreeRTOS also has its own TCP/IP stack, along with a simple HTTP driver. Beside that, WolfSSL is supported, which opens the way to HTTPS.

If you want to use lwIP, we can only give limited support.

Here you can get more information about FreeRTOS+TCP.

We adapted WolfSSL for FreeRTOS+TCP. If you’re interested using it, please tell us. It has not been published pubicly yet. Regards.

arvimg wrote on Saturday, March 04, 2017:

Hi Hein ! Thanks a lot !

I don’t really have any preference for lwIP. I just want my connection to be a HTTP connection, then HTTPS, where already it is a TCP/IP socket connection. My product already uses FreeRTOS , its uIP modules.
I’m not aware of the HTTP driver for client sde .

And I would love to have a provision of WolfSSL .Please guide me further.

I, individually am new to using FreeRTOS, so guidance with even smaller steps would be wonderful.

thanks !

heinbali01 wrote on Monday, March 06, 2017:

Arvind,
Now one thing I’m not sure if there is a +TCP driver for LPC2387. I don’t know if its EMAC is compatible with either the EMAC in LPC17xx or LPC18xx, for which there are +TCP driver.

glenenglish wrote on Tuesday, April 18, 2017:

Arvind
Go for the FreeRTOS+TCP

LwIP network stack is a total P.O.S. compared to +TCP…
LwIP its designed to work on footprints that are crazy small (by todays standards)
LwIP will fight you all the way when used with a multi tasking OS, it was designed NOT to need one.

Having never written an HTTP server, I actually used the LwIP HTTP server as a flowchart template for my +TCP implementation.