I am creating a simulator example that runs the TCP blaster example
using the loopback 127.0.0.1 device. I will give that to you once I
verify it.
Thanks Greg. That is exactly what I am trying to create, so I can get some
insight into what's wrong with my SAMA5D36 configuration.
I submitted two PRs. Both are needed:
* https://github.com/apache/incubator-nuttx/pull/247
* https://github.com/apache/incubator-nuttx-apps/pull/64
I think I am seeing basically the same failure as you. I haven't had
time to dig into details, but this is what I see:
$ ./nuttx.exe
NuttShell (NSH) NuttX-8.2
nsh> help
help usage: help [-v] [<cmd>]
[ cmp exit ifup mkrd pwd time
? dirname false kill mh rm true
basename date free losetup mount rmdir uname
break dd help ls mv set umount
cat df hexdump mb mw sh unset
cd echo ifconfig mkdir poweroff sleep usleep
cp exec ifdown mkfatfs ps test xd
Builtin Apps:
nsh tcpclient
nsh> tcpclient
Binding to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0000
server: Accepting connections on port 5471
Connecting to IPv6 Address: 0000:0000:0000:0000:0000:0000:0000:0100
client: Connected
server: Connection accepted -- receiving
Then nothing more.
In this configuration, the server runs as a daemon on the same
platform. It is started by the client. But after that, they should
behave the same.
NOTE that I have it set up to use IPv6 with the IPv6 loopback address.
IPv4 would probably be simpler to debug.
Greg
