I'm using dm648 ndk v2.0.0 to send jpeg image, but meet some problems.
The DM648 board(client) is connected to PC (server) via a net reticle directly.
After some hours, the program go wrong. the socket send() functure return err 35. And when the program re-connect the server， the socket connect() functure return err 64, then err 65.
I have checked the serrno.h which shows that:
#define EWOULDBLOCK 35 // Operation would block
#define EHOSTDOWN 64 // Host is down
#define EHOSTUNREACH 65 // No route to host
It seems the host PC goes wrong. But when the dsp program goes wrong, I keep the PC server program and restart dm648 client program, and the dm648 client will connect the server and send data successfully .
I want to know where is the beef after all? Is it the ndk's issue, or the dm648 client program's ?
Any useful advice will be highly appreciated!