Software Archive
Read-only legacy content
17060 Discussions

Edison Board Not Being Detected in Intel XDK

Josh_C_
Beginner
725 Views

This happened once before (when we were getting ready to present at the IoT Roadshow). The IoT Device list inside of the XDK does not show my Edison board, last time it happened with the Galileo. I have checked the subnet and it matches with that of my computer and I have tried manually inputting the IP (checked from the ifconfig command in SSH) to no avail.

I'm not sure how it started working after the first time it happened but I've tried everything from restarting my computer, the board, my router, the XDK and now I'm not sure what to try next.

Any help would be greatly appreciated!

0 Kudos
5 Replies
NagaVenkat_K_Intel
725 Views

Hi Josh,

What steps have u followed to add a device manually?

 

IP Address: <Device IP>

Port: 58888

 

If still facing issues try running these commands on the device, to make sure that xdk-daemon is running

 

 

  1. Select Add Manual Connection from the bottom IoT Device drop down list, a popup window launches asking for IP Address and Port.

  2. Please refer to Discovering Edison’s IP Address or Discovering Galileo’s IP Address for obtaining the IP address of your device.

  3. Once you enter the details as shown below you should be able to connect to the device.

root@edison:~# systemctl enable xdk-daemon

root@edison:~# systemctl restart xdk-daemon

Regards,

Raghu Kona

    0 Kudos
    Josh_C_
    Beginner
    725 Views

    I ran through you steps listed and still no luck. When I checked top /opt/xdk-daemon/current/ as well as /opt/xdk-daemon/main.js are both running. I also receive "Error: connect ETIMEDOUT" in the XDK after 30 seconds-ish of entering the manual information.

    0 Kudos
    NagaVenkat_K_Intel
    725 Views

    Quick question, were you able to ping to the device?? Have you tried connecting with IoT Devkit Eclipse C++ https://software.intel.com/en-us/iot/downloads. If yes, are you facing the same issues with Eclipse as well? Other option is, try installing RNDIS drivers and connect over USB. I have n't tested it though and If possible I can try it first thing tomorrow morning. If you are able to make progress with it feel free to post it over here.

     

    0 Kudos
    Josh_C_
    Beginner
    725 Views

    I just tried pinging the IP for the USB as well as the WLAN and both were unsuccessful.

    I have not tried using the IoT Eclipse Devkit but I can try that now. I have been able to connect via USB up until now and I'm on a Mac if that makes any difference. Will it still be useful to try loading the RNDIS drivers?

    0 Kudos
    Josh_C_
    Beginner
    725 Views

    My latest hunch was that in my last version of main.js that I loaded onto the board I create a NodeJS server and in that version of the code I did not add the responses.end() function. I killed main.js but then it restarted so I then deleted it and then rebooted the board. main.js didn't show up in top anymore but I'm still having the issue so that did not resolve it.

    0 Kudos
    Reply