Community
cancel
Showing results for 
Search instead for 
Did you mean: 
CBrou1
New Contributor I
1,553 Views

Failed image upgrade - how to recover ?

Jump to solution

I was commissioning a new Intel Edison with a windows PC and the sparkfun base circuit.

At first all was fine, as soon as I connected the two USB ports, I saw the Edison as a drive and got access to the shell (the drivers were already installed on my PC).

I was able to configure the edison name and wifi. I realized the image was not current and started the integrated installer to upgrade it. At some point the installer asked to disconnect the USB port and reconnect it. The process continued with the PC making several times the sound of a device connecting/disconnecting. At some point the installet terminated indicating a failure to upgrade.

Now I am stucked and wonder how to recover.

  • The edison is not visible anymore as a drive on the PC.
  • The console shell access still works but I received a series of system warnings when I log in (see hereunder)
  • Wifi does not work anymore. If i try to run Configure_edison -w , no network is found and I get the message sh: wpa_cli: not foundft
  • On the PC device manager I see the Intel SOC - DnX driver and the serial driver. Nothing else pertaining to the Edison.

In other words, the only remaining active link between the Edison and the outside world seems to be serial SSH .

Here is what I see when I log to the root:

Poky (Yocto Project Reference Distro) 1.6 Eduardo ttyMFD2

Eduardo login: root

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

[ 108.190719] systemd-fsck[1206]: /dev/mmcblk0p10:

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

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

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

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

[ 108.203491] systemd-fsck[1206]: e2fsck -b 8193

No directory, logging in with HOME=/

root@Eduardo:

Tags (1)
1 Solution
Pedro_M_Intel
Employee
435 Views

Hello CABrouwers,

I've experienced something similar a few months back. I had Edison's drivers installed on my PC and for some reason the integrated installer had a strange behavior that time and uninstalled them. So, something similar might be happening to you. In that case I suggest you to install them manually.

The Edison's standalone driver can be found in http://downloadmirror.intel.com/24909/eng/IntelEdisonDriverSetup1.2.1.exe here and the serial driver can be found in http://www.ftdichip.com/Drivers/D2XX.htm D2XX Direct Drivers.

After installing both drivers I suggest you to try to recover your board by flashing the https://software.intel.com/en-us/iot/hardware/edison/downloads latest image with https://software.intel.com/en-us/articles/flash-tool-lite-user-manual Flash Tool Lite or /docs/DOC-25154 flashall.

Peter.

View solution in original post

3 Replies
Pedro_M_Intel
Employee
436 Views

Hello CABrouwers,

I've experienced something similar a few months back. I had Edison's drivers installed on my PC and for some reason the integrated installer had a strange behavior that time and uninstalled them. So, something similar might be happening to you. In that case I suggest you to install them manually.

The Edison's standalone driver can be found in http://downloadmirror.intel.com/24909/eng/IntelEdisonDriverSetup1.2.1.exe here and the serial driver can be found in http://www.ftdichip.com/Drivers/D2XX.htm D2XX Direct Drivers.

After installing both drivers I suggest you to try to recover your board by flashing the https://software.intel.com/en-us/iot/hardware/edison/downloads latest image with https://software.intel.com/en-us/articles/flash-tool-lite-user-manual Flash Tool Lite or /docs/DOC-25154 flashall.

Peter.

View solution in original post

CBrou1
New Contributor I
435 Views

Thanks. I tried what you suggested but with not luck. After deleting and re-installing the driver, i still can't see the edison as a driver. Also, i think i use an Intel Gadget item in the list of device. I a concerned this edison is lost .. or is there a a way to reflash wiht only SSH access because it is my only reliable acces to the chip.

Here is what the flashtool said:

02/04/16 14:08:54.327 INFO : [Port -1] Starting flash ...

02/04/16 14:08:54.327 INFO : [Port -1] Running `Notify 'C:\Users\Smith John\Downloads\edison-iotdk-image-280915\helper\helper.html'` command

02/04/16 14:08:54.642 INFO : Displaying 'file:///C:/Users/Smith John/Downloads/edison-iotdk-image-280915/helper/helper.html' during 42000 ms

02/04/16 14:08:54.647 INFO : [Port -1] Command `Notify 'C:\Users\Smith John\Downloads\edison-iotdk-image-280915\helper\helper.html'` succeed

