9 Replies Latest reply on Jun 18, 2015 10:57 AM by DiegoV_Intel

    Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore

    ddewaele

      Hi,

       

      I followed the Loading Debian (Ubilinux) on the Edison - learn.sparkfun.com tutorial and I went through the flashall.sh script. After it finished I noticed the Edison rebooted a couple of times, and after about 10 minutes I disconnected the device. Only to find out that it didn't boot anymore.

       

      My entire boot sequence can be found here : https://gist.github.com/ddewaele/f1b13545586c78ddb545

       

      It basically halts with  "Reached target Rescue Mode.".

       

      Here are the last lines of the boot sequence:

       

      [ OK ] Found device /dev/disk/by-partlabel/home.

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

      [ OK ] Reached target Sound Card.

        Starting File System Check on /dev/disk/by-partlabel/home...

      [ OK ] Reached target System Initialization.

      [ 6.777944] systemd-fsck[166]: /dev/mmcblk0p10: recovering journal

      [ 6.790838] systemd-fsck[166]: /dev/mmcblk0p10: Superblock last mount time is in the future.

      [ 6.793319] systemd-fsck[166]: (by less than a day, probably due to the hardware clock being incorrectly set) FIXED.

      [ 6.801348] systemd-fsck[166]: /dev/mmcblk0p10: clean, 11/103584 files, 15310/413691 blocks

      [ OK ] Started File System Check on /dev/disk/by-partlabel/home.

        Mounting /home...

      [ OK ] Mounted /home.

        Starting Rescue Shell...

      [ OK ] Started Rescue Shell.

      [ OK ] Reached target Rescue Mode.

       

       

      Is there any way to recover from this ? I can interrupt the autoboot and view partitions and everything. I cannot run the flashall.sh script anymore as it fails with this:

       

       

      sudo ./flashall.sh

      Password:

      Using U-Boot target: edison-blank

      Now waiting for dfu device 8087:0a99

      Timed out while waiting for dfu device 8087:0a99

      DEBUG: lsusb

      Bus 021 Device 014: ID 05ac:8406 Apple Inc. Internal Memory Card Reader  Serial: 000000000820

      Bus 020 Device 028: ID 8087:0a9e Intel Corporation Multifunction Composite Gadget  Serial: 582175d0ceaf07c716ff241689c0a12e

      Bus 020 Device 015: ID 0403:6001 Future Technology Devices International Limited FT232R USB UART  Serial: A402F36C

      Bus 020 Device 004: ID 0a5c:4500 Broadcom Corp. BRCM20702 Hub

      Bus 020 Device 005: ID 05ac:8289 Apple Inc. Bluetooth USB Host Controller

      Bus 020 Device 003: ID 05ac:0262 Apple Inc. Apple Internal Keyboard / Trackpad

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

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

      DEBUG: dfu-util -l

      dfu-util 0.8

       

      Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.

      Copyright 2010-2014 Tormod Volden and Stefan Schmidt

      This program is Free Software and has ABSOLUTELY NO WARRANTY

      Please report bugs to dfu-util@lists.gnumonks.org

       

      Did you plug and reboot your board?

      If yes, please try a recovery by calling this script with the --recovery option

       

       

      Is there a procedure to get the Edison back up and running or is it bricked ?

        • 1. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
          DiegoV_Intel

          Hi ddewaele,

           

          I'd suggest you to try with flashall --recovery. I posted the steps to perform this method here: Re: Edison Bricked.

           

          Take a look on it, and let me know what the results are.

           

          Regards,

          Diego.

          • 2. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
            ddewaele

            I tried to do the recoverty thing, realised it was not available on mac, switched to a Windows machine, realised I had to build these libraries and probably needed a 32 bit ubuntu.

            So I gave up on that idea (I didn't bother setting up an Ubuntu to build this from the source. ) So the recovery mode only works on 32bit Ubuntu ?


            What I ended up doing was simply interrupt the U-Boot process, typing "run do_flash" , and after that I could run the flash_all.sh script in the Yocto distribution.

            After that things started working again.

            • 3. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
              DiegoV_Intel

              Hi ddewaele,

               

              Yes, it only works in Linux. I have performed it using Ubuntu 12.04 32 bit.

               

              But it's great that you resolved it!

               

              Regards,

              Diego.

              • 4. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
                ddewaele

                Yes. A friend of mine also had an issue with his Edison (his stimply hanged on "Starting kernel ...").

                Was able to fix it using the same mechanism.

                 

                Am I correct to say that as long as you're still able to access the U-Boot menu and interrupt the auto-boot that you have some way of reverting back to the stock Yocto image ?

                • 6. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
                  Bluzcat

                  Hi there. I'm running into exactly the same issue as ddewaele. I don't see an option to interrupt U-boot though. I'm using kermit to communicate with the serial port on the SparkFun console board, and by the time I've attached to it after plugging the two USB cables in, it's already 2/3 into the boot process. Does anyone have an explanation as to why the Ubilinux installation fails in this fashion? I really want to use it as I find Yocto with BusyBox insufficient for my needs. Thanks.

                  • 7. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
                    Bluzcat

                    So after bricking two Edison boards, I finally found this article:

                     

                    http://www.emutexlabs.com/forum/general-questions/12-problem-flashing-ubilinux-from-os-x

                     

                    What I did was connect the board using two USB cables to the Mac. Then load up Disk Utility, find the disk and erase it, which also creates a new partition. Once I had the new partition, I ran flashall.sh again (after modifying it according to the git-hub diff mentioned in the article above). After that, flashall.sh worked fine, and I'm now up and running on Ubilinux. The board is finally usable...

                    • 8. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
                      Bluzcat

                      I ran into one issue when trying to revive bricked board number two. It no longer shows up as a disk device. I've tried both on Raspbian Linux and Mac. The lsusb command shows this:

                      Bus 020 Device 022: ID 0403:6015 Future Technology Devices International Limited FT231X USB UART  Serial: DA01LQY5

                      I'm able to use kermit to capture the console of the board. The boot loader seems to work. However, I'm not able to re-flash it. If I do "run do_flash", it prints the following text and then blocks forever:

                       

                      boot > run do_flash

                      Saving Environment to MMC...

                      Writing to MMC(0)... done

                      GADGET DRIVER: usb_dnl_dfu

                       

                      After that GADGET DRIVER line, I never see any other output, and the device just sits there. I can reboot it and get back into the boot loader, but I don't seem to be able to re-flash it. The mmc seems to look OK to me. Here's what the 'mmc part' command reports:

                       

                      boot > mmc part

                       

                      Partition Map for MMC device 0  --   Partition Type: EFI

                       

                      Part    Start LBA    End LBA        Name

                          Attributes

                          Type GUID

                          Partition GUID

                        1    0x00000800    0x000017ff    "u-boot0"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    d117f98e-6f2c-d04b-a5b2-331a19f91cb2

                        2    0x00001800    0x00001fff    "u-boot-env0"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    25718777-d0ad-7443-9e60-02cb591c9737

                        3    0x00002000    0x00002fff    "u-boot1"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    8a4bb8b4-e304-ae48-8536-aff5c9c495b1

                        4    0x00003000    0x000037ff    "u-boot-env1"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    08992135-13c6-084b-9322-3391ff571e19

                        5    0x00003800    0x00003fff    "factory"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    333a128e-d3e3-b94d-92f4-d3ebd9b3224f

                        6    0x00004000    0x0000ffff    "panic"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    f20aa902-1c5d-294a-9177-97a513e3cae4

                        7    0x00010000    0x0001ffff    "boot"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    db88503d-34a5-3e41-836d-c757cb682814

                        8    0x00020000    0x0031ffff    "rootfs"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    012b3303-34ac-284d-99b4-34e03a2335f4

                        9    0x00320000    0x0049ffff    "update"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    faec2ecf-8544-e241-b19d-757e796da607

                      10    0x004a0000    0x00747fde    "home"

                          attrs:    0x0000000000000000

                          type:    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

                          guid:    f13a0978-b1b5-1a4e-8821-39438e24b627

                       

                      Any help on this is much appreciated! Thanks.

                      • 9. Re: Loading Debian (Ubilinux) on the Edison failed and Edison won't boot anymore
                        DiegoV_Intel

                        Hello Bluzcat,

                         

                        I'm not sure if your board can be recoverable or not after an unsuccessful attempt of installing Ubilinux. You might get a better response in the Ubilinux forum: EmutexLabs

                         

                        This thread is quite old, but now there is a new flashing tool that you could try to recover your board. It is the Flash Tool Lite and it can be downloaded from here: Intel® Edison Board Download | Intel® Developer Zone. Hopefully it works.

                         

                        Regards,

                        Diego.