6 Replies Latest reply on Jul 24, 2015 9:16 AM by JamesMoore

    Corrupted image on Intel Edison

    DangerousTim

      Ive got an Intel Edison on an arduino Breakout board. Recently i wanted to reflash the image on the edison... so i deleted all the files by clicking on "EDISION :F" in "My Computer" and delete all files.However during the deletion the edison got disconnected.

      When i reconnect the edison to the computer and opne a putty session, the "ready to receive applicaation, and "USB GADGET DRIVER: dfl...." comes, but after the "welcome to Linux" message i see several messages showing that some processes have failed.. for eg. the last one is...

      [FAILED] Failed to start Login Service...

       

      then after that this messgae

      [***   ] A start job is running for dev-ttyMFD2.device (1min 6s / 1min 30s)

       

      after which it attempts to reboot again..

      I tried to factory reset the edison... stopped autoboot and put this

      <boot> run do_ota

       

      the problem doesnt go...

      i also dont see the Edison Folder in the My Computer

       

      PLEASE HELP! X(

       

      Heres the entire message...

      Welcome to Linux!

       

       

               Expecting device dev-ttyMFD2.device...

      [  OK  ] Reached target Paths.

      [  OK  ] Reached target Swap.

      [  OK  ] Created slice Root Slice.

      [  OK  ] Created slice User and Session Slice.

      [  OK  ] Listening on Delayed Shutdown Socket.

      [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.

      [  OK  ] Listening on udev Control Socket.

      [  OK  ] Listening on udev Kernel Socket.

      [  OK  ] Listening on Journal Socket.

      [  OK  ] Created slice System Slice.

      [  OK  ] Created slice system-serial\x2dgetty.slice.

               Starting udev Coldplug all Devices...

               Starting Apply Kernel Variables...

               Mounting POSIX Message Queue File System...

               Mounting Debug File System...

               Starting Create list of required static device nodes...rrent kernel...

               Mounting Configuration File System...

               Mounting FUSE Control File System...

               Starting Journal Service...

      [  OK  ] Started Journal Service.

      [  OK  ] Reached target Slices.

               Starting Load/Save Random Seed...

               Mounting Temporary Directory...

      [FAILED] Failed to start udev Coldplug all Devices.

      See 'systemctl status systemd-udev-trigger.service' for details.

      [  OK  ] Started Apply Kernel Variables.

      [FAILED] Failed to mount POSIX Message Queue File System.

      See 'systemctl status dev-mqueue.mount' for details.

      [FAILED] Failed to mount Debug File System.

      See 'systemctl status sys-kernel-debug.mount' for details.

      [FAILED] Failed to start Create list of required static devic...current kernel.

      See 'systemctl status kmod-static-nodes.service' for details.

      [FAILED] Failed to mount Configuration File System.

      See 'systemctl status sys-kernel-config.mount' for details.

      [FAILED] Failed to mount FUSE Control File System.

      See 'systemctl status sys-fs-fuse-connections.mount' for details.

      [FAILED] Failed to start Load/Save Random Seed.

      See 'systemctl status systemd-random-seed.service' for details.

      [FAILED] Failed to mount Temporary Directory.

      See 'systemctl status tmp.mount' for details.

               Starting Create Static Device Nodes in /dev...

      [FAILED] Failed to start Create Static Device Nodes in /dev.

      See 'systemctl status systemd-tmpfiles-setup-dev.service' for details.

               Starting udev Kernel Device Manager...

      [  OK  ] Reached target Local File Systems (Pre).

      [  OK  ] Reached target Local File Systems.

               Starting Trigger Flushing of Journal to Persistent Storage...

               Starting Create Volatile Files and Directories...

      [  OK  ] Started udev Kernel Device Manager.

      [FAILED] Failed to start Trigger Flushing of Journal to Persistent Storage.

      See 'systemctl status systemd-journal-flush.service' for details.

      [FAILED] Failed to start Create Volatile Files and Directories.

      See 'systemctl status systemd-tmpfiles-setup.service' for details.

               Starting Update UTMP about System Boot/Shutdown...

      [  OK  ] Started Update UTMP about System Boot/Shutdown.

      [  OK  ] Reached target System Initialization.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

      [DEPEND] Dependency failed for D-Bus System Message Bus.

      [  OK  ] Reached target Sockets.

      [  OK  ] Reached target Timers.

      [  OK  ] Reached target Basic System.

               Starting Login Service...

               Starting Permit User Sessions...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

      [  OK  ] Started Permit User Sessions.

               Stopping Login Service...

      [  OK  ] Stopped Login Service.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

               Starting Login Service...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

               Stopping Login Service...

      [  OK  ] Stopped Login Service.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

               Starting Login Service...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

               Stopping Login Service...

      [  OK  ] Stopped Login Service.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

               Starting Login Service...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

               Stopping Login Service...

      [  OK  ] Stopped Login Service.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

               Starting Login Service...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

               Stopping Login Service...

      [  OK  ] Stopped Login Service.

      [FAILED] Failed to listen on D-Bus System Message Bus Socket.

      See 'systemctl status dbus.socket' for details.

               Starting Login Service...

      [FAILED] Failed to start Login Service.

      See 'systemctl status systemd-logind.service' for details.

      [***   ] A start job is running for dev-ttyMFD2.device (1min 7s / 1min 30s)

        • 1. Re: Corrupted image on Intel Edison
          JPMontero_Intel

          Hi DangerousTim,

           

          Have you tried using ./flashall.sh --recovery method? You could try it in case you haven’t, once the recovery is done you should be able to flash the board normally with ./flashall.sh. Keep in mind you need to install dfu-util. Note that for this method you don’t need to put the image files in the Edison drive, this message is a guide on how to do it. I hope it works for you, let me know if you get an error during the process or if it works successfully.

           

          Regards,
          JPMontero_Intel

          • 2. Re: Corrupted image on Intel Edison
            DangerousTim

            Thanks for the prompt response! :)

            I really don't know how exactly you do that :-/... Could you elaborate or show me a guide or something? Where to install dfu-util? Where's this flashall.sh???

            Thing is I can't login... I can though stop autoboot to type in some commands ( I think its called u-boot). This prompt appears : <boot>

             

            What commands should I put and where?

            Thanks in advance...

            • 3. Re: Corrupted image on Intel Edison
              DangerousTim

              Yes I saw that guide... I didn't understand where to pit those commands... Could you explain it in the simplest way possible? Because it really went bonkers over my head :-L

              • 4. Re: Corrupted image on Intel Edison
                JPMontero_Intel

                Hi DangerousTim,

                 

                Sure no problem. The flashall.sh and flashall.bat are in Edison Yocto complete image, and the steps are the following:

                 

                1. Download Edison Yocto complete image in this site.
                2. Now you need to download dfu-utils:
                  1. For Windows you can download it from vjou's message. Then save the file in the same folder you extracted Edison image.
                  2. For Mac type in the terminal brew install dfu-util coreutils gnu-getopt, like intel_dan suggested in Re: How to recover Edison firmware.
                  3. For Ubuntu type in the terminal sudo apt-get install dfu-util
                3. Run flashall.sh (for Linux and Mac) or flashall.bat (for Windows). To run this you need to get into the terminal into the folder of Edison image and type ./flashall.sh or flashall.bat for Windows.

                 

                If this does not work you might need to run flashall.sh –recovery first. For this procedure you need xfstk. I’ve tried this method only in Linux by using the source and steps provided by David_J_Hunt in this post Building xFSTK on Ubuntu 14.04 (32-bit) for flashing Edison . Once you have done this you should be able to run ./flashall.sh --recovery without any errors. Then when ./flashall.sh –recovery is finished you should be able to use ./flashall.sh. Let me know if this works for you.

                 

                Regards,
                JPMontero_Intel

                1 of 1 people found this helpful
                • 5. Re: Corrupted image on Intel Edison
                  CMata_Intel

                  Hi DangerousTim,

                   

                  Did you tried the JPMontero's suggestion? Were you able to flash your board?

                   

                  Regards;

                  CMata

                  • 6. Re: Corrupted image on Intel Edison
                    JamesMoore

                    You might add a check to flashall.sh to make sure you're not trying to run it from the mounted Edison drive. 

                     

                    In hindsight, it's obvious that was my problem, but at the time the failure was mysterious - you'll get complaints from the shell like this:

                     

                    cd /Volumes/EDISON

                    bash flashall.sh

                    find: .: Invalid argument


                    Since . is (at least on OSX) probably going to be invalid halfway through the script.