AnsweredAssumed Answered

FRDM-K64F KSDK 1.3.0 tcp_echo demo bugs?

Question asked by Nicola Bongiovanni on Jul 21, 2016
Latest reply on Aug 23, 2016 by manfredschnell

I tried to use the tcp echo demo project with rtos MQX supplied with KSDK_1.3.0, but I found some problems:

when I have tested the tcp_echo application using a PC Tool that performs echo request on TCP port 7, the FRDM-K64F responds for a little time but after the application stops in the assert function "void sys_assert( const char *msg )" file sys_arch.c.

 

I have captured the two msg below:

 

Name : msg

  Details:0x1def8 "tcpip_thread: invalid message"

  Default:0x1def8 "tcpip_thread: invalid message"

  Decimal:122616

  Hex:0x1def8

  Binary:11101111011111000

  Octal:0357370

   

Name : msg

  Details:0x1ca80 "pbuf_free: p->ref > 0"

  Default:0x1ca80 "pbuf_free: p->ref > 0"

  Decimal:117376

  Hex:0x1ca80

  Binary:11100101010000000

  Octal:0345200   

 

No changes I made to the project "lwip_tcpecho_demo_mqx_frdmk64f" from KSDK_1.3.0.

There are some bugs on the LWIP stack or there are some errata configuration parameters?

Thank for any help!

 

Nicola

Outcomes