02/04/16 14:08:54.647 INFO : [Port -1] Running `Wait for device with status dnx_fw on port -1` command

02/04/16 14:09:10.912 INFO : [Port -1] Command `Wait for device with status dnx_fw on port -1` succeed

02/04/16 14:09:10.912 INFO : [Port 2/1] Running `Notify 'Edison board plugged'` command

02/04/16 14:09:11.196 INFO : Displaying 'Edison board plugged'' during 5000 ms

02/04/16 14:09:11.220 INFO : [Port 2/1] Command `Notify 'Edison board plugged'` succeed

02/04/16 14:09:11.220 INFO : [Port 2/1] Running `"xfstkFlashTool.exe" "C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_dnx_fwr.bin" "C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_ifwi-dbg-00.bin" "C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_dnx_osr.bin" "C:\Users\Smith John\Downloads\edison-iotdk-image-280915\u-boot-edison.img" "0x80000007" "none" "none"` command

02/04/16 14:09:11.299 INFO : [Port 2/1] Disabling xFSTK Misc DnX

02/04/16 14:09:11.299 INFO : [Port 2/1] Disabling xFSTK wipe out ifwi option

02/04/16 14:09:11.299 INFO : [Port 2/1] Using xFSTK Solo interface (new API)

02/04/16 14:09:11.299 INFO : [Port 2/1] xFSTK Soft Fuse not set

02/04/16 14:09:11.299 INFO : [Port 2/1] XFSTK Downloader API 1.8.0

02/04/16 14:09:11.299 INFO : [Port 2/1] Copyright (c) 2015 Intel Corporation

02/04/16 14:09:11.299 INFO : [Port 2/1] fwdnx -- C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_dnx_fwr.bin

02/04/16 14:09:11.299 INFO : [Port 2/1] fwimage -- C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_ifwi-dbg-00.bin

02/04/16 14:09:11.299 INFO : [Port 2/1] osdnx -- C:\Users\Smith John\Downloads\edison-iotdk-image-280915\edison_dnx_osr.bin

02/04/16 14:09:11.299 INFO : [Port 2/1] osimage -- C:\Users\Smith John\Downloads\edison-iotdk-image-280915\u-boot-edison.img

02/04/16 14:09:11.299 INFO : [Port 2/1] gpflags -- 0x80000007

02/04/16 14:09:11.299 INFO : [Port 2/1] softfuse --

02/04/16 14:09:11.329 INFO : [Port 2/1] XFSTK-STATUS--Detecting Intel Device - Attempt # 0

02/04/16 14:09:12.459 INFO : [Port 2/1] ....XFSTK-LOG--virtual bool MerrifieldDownloader::SetDevice(IGenericDevice*)

02/04/16 14:09:12.459 INFO : [Port 2/1] Initiating download...

02/04/16 14:09:12.462 INFO : [Port 2/1] XFSTK-STATUS--FW(Miscdnx) download is in progress ...

02/04/16 14:09:12.463 INFO : [Port 2/1] XFSTK-STATUS--FW: Sending DnX DCFI00 ...

02/04/16 14:09:15.373 INFO : [Port 2/1] XFSTK-STATUS--Error Code: 0 - Success

02/04/16 14:09:15.373 INFO : [Port 2/1] XFSTK-STATUS--Firmware download completed. Continuing to OS...

02/04/16 14:09:25.513 INFO : [Port 2/1] XFSTK-STATUS--Reconnecting to device - Attempt # 1

02/04/16 14:09:26.643 INFO : [Port 2/1] XFSTK-STATUS--POS download is in progress ...

02/04/16 14:09:29.718 INFO : [Port 2/1] XFSTK-STATUS--Error Code: 0 - Success

02/04/16 14:09:29.718 INFO : [Port 2/1] XFSTK-STATUS--Firmware and OS download completed.

02/04/16 14:09:29.718 INFO : [Port 2/1] XFSTK: Transfer Completed Successfully.

<span style="font-size: 12.0...

CBrou1
New Contributor I
435 Views

VICTORY!

I was able to reflash. I noticed that the failure point changed at each attempt. I just needed to try enought time until the process managed to run for 11m59s without trouble.

It is not very scientific but it worked, Thanks,

Reply