6 Replies Latest reply on Nov 20, 2015 5:39 PM by HTinoco

    Edison - Flash lite tool fails at 69%

    jamesod

      I am attempting to flash the Yocto 2.1 image to an Edison on the Sparkfun base board using the phone flash tool lite. I am on 64-bit windows 7 pro. I start the tool, select the FlashEdison.json file, click start to flash, and then plug in the board. It gets to 69% complete and then fails. This is the log from the flash tool:

       

      06/26/15 15:40:13.425 INFO : [Port -1] Starting flash ...

      06/26/15 15:40:13.425 INFO : [Port -1] Running `Notify 'D:\Google Drive\Edison\helper\helper.html'` command

      06/26/15 15:40:13.541 INFO : Displaying 'file:///D:/Google Drive/Edison/helper/helper.html' during 42000 ms

      06/26/15 15:40:13.542 INFO : [Port -1] Command `Notify 'D:\Google Drive\Edison\helper\helper.html'` succeed

      06/26/15 15:40:13.542 INFO : [Port -1] Running `Wait for device with status dnx_fw on port -1` command

      06/26/15 15:40:24.141 INFO : [Port 2/2] Command `Wait for device with status dnx_fw on port -1` succeed

      06/26/15 15:40:24.141 INFO : [Port 2/2] Running `Notify 'Edison board plugged'` command

      06/26/15 15:40:24.323 INFO : Displaying 'Edison board plugged'' during 5000 ms

      06/26/15 15:40:24.361 INFO : [Port 2/2] Command `Notify 'Edison board plugged'` succeed

      06/26/15 15:40:24.361 INFO : [Port 2/2] Running `"xfstkFlashTool.exe" "D:\Google Drive\Edison\edison_dnx_fwr.bin" "D:\Google Drive\Edison\edison_ifwi-dbg-00.bin" "D:\Google Drive\Edison\edison_dnx_osr.bin" "D:\Google Drive\Edison\u-boot-edison.img" "0x80000007" "none" "none"` command

      06/26/15 15:40:24.385 INFO : [Port 2/2] Disabling xFSTK Misc DnX

      06/26/15 15:40:24.385 INFO : [Port 2/2] Disabling xFSTK wipe out ifwi option

      06/26/15 15:40:24.385 INFO : [Port 2/2] Using xFSTK Solo interface (new API)

      06/26/15 15:40:24.385 INFO : [Port 2/2] xFSTK Soft Fuse not set

      06/26/15 15:40:24.385 INFO : [Port 2/2] XFSTK Downloader API 1.8.0

      06/26/15 15:40:24.385 INFO : [Port 2/2] Copyright (c) 2015 Intel Corporation

      06/26/15 15:40:24.385 INFO : [Port 2/2] fwdnx -- D:\Google Drive\Edison\edison_dnx_fwr.bin

      06/26/15 15:40:24.385 INFO : [Port 2/2] fwimage -- D:\Google Drive\Edison\edison_ifwi-dbg-00.bin

      06/26/15 15:40:24.385 INFO : [Port 2/2] osdnx -- D:\Google Drive\Edison\edison_dnx_osr.bin

      06/26/15 15:40:24.385 INFO : [Port 2/2] osimage -- D:\Google Drive\Edison\u-boot-edison.img

      06/26/15 15:40:24.385 INFO : [Port 2/2] gpflags -- 0x80000007

      06/26/15 15:40:24.385 INFO : [Port 2/2] softfuse --

      06/26/15 15:40:24.395 INFO : [Port 2/2] XFSTK-STATUS--Detecting Intel Device - Attempt #0

      06/26/15 15:40:25.525 INFO : [Port 2/2] ....XFSTK-LOG--virtual bool MerrifieldDownloader::SetDevice(IGenericDevice*)

      06/26/15 15:40:25.525 INFO : [Port 2/2] Initiating download...

      06/26/15 15:40:25.526 INFO : [Port 2/2] XFSTK-STATUS--FW(Miscdnx) download is in progress ...

      06/26/15 15:40:25.527 INFO : [Port 2/2] XFSTK-STATUS--FW: Sending DnX DCFI00 ...

      06/26/15 15:40:28.392 INFO : [Port 2/2] XFSTK-STATUS--Error Code: 0 - Success

      06/26/15 15:40:28.392 INFO : [Port 2/2] XFSTK-STATUS--Firmware download completed. Continuing to OS...

      06/26/15 15:40:38.522 INFO : [Port 2/2] XFSTK-STATUS--Reconnecting to device - Attempt #1

      06/26/15 15:40:39.653 INFO : [Port 2/2] XFSTK-STATUS--POS download is in progress ...

      06/26/15 15:40:42.672 INFO : [Port 2/2] XFSTK-STATUS--Error Code: 0 - Success

      06/26/15 15:40:42.672 INFO : [Port 2/2] XFSTK-STATUS--Firmware and OS download completed.

      06/26/15 15:40:42.672 INFO : [Port 2/2] XFSTK: Transfer Completed Successfully.

      06/26/15 15:40:42.672 INFO : [Port 2/2] Success: Download of FW Completed.

      06/26/15 15:40:42.672 INFO : [Port 2/2] xfstkFlashTool exited with success

      06/26/15 15:40:42.678 INFO : [Port 2/2] Command `"xfstkFlashTool.exe" "D:\Google Drive\Edison\edison_dnx_fwr.bin" "D:\Google Drive\Edison\edison_ifwi-dbg-00.bin" "D:\Google Drive\Edison\edison_dnx_osr.bin" "D:\Google Drive\Edison\u-boot-edison.img" "0x80000007" "none" "none"` succeed

      06/26/15 15:40:42.678 INFO : [Port 2/2] Running `Wait for device with status pos on port 2/2` command

      06/26/15 15:40:59.233 INFO : [Port 2/2] Command `Wait for device with status pos on port 2/2` succeed

      06/26/15 15:40:59.233 INFO : [Port 2/2] Running `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot0" "-D" "D:\Google Drive\Edison\u-boot-edison.bin" "-t" "4096" "-d" "8087:0a99"` command

      06/26/15 15:41:00.491 INFO : [Port 2/2] Command `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot0" "-D" "D:\Google Drive\Edison\u-boot-edison.bin" "-t" "4096" "-d" "8087:0a99"` succeed

      06/26/15 15:41:00.491 INFO : [Port 2/2] Running `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env0" "-D" "D:\Google Drive\Edison\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-d" "8087:0a99"` command

      06/26/15 15:41:01.660 INFO : [Port 2/2] Command `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env0" "-D" "D:\Google Drive\Edison\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-d" "8087:0a99"` succeed

      06/26/15 15:41:01.660 INFO : [Port 2/2] Running `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env1" "-D" "D:\Google Drive\Edison\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-R" "-d" "8087:0a99"` command

      06/26/15 15:41:02.808 INFO : [Port 2/2] Command `"C:\Program Files (x86)\Intel\Phone Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env1" "-D" "D:\Google Drive\Edison\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-R" "-d" "8087:0a99"` succeed

      06/26/15 15:41:02.809 INFO : [Port 2/2] Running `Wait for device with status dnx_fw on port 2/2` command

      06/26/15 15:41:05.606 INFO : [Port 2/2] Command `Wait for device with status dnx_fw on port 2/2` succeed

      06/26/15 15:41:05.606 INFO : [Port 2/2] Running `Wait for device with status pos on port 2/2` command

      06/26/15 15:43:05.607 ERROR : [Port 2/2] Command `Wait for device with status pos on port 2/2` failed

      06/26/15 15:43:05.607 ERROR : [Port 2/2] Flash failed (Command type: Device enumeration)


      This is the serial console output during the process:

       

      ******************************

      PSH KERNEL VERSION: b0182b2b

                      WR: 20104000

      ******************************

       

       

      SCU IPC: 0x800000d0  0xfffce92c

       

       

      PSH miaHOB version: TNG.B0.VVBD.0000000c

       

       

      microkernel built 11:24:08 Feb  5 2015

       

       

      ******* PSH loader *******

      PCM page cache size = 192 KB

      Cache Constraint = 0 Pages

      Arming IPC driver ..

      Adding page store pool ..

      PagestoreAddr(IMR Start Address) = 0x04899000

      pageStoreSize(IMR Size)          = 0x00080000

       

       

      *** Ready to receive application ***

       

       

       

       

      ******************************

      PSH KERNEL VERSION: b0182b2b

                      WR: 20104000

      ******************************

       

       

      SCU IPC: 0x800000d0  0xfffce92c

       

       

      PSH miaHOB version: TNG.B0.VVBD.0000000c

       

       

      microkernel built 11:24:08 Feb  5 2015

       

       

      ******* PSH loader *******

      PCM page cache size = 192 KB

      Cache Constraint = 0 Pages

      Arming IPC driver ..

      Adding page store pool ..

      PagestoreAddr(IMR Start Address) = 0x04899000

      pageStoreSize(IMR Size)          = 0x00080000

       

       

      *** Ready to receive application ***

       

       

       

       

      U-Boot 2014.04 (Apr 29 2015 - 03:53:19)

       

       

             Watchdog enabled

      DRAM:  980.6 MiB

      MMC:   tangier_sdhci: 0

      In:    serial

      Out:   serial

      Err:   serial

      Writing to redundant MMC(0)... done

      Writing to MMC(0)... done

      Hit any key to stop autoboot:  0

      Target:ifwi

      Partitioning using GPT

      Writing GPT: success!

      Saving Environment to MMC...

      Writing to redundant MMC(0)... done

      Partitioning already done...

      Saving Environment to MMC...

      Writing to MMC(0)... done

      GADGET DRIVER: usb_dnl_dfu

      #

      DFU complete CRC32: 0xd1ef933d

      DOWNLOAD ... OK

      Ctrl+C to exit ...

      #

      DFU complete CRC32: 0x9cb56567

      DOWNLOAD ... OK

      Ctrl+C to exit ...

      #

      DFU complete CRC32: 0x9cb56567

      DOWNLOAD ... OK

      Ctrl+C to exit ...

      resetting ...

       

       

       

       

      ******************************

      PSH KERNEL VERSION: b0182b2b

                      WR: 20104000

      ******************************

       

       

      SCU IPC: 0x800000d0  0xfffce92c

       

       

      PSH miaHOB version: TNG.B0.VVBD.0000000c

       

       

      microkernel built 11:24:08 Feb  5 2015

       

       

      ******* PSH loader *******

      PCM page cache size = 192 KB

      Cache Constraint = 0 Pages

      Arming IPC driver ..

      Adding page store pool ..

      PagestoreAddr(IMR Start Address) = 0x04899000

      pageStoreSize(IMR Size)          = 0x00080000

       

       

      *** Ready to receive application ***

       

       

       

       

      U-Boot 2014.04 (Apr 29 2015 - 03:53:19)

       

       

             Watchdog enabled

      DRAM:  980.6 MiB

      MMC:   tangier_sdhci: 0

      In:    serial

      Out:   serial

      Err:   serial

      Writing to redundant MMC(0)... done

      Writing to MMC(0)... done

      Hit any key to stop autoboot:  0

      Target:blank

      Partitioning using GPT

      Writing GPT: success!

      Saving Environment to MMC...

      Writing to redundant MMC(0)... done

      Flashing already done...

      GADGET DRIVER: usb_dnl_dfu

      reading vmlinuz

      5124192 bytes read in 128 ms (38.2 MiB/s)

      Valid Boot Flag

      Setup Size = 0x00003c00

      Magic signature found

      Using boot protocol version 2.0c

      Linux kernel version 3.10.17-poky-edison+ (sys_dswci@ncsndgbuild04) #1 SMP PREEMPT Wed Aug 20 16:09:18 CEST 2014

      Building boot_params at 0x00090000

      Loading bzImage at address 00100000 (5108832 bytes)

      Magic signature found

      Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=f5ab4865aaaea6f1fff233918508524a g_multi.dev_addr=02:00:86:08:52:4a platform_mrfld_audio.audio_codec=dummy"

       

       

      Starting kernel ...

       

       

      [    0.769046] pca953x 1-0020: failed reading register

      [    0.772732] pca953x 1-0021: failed reading register

      [    0.778733] pca953x 1-0022: failed reading register

      [    0.779124] pca953x 1-0023: failed reading register

      [    1.655836] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk

      [    1.667860] pmic_ccsm pmic_ccsm: Battery Over heat exception

      [    1.676970] pmic_ccsm pmic_ccsm: Battery0 temperature outside boundary

       

       

      Welcome to Linux!

       

       

      [  OK  ] Reached target Remote File Systems.

               Expecting device dev-ttyMFD2.device...

               Expecting device dev-mmcblk1p1.device...

      [  OK  ] Reached target Paths.

      [  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.

      [  OK  ] Reached target Swap.

      [  OK  ] Set up automount boot.automount.

      [  OK  ] Set up automount home.automount.

      [  OK  ] Created slice Root Slice.

      [  OK  ] Listening on Delayed Shutdown Socket.

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

      [  OK  ] Listening on Syslog Socket.

      [  OK  ] Listening on udev Kernel Socket.

      [  OK  ] Listening on udev Control Socket.

      [  OK  ] Created slice User and Session Slice.

      [  OK  ] Listening on Journal Socket.

      [  OK  ] Created slice System Slice.

               Starting Remount Root and Kernel File Systems...

               Starting Load Kernel Modules...

               Starting udev Coldplug all Devices...

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

               Mounting Debug File System...

               Starting Apply Kernel Variables...

               Mounting POSIX Message Queue File System...

      [  OK  ] Created slice system-getty.slice.

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

               Starting Journal Service...

      [  OK  ] Started Journal Service.

      [  OK  ] Reached target Slices.

               Mounting Temporary Directory...

      [  OK  ] Set up automount factory.automount.

      [  OK  ] Mounted POSIX Message Queue File System.

      [  OK  ] Mounted Debug File System.

      [  OK  ] Mounted Temporary Directory.

      [  OK  ] Started Remount Root and Kernel File Systems.

      [  OK  ] Started Create list of required static device nodes ...current kernel.

      [    4.391930] g_multi: Unknown parameter `ethernet_config'

      [  OK  ] Started Apply Kernel Variables.

      [FAILED] Failed to start Load Kernel Modules.

      See 'systemctl status systemd-modules-load.service' for details.

      [  OK  ] Started udev Coldplug all Devices.

               Mounting FUSE Control File System...

               Mounting Configuration File System...

               Starting Create Static Device Nodes in /dev...

               Starting Load/Save Random Seed...

      [  OK  ] Mounted Configuration File System.

      [  OK  ] Mounted FUSE Control File System.

      [  OK  ] Started Create Static Device Nodes in /dev.

      [  OK  ] Started Load/Save Random Seed.

               Starting udev Kernel Device Manager...

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

               Mounting /var/volatile...

      [  OK  ] Mounted /var/volatile.

      [  OK  ] Started udev Kernel Device Manager.

      [  OK  ] Reached target Local File Systems.

               Starting Trigger Flushing of Journal to Persistent Storage...

               Starting Create Volatile Files and Directories...

      [  OK  ] Started Create Volatile Files and Directories.

      [  OK  ] Started Trigger Flushing of Journal to Persistent Storage.

      [  OK  ] Found device /dev/ttyMFD2.

               Starting Network Time Synchronization...

               Starting Update UTMP about System Boot/Shutdown...

      [  OK  ] Created slice system-systemd\x2drfkill.slice.

               Starting Load/Save RF Kill Switch Status of rfkill2...

               Starting Load/Save RF Kill Switch Status of rfkill0...

               Starting Load/Save RF Kill Switch Status of rfkill1...

      [  OK  ] Started Network Time Synchronization.

      [  OK  ] Started Load/Save RF Kill Switch Status of rfkill2.

      [  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.

      [  OK  ] Started Load/Save RF Kill Switch Status of rfkill1.

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

      [  OK  ] Reached target Sound Card.

      [  OK  ] Reached target System Initialization.

      [  OK  ] Reached target Timers.

      [  OK  ] Listening on D-Bus System Message Bus Socket.

      [  OK  ] Listening on sshd.socket.

      [  OK  ] Reached target Sockets.

      [  OK  ] Reached target Basic System.

               Starting Watchdog sample daemon...

      [  OK  ] Started Watchdog sample daemon.

               Starting USB Ethernet gadget...

               Starting Crashlog service...

      [  OK  ] Started Crashlog service.

               Starting Edison RM button handler...

      [  OK  ] Started Edison RM button handler.

               Starting Kernel Logging Service...

      [  OK  ] Started Kernel Logging Service.

               Starting Bluetooth rf kill event daemon...

      [  OK  ] Started Bluetooth rf kill event daemon.

               Starting Daemon to handle arduino sketches...

      [  OK  ] Started Daemon to handle arduino sketches.

               Starting Daemon to reset sketches...

      [  OK  ] Started Daemon to reset sketches.

               Starting System Logging Service...

      [  OK  ] Started System Logging Service.

               Starting Login Service...

               Starting Permit User Sessions...

               Starting D-Bus System Message Bus...

      [  OK  ] Started D-Bus System Message Bus.

               Starting Network Service...

      [  OK  ] Started Permit User Sessions.

      [  OK  ] Started Network Service.

      [  OK  ] Started USB Ethernet gadget.

      [  OK  ] Started Login Service.

      [  OK  ] Reached target Network.

               Starting Mosquitto - lightweight server implementati...SN protocols...

      [  OK  ] Started Mosquitto - lightweight server implementatio...T-SN protocols.

               Starting Zero-configuration networking...

      [  OK  ] Started Zero-configuration networking.

               Starting Intel_XDK_Daemon...

      [  OK  ] Started Intel_XDK_Daemon.

               Starting Network Name Resolution...

      [  OK  ] Created slice system-systemd\x2dfsck.slice.

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

               Starting Getty on tty1...

      [  OK  ] Started Getty on tty1.

               Starting Serial Getty on ttyMFD2...

      [  OK  ] Started Serial Getty on ttyMFD2.

      [  OK  ] Reached target Login Prompts.

               Starting HSU runtime pm service...

      [  OK  ] Started Network Name Resolution.

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

      [  OK  ] Started HSU runtime pm service.

      [    9.934740] systemd-fsck[230]: /dev/mmcblk0p5: clean, 13/128 files, 40/1024 blocks

               Mounting /factory...

      [  OK  ] Mounted /factory.

       

       

      Poky (Yocto Project Reference Distro) 1.6 edison ttyMFD2

       

      At this point I can login using root, and I receive this output:

       

      edison login: root

      [   18.164801] systemd-fsck[332]: fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p10

      [   18.167264] systemd-fsck[332]: /dev/mmcblk0p10:

      [   18.169266] systemd-fsck[332]: The superblock could not be read or does not describe a correct ext2

      [   18.171714] systemd-fsck[332]: filesystem.  If the device is valid and it really contains an ext2

      [   18.174870] systemd-fsck[332]: filesystem (and not swap or ufs or something else), then the superblock

      [   18.183180] systemd-fsck[332]: is corrupt, and you might try running e2fsck with an alternate superblock:

      [   18.184210] systemd-fsck[332]: e2fsck -b 8193 <device>

      No directory, logging in with HOME=/

      root@edison:/# reboot

      -sh: reboot: not found

       

      I can't reboot. I am stuck here, and not sure how to proceed. Any help would be appreciated.

       


        • 1. Re: Edison - Flash lite tool fails at 69%
          JTilghman

          You might try using the method I had to use to unbrick my edison.

           

          EDISON BRICKED ! MMC 2nd Partition with FWI erased, can this be fixed ?

           

          It rescued mine.

           

          JT

          • 2. Re: Edison - Flash lite tool fails at 69%
            CMata_Intel

            Hi jamesod ;

             

            One thing we could try is with the flashall script. Take a look at this thread where is explained the process to follow in different OS. Let me know the outcome of it. Also which OS are you using?

             

             

            Regards;

            CMata

            • 3. Re: Edison - Flash lite tool fails at 69%
              jamesod

              I tried to run flashall.bat, and this failed while rebooting to apply partition changes. Here is the output from the Windows cmd window:

               

               

              D:\Google Drive\Edison_Image_20150626\edison-image-ww18-15>flashall.bat

              Using U-boot target: edison-blankrndis

              Now waiting for dfu device 8087:0a99

              Please plug and reboot the board

              Dfu device found

              Flashing IFWI

              Download        [=========================] 100%      4194304 bytes

              Download done.

              Download        [=========================] 100%      4194304 bytes

              Download done.

              Flashing U-Boot

              Download        [=========================] 100%       245760 bytes

              Download done.

              Flashing U-Boot Environment

              Download        [=========================] 100%        65536 bytes

              Download done.

              Flashing U-Boot Environment Backup

              Download        [=========================] 100%        65536 bytes

              Download done.

              Rebooting to apply partiton changes

              Dfu device not found Timeout

              Did you plug and reboot your board?

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

               

              I was watching the output on the serial console at this time, and the Edison just booted like above. I guessed that something was missed to make the Edison ready to communicate with my computer. So I decided to start over with the Flash tool lite. It got hung up again at 69%, and I saw the same thing in the serial console. I restarted the Edison with the power button on the Sparkfun board, and this time I interrupted the boot and entered the command run do_flash.

               

              boot > run do_flash

              Saving Environment to MMC...

              Writing to MMC(0)... done

              GADGET DRIVER: usb_dnl_dfu

               

              After this the flash took off again and finished 100%. After another reboot I could see that it had loaded the correct version, but the Edison drive did not show up on my Windows machine. So I tried again to run flashall.bat. This again failed at "Rebooting to apply partition changes." Strangely though, I rebooted the Edison again and the drive appeared.

               

              So, I think I have a working image now.... but the roundabout way I went about this bothers me. Any ideas on what happened? This was a brand new Edison fresh out of the box. The first thing I tried to do was flash the new firmware so I could start working with the MCU. I need to figure out what happened here because this killed so much time, and I will most likely be flashing dozens of these at a time pretty soon.

              • 4. Re: Edison - Flash lite tool fails at 69%
                Ferda

                Hello jamesod,

                 

                I have similar problem on Xubuntu 14.04. I think that this is due to USB device (Edison) is taken and locked by system and Flash Lite Tool can't continue (some bad timing).

                I resolved this by next steps:

                1. When flashing stops at 69% and when system automount USB Edison device, then disconnect micro USB from Edison (Edison must be powered by this micro USB, so power it off).

                2. Reconnect micro USB to Edison (power it on). Must be done before Flash Tool timeout.

                3. Then, for me, flashing continue up to 100%.


                During the second or next flashing of own image usually all complete at once up to 100%.

                 

                I hope this helps.

                1 of 1 people found this helpful
                • 5. Re: Edison - Flash lite tool fails at 69%
                  CMata_Intel

                  Hi jamesod

                   

                  I think that the first time you were able to flash it probably it had a working image too but you wouldn't able to see the Edison drive because of an issue with a cable/port or because the board hasn't finished to boot in that moment or probably what it needed was to unplug and plug the board to the power supply (this happens to me after flashing the board with the flashall script, I have to power down and power up the board).

                  In future, you can try with:

                  1. Using another OS.

                  2. Changing the timeout for rootfs in the FlashEdison.json.

                   

                  Regards;

                  CMata

                  • 6. Re: Edison - Flash lite tool fails at 69%
                    HTinoco

                    Thank you !

                    I've been fighting with 2 of these units for 2 days, until I found your workaround

                    Poor software development from Intel