You might try running the flashall batch file and restore the flash to a stock image:
Instructions are found here:
I haven't tried the Windows version but I've run the flashall script from a Linux host and it worked the first time.
Just to get more info:
Did you try cycling power to the board?
Do you see any leds that would indicate that the board is powered?
Did you try powering the board from a USB hub or something that you're sure supplies enough current?
Did you smell any burning electronics or chips overheating?
Did you try rebooting your host Windows system (the universal solution to most computer problems)?
Do you see any USB devices being enumerated on the USB bus when you connect the Edison board?
Q1: Did you try cycling power to the board?
I do not understand your question. Sorry, but I using 2 USB cable to power up the Edison board.
Q2: Do you see any leds that would indicate that the board is powered?
Yes, DS1 and DS2 are light up not at the same time.
Q3: Did you try powering the board from a USB hub or something that you're sure supplies enough current?
No, I direct use my Laptop to power up the board.
Q4: Did you smell any burning electronics or chips overheating?
No, no burning smell.
Q5: Did you try rebooting your host Windows system (the universal solution to most computer problems)?
I try to restart my laptop for several times.
Q6: Do you see any USB devices being enumerated on the USB bus when you connect the Edison board?
The USB cable and the port on the laptop I have try to connect to my smart phone to transfer photo. Still can transfer the file.
Thank you and I will try on your suggestion.
Looks like you have admin rights when running the flashall script so that's good.
I'm not sure what Windows provides for logs and tools but when running Linux I notice a usb device (8087:0a99) show up for about 3 seconds when the GADGET DRIVER: usb_dni_dfu line is displayed.
Looks something like this:
Bus 003 Device 061: ID 8087:0a99 Intel Corp.
idVendor 0x8087 Intel Corp.
That's the device that the flashall script is waiting for:
did you unplug the usb cable that's providing power to the board and plug it back in when the script prompts you? (note I did not need to unplug the usb cable that connects to the serial debug port but I'm not using the same board (the mini breakout board))
You could also interrupt u-boot using the serial debugging terminal and try running:
The important thing is the timing; the USB device has to be detected while the script is waiting for it.
Looks like it worked, that's the same text I saw on my board.
It takes a while for the board to reboot a few times to complete the install, just don't unplug it while it's writing stuff.
On the debug console you should be able to see some output when u-boot starts. If the install happens to be complete when you connect with the debug console you can press enter and you should see a login prompt. (you can login as root with no password)
I couldn't tell from the picture of the board if you had unplugged the micro secure digital card, but if not you might try rebooting without the card plugged in. I don't have that board so I can't test it and don't know which flash device takes boot precedence.