K64F: RTOS + LiWP - tcp echo and http server

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

K64F: RTOS + LiWP - tcp echo and http server

1,328 Views
grochal7
Contributor III

Hello!

Is it possible to deinitialize the tcpip with liwp?

I'am using the tcp echo example.

I'd like to close tcp taks and then open the http server (also from http server example) - after pressing the button.

So first i initialized tcpecho and switch IRQ. It works. Then I press the button - now i'd like to initialize http server.

If i try use both in one project (http server initialization after pressing a button), I have this statement:

"tcp_slowtmr: active pcb->state != CLOSED".

Now I try to delete tcp connection and tcp task:

netconn_close(conn);
netconn_delete(conn);
vTaskDelete(xHandle_TCP_task);‍‍‍‍‍‍

And after that initialize the http server:

if(xTaskCreate(http_server,"http_server",5000, NULL, 16, NULL) != pdPASS)
{
     PRINTF("Task creation failed!(main)\r\n");
}

Now I dont have "tcp_slowtmr: active pcb->state != CLOSED", but unfortunately, still not working.

Both of exampkes work separately.

So, what i should to do? Is it possible to use http server after closing some tcpip application?

Labels (1)
3 Replies

920 Views
kalei_joanel
Contributor I

Can anyone please confirm for me that the recently updated EthernetInterface library works on the FRDM-K64F platform? I am presently struggling to get the TCPSocket_Helloworld example application to run. It hangs when init() is called.

Subway Surfers Psiphon Hill Climb Racing

0 Kudos

920 Views
grochal7
Contributor III

I'm using SDK 2.3.0 for my k64f board and all of examples (with freertos and without) from this SDK work (SDK 2.2.0 works too)

Whitch one not working for u?

0 Kudos

920 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi grochal7:

It is possible to run tcp echo and http server simultaneously.

I added function tcpecho_init based http server demo. Please see below picture. Both echo server and http server work normally.

pastedImage_1.png

But deinitialize the tcpip is not a normal behavior.  On most embedded system, when you start the TCP/IP stack, you never stop it. A lot of the memory that LwIP uses comes from statically allocated pools.

Regards

Daniel