Hello Rndm Tsk,
It seems that there might have been an issue when you are flashing the board. As the issue seems to appear when you use the Intel(R) Edison Board Configuration Tool, I'd suggest you to try using the manual method called flashall.sh. You can find a guide on how to do it in How to Run the Flashall Script .
Let me know if this helps you.
Thanks for your response, I'll give this a try!
As a note, is it enough to power the board using the OTG port via a USB port on a MacBook Pro while doing this? I was thinking this could be part of the problem.
I'm using SparkFun's Base Block with OTG and Console ports (DEV-13045)
I tried connecting to my Windows machine and I was able to flash and setup the device, however an attempt to SSH or access the device via HTTP was unsuccessful.
I tried running "flashall.bat" with the "--recovery" option but it complained about "xfstk" tools being missing (I couldn't find a Windows version) so I tried running "flashall.bat" and it seemed to be successful.
I still can't seem to connect via SSH or HTTP, all I get are timeouts.
It seems to have been set up properly, it shows up in Windows, yet I cannot connect to the device at all.
Could you please send us a screenshot of the IP address of both your Edison and your computer? I would like to verify that they are on the same network.
Also, could you please check if your Edison has internet access? You can try pinging Google for that purpose.
I only have one network in my home, everything is on the 192.168.2.XXX range of IP addresses..
It has a 5GHz band and a regular band, my PC is connected via Ethernet Cable and my Macbook Pro is connected via Wifi (5GHz). I have a router that serves up DHCP and a secondary router that acts as a network extender (serving up the same WiFi network 192.168.2.XXX).
In this screenshot you can see that my PC can detect my edison, the setup process was completed successfully (although when I connected the Edison again today, the SSH and WiFi settings needed to be redone after I had done flashall.bat the night before).
You can also see that they are both on the same network and when I try to connect via SSH using PuTTY I get a timeout.
After figuring out how to connect via the CONSOLE port on my SparkFun base block I was able to get shell level access to my Edison. It seems to get an IP address, but wouldn't connect to anything nor resolve host names:
$ ping -c 3 www.google.ca
$ ping -c 3 192.168.2.1 # The IP of my router
I then updated my
/etc/resolv.confto point to Google's DNS (126.96.36.199 and 188.8.131.52) rather than the DNS provided by my ISP and restarting
wlan0(as suggested in the "Troubleshooting" section of this guide: https://software.intel.com/en-us/connecting-your-intel-edison-board-using-wifi) I was able to ping my router and Google without issues, plus I could SSH to my Edison!
I'll keep plugging away, but hopefully I don't have to connect to my Edison via console each time to fix WiFi!
So it seems that my fears are correct, each time I start my Edison I have to replace the resolv.conf with one that has either Google's DNS or the IP of my router and then restart usb0 and wlan0 to get things to work.
I'm still unable to set up the Edison.local DNS Entry nor connect via http.
I see, I'm glad to hear that you are now able connect to your Edison through an SSH connection.
The reason why you can't connect to your Edison using its IP address or edison.local (this would only work if you have the Bonjour service installed) is because there is a known issue with Edison's server on the latest images, this issue has been reported and we are currently working on it, nevertheless, there is no ETA for a fix. If you would like to use this feature, you'd have to flash an older image.
Thanks for pointing that out! Do you have any suggestions on how I can avoid restarting usb0 and wlan0 each time I power up the Edison?