Solved: Intel Edison flashing fails

CMay5 · ‎09-14-2018

Hi folks,

my Intel Edison stopped being reachable by terminal and ssh over wifi, so I decided to flash it.

$ ./flashall.sh

Using U-Boot target: edison-blankcdc

Now waiting for dfu device 8087:0a99

Please plug and reboot the board

Timed out while waiting for dfu device 8087:0a99

DEBUG: lsusb

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

Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc.

Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd

Bus 001 Device 005: ID 8087:0a2b Intel Corp.

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

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

DEBUG: dfu-util -l

dfu-util 0.9

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Did you plug and reboot your board?

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

The normal flashing did not work, so I tried the recovery option:

$ ./flashall.sh --recovery

Starting Recovery mode

Please plug and reboot the board

Flashing IFWI

XFSTK Downloader Solo 1.8.1-5.1

Build date and time: Sep 1 2017 15:13:00

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 Failed: Attempt # 10

Intel SoC Device Detection Failed: Attempt # 11

Intel SoC Device Detection Failed: Attempt # 12

Intel SoC Device Detection Failed: Attempt # 13

Intel SoC Device Detection Failed: Attempt # 14

Intel SoC Device Detection Failed: Attempt # 15

Intel SoC Device Detection Failed: Attempt # 16

Intel SoC Device Detection Failed: Attempt # 17

Intel SoC Device Detection Failed: Attempt # 18

Intel SoC Device Detection Failed: Attempt # 19

Intel SoC Device Detection Failed: Attempt # 20

Xfstk tool error

DEBUG: lsusb

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

Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc.

Bus 001 Device 003: ID 04f2:b52c Chicony Electronics Co., Ltd

Bus 001 Device 005: ID 8087:0a2b Intel Corp.

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

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

DEBUG: dfu-util -l

dfu-util 0.9

This program is Free Software and has ABSOLUTELY NO WARRANTY

Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

So there was no success either. I figured I should try a serial connect:

$sudo screen /dev/ttyUSB0

4DE��}��D��E��u�5�d�ń��ZR��Z��~��g��gZ�cWs�gK�f�s��SgR�s�~�os{k��K

So there is something coming from the Edison upon reboot... Every time I reset the Edison, this line of garbage is being received again...

Does anybody have any clue how to proceed with this?

Thank you!

idata · ‎09-14-2018

Hi Christian,

Thanks for your interest in the Intel Edison Kits.

Could you please tell us if you followed the steps from the link below? : https://www.intel.com/content/www/us/en/support/articles/000006285/boards-and-kits.html

You can also try using FlashToolLite in order to flash the latest Firmware on Intel Edison Board: https://01.org/node/2463

Please let us know if you have additional questions.

Best regards,

George

View solution in original post

idata · ‎09-14-2018

Hi Christian,

Thanks for your interest in the Intel Edison Kits.

Could you please tell us if you followed the steps from the link below? : https://www.intel.com/content/www/us/en/support/articles/000006285/boards-and-kits.html

You can also try using FlashToolLite in order to flash the latest Firmware on Intel Edison Board: https://01.org/node/2463

Please let us know if you have additional questions.

Best regards,

George

View solution in original post

CMay5 · ‎09-14-2018

Yes, I followed these steps and it already fails at step 2.

If I connect both cables to my computer and invoke screen, I get a reboot loop. I guess it is due to insufficient power from the USB port:

$ sudo screen /dev/ttyUSB0 115200

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

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 ***

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

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 ***

So I connected J16 to an external power supply and J3 to a USB port on my computer. Then I see the following:

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

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 (Jun 06 2016 - 14:40:07)

Watchdog enabled

DRAM: 980.6 MiB

MMC: tangier_sdhci: 0

In: serial

Out: serial

Err: serial

Hit any key to stop autoboot: 0

Target:blank

Partitioning already done...

Flashing already done...

GADGET DRIVER: usb_dnl_dfu

reading vmlinuz

5461344 bytes read in 135 ms (38.6 MiB/s)

Valid Boot Flag

Setup Size = 0x00003c00

Magic signature found

Using boot protocol version 2.0c

Linux kernel version 3.10.98-poky-edison+ (neck@flax) # 1 SMP PREEMPT Mon Jun 6 14:32:08 PDT 2016

Building boot_params at 0x00090000

Loading bzImage at address 00100000 (5445984 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=cdc systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=a4015fb9e5c0de59334eaaf4e10feb92 g_multi.dev_addr=02:00:86:0f:eb:92 platform_mrfld_audio.audio_codec=dummy"

Starting kernel ...

So it just hangs when the kernel is supposed to be started...

Thanks for your help...

idata · ‎09-17-2018

Hello Christian,

We would really appreciate if you could provide us the answers to the following questions:

When was the last time the board worked?

Were there any external sensors connected?

Any additional information that could help us to identify the problem would be much appreciated.

We also suggest that you submit a warranty request via web ticket.

Regards,

George

CMay5 · ‎09-18-2018

Hello George,

thank you for your reply. The board stopped being reachable by ssh (over wifi) about 3 weeks ago. Then I realized the problems explained above. There were no external sensors connected, it was just performing calculations.

Strangely enough, I tried again and again and suddenly yesterday it booted up successfully. I have no explanation, but for the moment everything seems to be ok.

Thanks for your support.

Christian

idata · ‎09-18-2018

Hello Christian,

Thank you for informing us. We are happy to hear that your problem is solved.

Please let us know if you have any other updates or questions.

Have a nice day.

Regards,

George