I am trying to develop a project over TM4C Iot launchpad, so I want to running a client on the Rpi so I can do some test.
Right now the code can compile on linux, but it did not works, it did not communicate with the lwip running on the Tm4c launchpad, for the launchpad side, I could use the browser to read the simple website out from it. so the server side is ok. I was wondering, I only init lwip with the lwip_init() function. I am trying to use the linux ethernet driver to acquire the IP, and use the raw tcp function to collect the data send by the TM4C launchpad. just like the regular socket programming did. so my question is 1. Do I need any other functions so that I could init the lwip which could enable raw tcp connection. 2. right now the tcp_bind() could bind to any ip without an error, even the ip is not belonging to the linux system. (I have enable the Debug, all the pcb is empty.) which part could be wrong? any hints? Shan main.c <http://lwip.100.n7.nabble.com/file/n26335/main.c> -- View this message in context: http://lwip.100.n7.nabble.com/TCP-Raw-communication-between-Raspberry-pi-and-TI-TM4C-tp26335.html Sent from the lwip-users mailing list archive at Nabble.com. _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
