Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor I
2,593 Views

how do you fully recover a board?

Jump to solution

Working with u-boot, I've managed to do something terrible and u-boot won't finish loading now. How to do a recovery? I've managed to get far enough along so that the flashall.sh --recovery tries to work, but it won't actually flash. I cannot find an official procedure on this.

Thanks

airdamien@edibuild:~/edison$ ./flashall.sh --recovery -v

Starting Recovery mode

Please plug and reboot the board

Flashing IFWI

XFSTK Downloader Solo 0.0.0

Copyright (c) 2014 Intel Corporation

Build date and time: Oct 14 2014 15:38:56

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 Found

Parsing Commandline....

Registering Status Callback....

.Initiating Download Process....

.....................................XFSTK-STATUS--Reconnecting to device - Attempt # 1

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 2

XFSTK-STATUS--Reconnecting to device - Attempt # 3

XFSTK-STATUS--Reconnecting to device - Attempt # 4

XFSTK-STATUS--Reconnecting to device - Attempt # 5

XFSTK-STATUS--Reconnecting to device - Attempt # 6

XFSTK-STATUS--Reconnecting to device - Attempt # 7

XFSTK-STATUS--Reconnecting to device - Attempt # 8

XFSTK-STATUS--Reconnecting to device - Attempt # 9

XFSTK-STATUS--Reconnecting to device - Attempt # 10

XFSTK-STATUS--Reconnecting to device - Attempt # 11

XFSTK-STATUS--Reconnecting to device - Attempt # 12

XFSTK-STATUS--Reconnecting to device - Attempt # 13

XFSTK-STATUS--Reconnecting to device - Attempt # 14

XFSTK-STATUS--Reconnecting to device - Attempt # 15

XFSTK-STATUS--Reconnecting to device - Attempt # 16

XFSTK-STATUS--Reconnecting to device - Attempt # 17

XFSTK-STATUS--Reconnecting to device - Attempt # 18

XFSTK-STATUS--Reconnecting to device - Attempt # 19

XFSTK-STATUS--Reconnecting to device - Attempt # 20

XFSTK-STATUS--Reconnecting to device - Attempt # 21

Xfstk tool error

DEBUG: lsusb

Bus 001 Device 004: ID 203a:fff9

Bus 001 Device 003: ID 203a:fff9

Bus 001 Device 002: ID 203a:fff9

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

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

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

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 mailto:dfu-util@lists.gnumonks.org dfu-util@lists.gnumonks.org

airdamien@edibuild:~/edison$

Tags (1)
0 Kudos

Accepted Solutions
Highlighted
New Contributor I
1 View

Re: how do you fully recover a board?

Jump to solution

thanks guys, I just figured it out. It takes moving the jumper to the other set of pins(top) and then bringing it up. then the flashall --recovery can do the work.

View solution in original post

0 Kudos
7 Replies
Highlighted
1 View

Re: how do you fully recover a board?

Jump to solution

You are definitely not the only one running into this.It's something which should get fixed in the script

If you don't run as root it won't work but you also won't get any warning / error message.

Highlighted
Community Manager
1 View

Re: how do you fully recover a board?

Jump to solution

1. Run the script as root (e.g. sudo ./flashall.sh)

2. For some reason I don't see your Edison board in lsusb output. Please connect both MicroUSB Edison ports to your computer. Run lsusb, you should be seeing the following IDs:

8087:0a9e - This is Edison DFU

0403:6001 - FTDI - Serial to USB Interface

Also start a serial console, it might spit some useful info (sudo screen /dev/ttyUSB0 115200).

Highlighted
1 View

Re: how do you fully recover a board?

Jump to solution

... and obviously the switch put away from the big USB socket but towards the micro USB one (if using the Arduino baseboard)

Highlighted
New Contributor I
2 Views

Re: how do you fully recover a board?

Jump to solution

thanks guys, I just figured it out. It takes moving the jumper to the other set of pins(top) and then bringing it up. then the flashall --recovery can do the work.

View solution in original post

0 Kudos
Highlighted
Beginner
1 View

Re: how do you fully recover a board?

Jump to solution

I currently have the same problem with the command "sudo ./flashall.sh --recovery"

Would you help me by explain what JUMPER and what PINS you mentioned about?

0 Kudos
Highlighted
Novice
1 View

Re: how do you fully recover a board?

Jump to solution

Hi - I'm also not having any luck with the --recovery option, here is my output (this is with the Arduino board).

Update: the recovery process was successful after pressing the reset button on the board, and attempting it again.

Which jumpers/pins are you referring to?

sudo ./flashall.sh --recovery

Starting Recovery mode

Please plug and reboot the board

Flashing IFWI

XFSTK Downloader Solo 0.0.1

Copyright (c) 2015 Intel Corporation

Build date and time: May 2 2015 15:34:00

.Intel SoC Device Detection Found

Parsing Commandline....

Registering Status Callback....

.Initiating Download Process....

.....................................XFSTK-STATUS--Reconnecting to device - Attempt # 1

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 2

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 3

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 4

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 5

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 6

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 7

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 8

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 9

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 10

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 11

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 12

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 13

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 14

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 15

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 16

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 17

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 18

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 19

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 20

...................................XFSTK-STATUS--Reconnecting to device - Attempt # 21

Xfstk tool error

DEBUG: lsusb

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

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 005: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)

Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply

Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver

Bus 002 Device 004: ID 046d:c52f Logitech, Inc. Wireless Mouse M305

Bus 001 Device 046: ID 8086:e005 Intel Corp.

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

DEBUG: dfu-util -l

dfu-util 0.8

Thanks!

0 Kudos
Highlighted
Beginner
1 View

Re: how do you fully recover a board?

Jump to solution

I currently have the same problem with the command "sudo ./flashall.sh --recovery"

Would you help me by explain what JUMPER and what PINS you mentioned about?

airdamien

0 Kudos