Having followed the AVR-IoT AC164106 QUICK START GUIDE on two development boards, I've had no success on getting either board to connect to WiFi correctly 'out-of-the-box'.
Given the simplicity of the three step QUICK START procedure ... it's not met my "Get Started in 30 second" expectation.
1st ISSUE: I needed to update the firmware before I was able to get the blue (WiFi connected) led to go on (after the board's initial start up check). Before I applied the update (i.e. in the out-of-the-box state) only the red (error status) led would light.
If this is always going to be the case ... it might be better to highlight this as the first step in the QUICK START procedure webpage.
2nd ISSUE: After the firmware update was applied the blue (WiFi connected) LED turned on ... but only for a short while. On one device it would remain on for 5 seconds before the fault led lit. On the 2nd device it took around 20 seconds. I have not investigated yet, so have no idea as to why there is this discrepancy in time, only that it is consistent and related to the board. After a further period of time the red (error status) led goes off and thew blue (WiFi connected) led turns on. This cycle continues indefinitely.
While a list of meanings is provided for various led states is given in the USER GUIDE ... none of the documented led states relate to this: red then blue then red led sequence.
3rd ISSUE: having done some investigation, I observe both boards correctly get their reserved IP address from the network DHCP server, but then seem to drop off the WiFi network. As such neither gets to connect out of the network to the Google IoT Cloud.
My investigation with WireShark suggests this may be an ARP related issue (see attached)
Specifically the ARP broadcast from the devices requesting the MAC address of the gateway is NOT getting a response. Thus, presumably, the board is NOT able to update it's APR table... and thus communicate out across the local network.
Naturally my suspicions, fall onto the local network or router configuration
I notice the ARP 'Who has' request sent out by the AVR-IoT board is 60 bytes long ... and getting NO response.
Whereas I can see similar 60 byte broadcast requests from other devices on the network, that are getting answered as a 42 byte response.
For completeness, I can see 'Who has' requests being sent out as 42 bytes to a specific host and getting answered as 60 bytes.
Is anyone able to shed light on what might be happening ... and how to correct it, so these AVR-IoT boards connects to Google IoT Core Cloud correctly?
Thanks in advance,