Hi, I'm still having problems with TCP sending and receiving on the SAMA5D36. I switched from tcpblaster to tcpecho. That works as long as whatever send I do from the host linux computer is shorter than the MTU or ETH_PKTSIZE (right now, configured to be 1500 bytes). I'm using the SAMA5D36 GMAC (gigabit ethernet port) which has a max packet size of 1536 bytes.
So I can do any amount of discrete sends, each of less than 1448 bytes. This seems to be because the IP header size is 30 bytes and the TCP header size is 20 bytes, 1448 + 32 + 20 = 1500 bytes. But when I try to do a send of 1448 bytes or more, the tcpecho server hangs. It seems like it can't handle TCP sends that have more than one IP packet. What could cause that? Could it be a bug in the NuttX TCP code? Or is it some kind of misconfiguration on my part? (I wrote a custom python echo server client to test the message sizes.) I also tried tcpblaster from linux to linux (client and server both on linux) and they work fine. But they don't work linux->nuttx or nuttx->linux. -adam -- Adam Feuer <a...@starcat.io>
