Is there a way to report a bug to intel for this? After much more time researching I have it down to a few scenerios. I looked at the library for UDP. Upon further testing I know that if I call just UDP.read() it locks up. The flush function calls UDP.read() until there in no more data using the UDP.available function (more on this in a bit) and flush locks up as well. The UDP.parsepacket function calls flush before reading in data. So it looks like something in just read. However, there are other anomalies as well.
Here is a snippet of code:
Serial.print("Udp Avail before: ");
Serial.println(Udp.available());
Udp.read(_packetBuffer, 25);
Serial.print("Udp Avail after: ");
Serial.println(Udp.available());
Here is the output:
Udp Avail before: 26 Udp Avail after: 26
As you can see, doing a UDP.read(variable, numbertoread) does not decrement the UDP.Available() as it should. So there is a bug around that as well.
I am running the arduino IDE on a Mac, I have not tried on Windows but I am not sure why that would make a difference.
Anyone have any ideas before I give up on the Galileo and look for a better CPU?
BTW.. This is the 1st generation, I ordered a 2nd generation just to see if anything would change.