1 2 Previous Next 15 Replies Latest reply on Feb 18, 2015 3:33 PM by cobster

    XDK won't connect to edison

    cobster

      I can't SSH (timed out while waiting for handshake), but I can use the serial terminal.

      I tried:

      systemctl enable xdk-daemon

      systemctl restart xdk-daemon

      but the xdk-whitelist command is not found.

      Does this mean the new firmware failed to flash properly? How can I tell what version is running?

      It is also not receiving the first character that I type, as if it is waking from sleep when the character comes in, and the network connection over usb0 keeps connecting and disconnecting spontaneously.

      XDK is running in Linux.

        • 1. Re: XDK won't connect to edison
          CMata_Intel

          Hi cobster

           

          In order to add the IP you need to use:

          root@edison:~# systemctl enable xdk-daemon
          root@edison:~# systemctl restart xdk-daemon
          root@edison:~# xdk-whitelist --add XXX.XXX.XX.XX
          

          Do you have your board connected to WiFi?

           

          With the command:

          root@edison:~# configure_edison --version
          

          If you have as outcome 120, that it's the latest one.

           

          About:

          It is also not receiving the first character that I type....

          Is this happening with the board connected with cable or SSH?

          In order to avoid problems with usb0, try running

          root@edison:~# ifconfig usb0 down
          

           

          Regards;

          CMata

          • 2. Re: XDK won't connect to edison
            intel_dan

            Sounds like you may still have an older firmware version. (the issue with the first character being dropped was an issue in earlier firmwares).

             

            What is the output of  'uname -a' ? 

             

            Also, If you are on the latest Edison image (R2 beta ww05-15) (Intel® Edison Boards and Compute Modules — Software Downloads) then there is no need to add any ip to the whitelist because the whitelisting has been dropped in favor of a secure connection (using the password you set when using configure_edison)

             

            Also, note the work around (Re: ECONNREFUSED from XDK)) to a connection issue when using the latest Edison image (ww05-15) and the current XDK IoT Edition (0128)

            • 3. Re: XDK won't connect to edison
              cobster

              I just tried connecting through wifi after running configure_edison and it told me that the daemon was out of date.

              The first thing I did with the board was to download the ww05-15 image and I followed the procedure to flash it, but I suspect it is still running the old one somehow.

              Perhaps I copied the files to the wrong partition? The howto said there would be two mounted on my desktop, but I only saw one: /media/Edison

               

              Here is the output of uname -a:

               

              root@edison:~# uname -a

              Linux edison 3.10.17-poky-edison+ #1 SMP PREEMPT Wed Aug 20 16:09:18 CEST 2014 i686 GNU/Linux

              • 4. Re: XDK won't connect to edison
                cobster

                I configured the wifi and it connected, but warned that I have and old xdk daemon.

                When I try to build, I get many "dns service error"

                 

                root@edison:~# xdk-whitelist --add 192.168.1.11

                -sh: xdk-whitelist: not found

                root@edison:~# uname -a

                Linux edison 3.10.17-poky-edison+ #1 SMP PREEMPT Wed Aug 20 16:09:18 CEST 2014 i686 GNU/Linux

                 

                My configure_edison doesn't seem to have the --version option:

                root@edison:~# configure_edison --version

                Incorrect input. Redirecting to --help

                • 5. Re: XDK won't connect to edison
                  intel_dan

                  You appear to be on an early version of the linux image. The ww05-15 image has a build date of February 2015 (the image you are running is from August 2014). Plus that fact that your are seeing the "first character" serial bug, and configure_edison is missing options all point to an early image.

                  • 6. Re: XDK won't connect to edison
                    intel_dan

                    I recommend trying the second set of flashing instructions located here Intel® Edison Boards and Compute Modules — Flashing Intel® Edison (wired) - Linux*

                     

                            Alternate Flashing Method:

                    1. Install dfu-util which is a open source program that implements USB DFU (USB Device Firmware Upgrade) protocol
                      1. sudo apt-get install dfu-util
                    2. Extract the contents of the pre-built Edison image
                    3. Run the script and then connect the Edison board using USB2.0 cable
                      1. ./flashall.sh
                      2. NOTE: the script can take up to 5 minutes to complete the flashing

                     

                     

                      Note: you may have to run ./flashall.sh --recovery  and then run ./flashall.sh if the above directions do not seem to work

                    • 7. Re: XDK won't connect to edison
                      cobster

                      I've tried the flashall.sh method too.

                      It doesn't say that it fails, but I'm still getting the August date for "uname -a".

                      I checked that the creation date of the edison-image-edison.ext4 file is in fact Feb 17 2015.

                       

                      qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$ ./flashall.sh

                      Using U-Boot target: edison-blankcdc

                      Now waiting for dfu device 8087:0a99

                      Please plug and reboot the board

                      Flashing IFWI

                      Flashing U-Boot

                      Flashing U-Boot Environment

                      Flashing U-Boot Environment Backup

                      Rebooting to apply partition changes

                      Now waiting for dfu device 8087:0a99

                      Flashing boot partition (kernel)

                      Flashing rootfs, (it can take up to 5 minutes... Please be patient)

                      Rebooting

                      U-boot & Kernel System Flash Success...

                      Your board needs to reboot to complete the flashing procedure, please do not unplug it for 2 minutes.

                      qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$

                       

                      To run flashall.sh --recovery, I built and installed xfstk (and cmake).

                      I get the following:

                       

                       

                      qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$ ./flashall.sh --recovery

                      Starting Recovery mode

                      Please plug and reboot the board

                      Flashing IFWI

                       

                       

                      XFSTK Downloader Solo 0.0.0

                      Copyright (c) 2015 Intel Corporation

                      Build date and time: Feb 17 2015 22:34:38

                       

                       

                      Intel SoC Device Detection Failed: Attempt #0

                      Intel SoC Device Detection Failed: Attempt #1

                      Intel SoC Device Detection Failed: Attempt #2

                      Intel SoC Device Detection Failed: Attempt #3

                      Intel SoC Device Detection Failed: Attempt #4

                      Intel SoC Device Detection Failed: Attempt #5

                      Intel SoC Device Detection Failed: Attempt #6

                      Intel SoC Device Detection Failed: Attempt #7

                      Intel SoC Device Detection Failed: Attempt #8

                      Intel SoC Device Detection Failed: Attempt #9

                      .Intel SoC Device Detection Found

                      Parsing Commandline....

                      Registering Status Callback....

                      .Initiating Download Process....

                      .....................................XFSTK-STATUS--Reconnecting to device - Attempt #1

                      ...................................XFSTK-STATUS--Reconnecting to device - Attempt #2

                      XFSTK-STATUS--Reconnecting to device - Attempt #3

                      XFSTK-STATUS--Reconnecting to device - Attempt #4

                      XFSTK-STATUS--Reconnecting to device - Attempt #5

                      XFSTK-STATUS--Reconnecting to device - Attempt #6

                      XFSTK-STATUS--Reconnecting to device - Attempt #7

                      XFSTK-STATUS--Reconnecting to device - Attempt #8

                      XFSTK-STATUS--Reconnecting to device - Attempt #9

                      XFSTK-STATUS--Reconnecting to device - Attempt #10

                      XFSTK-STATUS--Reconnecting to device - Attempt #11

                      XFSTK-STATUS--Reconnecting to device - Attempt #12

                      XFSTK-STATUS--Reconnecting to device - Attempt #13

                      XFSTK-STATUS--Reconnecting to device - Attempt #14

                      XFSTK-STATUS--Reconnecting to device - Attempt #15

                      XFSTK-STATUS--Reconnecting to device - Attempt #16

                      XFSTK-STATUS--Reconnecting to device - Attempt #17

                      XFSTK-STATUS--Reconnecting to device - Attempt #18

                      XFSTK-STATUS--Reconnecting to device - Attempt #19

                      XFSTK-STATUS--Reconnecting to device - Attempt #20

                      XFSTK-STATUS--Reconnecting to device - Attempt #21

                      Xfstk tool error

                      DEBUG: lsusb

                      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                      Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                      Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

                      Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

                      Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

                      Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub

                      Bus 003 Device 003: ID 04b8:0818 Seiko Epson Corp. Stylus CX3700/CX3800/DX3800

                      Bus 001 Device 071: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

                      Bus 001 Device 075: ID 8087:0a9e Intel Corp.

                      DEBUG: dfu-util -l

                      dfu-util 0.5

                       

                       

                      (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.

                      (C) 2010-2011 Tormod Volden (DfuSe support)

                      This program is Free Software and has ABSOLUTELY NO WARRANTY

                       

                       

                      dfu-util does currently only support DFU version 1.0

                       

                       

                      qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$

                      • 8. Re: XDK won't connect to edison
                        intel_dan

                        Hmm try doing a sudo/running as root, and see if that make a difference. The documentation for dfu-util says

                         

                        "Also, please remember to execute the dfu-util command with sufficient privileges (ie. root) -- you will need complete control over the usb bus."

                         

                        so try the following:

                         

                        1. run 'sudo ./flashall --recovery'

                        2. plugin Edison to USB (you should get output/messages from flashall)

                        3. When flashall --recovery is complete, leave Edison plugged in

                        4. Run 'sudo ./flashall'  (this should take ~5 minutes)

                        • 9. Re: XDK won't connect to edison
                          cobster

                          OK, running as sudo allowed flashall.sh --recovery  to succeed. (correct output shown below), Thanks.

                          I now have the latest firmware.

                          No more dropped characters in the serial term, however iotxdk still won't connect except over serial. (I tried running xdk with sudo as well).

                           

                          root@edison:~# systemctl enable xdk-daemon

                          root@edison:~# systemctl restart xdk-daemon

                          root@edison:~# xdk-whitelist --add 192.168.1.11

                           

                          IP address already in whitelist!

                           

                          root@edison:~# uname -a

                          Linux edison 3.10.17-poky-edison+ #1 SMP PREEMPT Fri Jan 30 14:16:35 CET 2015 i686 GNU/Linux

                          root@edison:~#



                          Whenever the edison is plugged in, Ubuntu keeps popping up messages "Wired network disconnected" every few minutes. It apparently keeps disconnecting and reconnecting spontaneously.

                          Maybe I have a problem with my Ubuntu network setup. Any ideas?




                          Here is the correct flashall output for future reference:


                          qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$ sudo ./flashall.sh --recovery

                          Starting Recovery mode

                          Please plug and reboot the board

                          Flashing IFWI

                           

                           

                          XFSTK Downloader Solo 0.0.0

                          Copyright (c) 2015 Intel Corporation

                          Build date and time: Feb 17 2015 22:34:38

                           

                           

                          Intel SoC Device Detection Failed: Attempt #0

                          Intel SoC Device Detection Failed: Attempt #1

                          Intel SoC Device Detection Failed: Attempt #2

                          Intel SoC Device Detection Failed: Attempt #3

                          Intel SoC Device Detection Failed: Attempt #4

                          Intel SoC Device Detection Failed: Attempt #5

                          Intel SoC Device Detection Failed: Attempt #6

                          Intel SoC Device Detection Failed: Attempt #7

                          Intel SoC Device Detection Failed: Attempt #8

                          Intel SoC Device Detection Failed: Attempt #9

                          .Intel SoC Device Detection Found

                          Parsing Commandline....

                          Registering Status Callback....

                          .Initiating Download Process....

                          .....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................XFSTK-STATUS--Reconnecting to device - Attempt #1

                          ................................................................................................................................Recovery Success...

                          You can now try a regular flash

                          qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$ sudo ./flashall.sh

                          Using U-Boot target: edison-blankcdc

                          Now waiting for dfu device 8087:0a99

                          Please plug and reboot the board

                          Flashing IFWI

                          ##################################################] finished!

                          ##################################################] finished!

                          Flashing U-Boot

                          ##################################################] finished!

                          Flashing U-Boot Environment

                          ##################################################] finished!

                          Flashing U-Boot Environment Backup

                          ##################################################] finished!

                          Rebooting to apply partition changes

                          Now waiting for dfu device 8087:0a99

                          Flashing boot partition (kernel)

                          ##################################################] finished!

                          Flashing rootfs, (it can take up to 5 minutes... Please be patient)

                          ##################################################] finished!

                          Rebooting

                          U-boot & Kernel System Flash Success...

                          Your board needs to reboot to complete the flashing procedure, please do not unplug it for 2 minutes.

                          qingping@qingping-HP-Compaq-Elite-8300-CMT:~/intel/edison_image$

                          • 10. Re: XDK won't connect to edison
                            intel_dan

                            Did you run 'configure_edison --setup' ?  How are you trying to connect to the Edison via wifi? via usb/virtual ethernet?  Does your device appear in the IoT device dropdown in the Intel XDK IoT Edition?

                            • 11. Re: XDK won't connect to edison
                              cobster

                              I hadn't run configure_edison yet.

                              The edison was listed as 192.168.2.15 in the dropdown until I ran configure_edison --setup.

                              Now it is not listed.

                              However I can finally connect to it over wifi by manually entering its newly assigned wifi ip address.

                              I have the Blink example working at last!

                               

                              I'm going to say it is resolved, but I wish I knew why it wouldn't work over the usb/virtual ethernet.

                              1 of 1 people found this helpful
                              • 12. Re: XDK won't connect to edison
                                cobster

                                The following message is continually spouted into the  IoT XDK console. Maybe it is a clue to why the usb/ethernet is not working?

                                 

                                at SocketWatcher.MDNSService.self.watcher.callback (/opt/xdk-daemon/current/node_modules/mdns2/lib/mdns_service.js:17:38)uncaughtException occured: Error: dns service error: bad reference

                                • 13. Re: XDK won't connect to edison
                                  intel_dan

                                  That is a known bug (will be fixed in the next release). From the serial/ssh console run 'systemctl restart xdk-daemon'  or just restart the Edison board.

                                  • 14. Re: XDK won't connect to edison
                                    intel_dan

                                    Once you restart the xdk-daemon/board, you should see the usb/ethernet device again. What happens if you manually try to connect to 192.168.2.15?

                                    1 2 Previous Next