It has been a few months since I used my Edison breakout boards. I need to re-flash them. To my surprise the Intel web site has changed to a confusing tangle of links with cryptic names when one wants to re-flash an Edison module! Can somebody please point me to the URL that allows one to flash an Edison on a mini-breakout board.
I'm looking for the one with the rocket ship at the start NOT the batch file approach (which in the past never worked for me in the past anyway). Attached is the second popup that appears during the install. Why is this no longer displayed or easy to fined by Intel for new users?
Thanks for reaching out.
As you have noticed, all Edison's files and drivers are located now in the Download Center. At this link you can find the Tool you are looking for: https://downloadcenter.intel.com/download/26993/Intel-Edison-Configuration-Tool https://downloadcenter.intel.com/download/26993/Intel-Edison-Configuration-Tool. The file name is intel_edison_setup_win_v2016.2.007.zip.
Hoe you find this information useful.
Thanks for the rapid reply Yermi.
Don't know why everything is so difficult with Intel/Edison software downloads! It never seems to get easier.
The link you gave was to run on an old Windows 8.1 or earlier version. Like much of the rest of the world I have long since moved passed that. I am running Windows 10 64 bit! Does anybody on this site seriously run Windows 8? Must be Unix programmers updating this stuff.
Anyway just for the heck of it I ran your suggestion anyway. And yes it started off with the "Rocket Space Ship Icon". It insisted on me installing USB drivers. I did so. At first they seemed to be OK. But then they were rejected, See the following two pictures.
If you continue it proceeds to unwind the above process.
So I'm back to where I started! There does not seem to be an equivalent file Intel_edison_setup_win_vxxx.zip for windows 10.
There is an IntelEdisonDriverSetup1.2.1.exe for windows 10. I ran than and it seemed to run OK. But where is the rest of the menu items to flash the Edison on the breakout board, set the password and Change WiFi.
What am I missing here? Why can Intel not have a single button to launch a flash process. Am I the only one missing something. Please help.
The IntelEdisonDriverSetup1.2.1.exe file is used only to install the Edison USB drivers. You should see something like this if the USB and FTDI drivers are installed correctly:
Then, in order to flash the OS image on your Edison I'd recommend you to do it manually following these steps:
This command will start the flashing process and also request you to plug the board, at this moment you should plug the power supply J1 (recommended) and micro USB cable J6.
Note: the flashing process can take up to 5 minutes to complete.
You should see something like the following picture when the process has finished:
Here you can find more details about flashing process: https://software.intel.com/en-us/flashing-firmware-on-your-intel-edison-board-windows https://software.intel.com/en-us/flashing-firmware-on-your-intel-edison-board-windows
Hope this information helps. However, if you have any issue during the process, don't hesitate to ask for help.
Thanks for the fast reply Yermi.
Unfortunately in my system (Windows 10, 64 bit) device manager does not display (Ports & LPT). Again that's for an old Windows 8 and earlier OS as best I can tell.
The closest I seem to get is Universal Serial Bus Controllers. There is a long list see attached.
When I disconnected the Edison the USB Serial Converter entry disappeared. So I added the Edison back and deleted the driver.
I then added the Edison USB Drivers and it seemed to go Ok as shown here.
Then as you suggested I used the above link to reflash the Edison OS. I was reluctant to do this because I tried that method months ago and had no success.
Anyway thinking it would be better this time I proceeded -- with all the long file names etc. Why Intel cannot provide a simple one click button for users is past me to understand. Anyway -- as before -- the flash failed. The program could not locate the Edison. See here.
This is exactly what happened last time.
Now for the ridiculous part. when you actually download the xfstk.sureforge.net link and download the "Intel xFSTK Downloader" whatever that is, you discover its a .tar.gz Linux file. IT WILL NOT RUN ON WINDOWS!!!!
When is Intel going to get real Windows programmers to cleanup the Edison download site.
BTW, the Edison communicates fine over WiFi with the well known Windows program WinSCP.
Totally unclear why the above batch file does not work.
I write quite a bit about the Edison board. For example see here:-
http://s100computers.com/My%20System%20Pages/Edison%20Board/Edison%20CPU%20Board.htm S100 Computers - Edison CPU Board
I need to have a way for windows users to flash their units with Windows 10.
First, I would like to confirm that the Edison USB drivers are installed correctly, as you can't see it under Ports (COM & LPT), I'd recommend to look for the following:
Additionally, in This PC under Devices and drivers, the Edison should appear as shown in the following picture.
If the drivers are installed correctly, I recommend to try to run the flashall.bat (make sure to run the .bat file) command again, but in this case remove the old dfu-util.exe and libusb-1.0.dll files I suggested previously and download them again from this link: http://dfu-util.sourceforge.net/releases/dfu-util-0.9-win64.zip http://dfu-util.sourceforge.net/releases/dfu-util-0.9-win64.zip.
In regards to the flashall.bat –recovery option it is used to unbrick an Intel Edison, so we should not use that option.
I'll be waiting for your results.
Today Yermi, for some unknown reason the Ports & LPT shows up in the Device driver list. If I add the Edison it shows up as COM15.
Here are two pictures:-
When I look at network Adaptors I only see:-
As I said before I have absolutely no problem communicating with two of these Edison breakout boards over the serial/USB link using either a TTY terminal on the PC or WinSCP. Here is the root folder using the latter.
I spent the best part of two hours trying to flash both units using flashall etc. In every case the Intel USB ports (re)install works fine but the units can never seem to flash the OS. Flashall just does not detect the units. This is very frustrating. Even with the fresh downloads you suggested above.
Note to other people. Has anybody else had a problem with Flashall. Does it for example only work on virgin/new units???
BTW it's simply inexcusable that Intel only supplies a method to "unbrick" these units in Linux. The vast majority of Edison users use windows worldwide. Why are a few (I assume Linux) programmers at Intel not told to take care of us non Linus users. I guess I should post this issue elsewhere on this forum.
Thanks in advance Yermi.
According to the picture of the device manager you shared, the USB drivers for the Edison are not installed and they are used in order to perform the flash process, only the FTDI drivers are installed (USB Serial Port (COM 4)) for that reason you can establish a serial communication with your boards. I suggest you to look at: https://software.intel.com/en-us/installing-drivers-for-intel-edison-board-with-windows Installing the USB drivers and run the Windows* standalone driver 1.2.1 to install those drivers, once the drivers are installed correctly you should be able to flash you Edison.
Hi again Yermi,
I must be missing something that is exactly what I tried at the start of this forum. I'm doing it again here with pictures. Ran as administrator. Please examine
Then I ran Flashall. This is what I got:-
What in the heck am I doing wron. I launch Flashall and when displayed, I plug power & the USB port.
Both breakout board LED's are on. The led above the button flashes.
After installing the USB Drivers again, can you see the Intel Edison Virtual Com Port (COMx) and Intel Edison USB Composite Device (COMx) under Device manager -> Ports (COM & LPT)?
I just want to share some information about the flashing process of the Edison's image. Please check the following post here: https://communities.intel.com/message/495699# 495699 https://communities.intel.com/message/495699# 495699
On the other hand, it seems that you have installed the USB drivers and the FTDI drivers successfully. However, I noticed that you are running the flashall script without the .bat extension. Please try the following in cmd:
Sorry for the delayed reply Yermi, I was traveling yesterday.
First I now realize why sometimes the Ports (COM & LPT) were not displaying in the device manager.
If you have no USB serial ports connected it does not show up! To debug my setup I always remove all other USB ports.
So when I hookup the Edison (I tried two), I get the follow display.
As you can see just the Serial USB driver is installed. This is after a ran completely the IntelEdisonDriverSetup 1/2/1.exe
It removed the "old version" and completed (it said) OK. Looks like not everything is there?
Thanks for that input Diego. Indeed there seem to be a lot in common with my problems. I'm wondering if in fact Intel has in fact fixed the problem.
Has anybody recently got this Edison Re-flashing software download to work?
Are you using a breakout board?
Are you re-flashing a board with a current OS or a new board?
I seriously doubted that adding the .bat extension would make a difference in Window10. Anyway I tried it. No success!
Here are two pictures.
Obviously using the "---recovery" option is useless since it only works on Linux!
Any other suggestions
We've experienced similar behavior when trying to flash the Intel Edison board. Have you tried using a different micro-USB cable and different USB ports on your computer?
monahanz The ftdi drivers are exactly where Microsoft wants them to be, under Ports. This is not new for windows 10, in fact it has always been like this. Being an electronics engineer I like to know where things are plugged in to. In the menu of the Device Manager you can select 'view by connection' or something similar. You will see a ACPI computer, with a PCI bus, with a USB host, with a hub and finally the serial port connected (this a very approximate description). I think you will like it.
I am not sure if you understand the usb connections to the edison. If you do skip this.
One usb port is the serial port, it is a usb device and will show up as a serial port. You can connect a terminal program to the serial port and log into the edsion. I think windows 10 does not have one installed, in the past there was hyperterm.
The other usb port has a dual function, at least on my Eds Arduino board you switch the function using a hardware switch. On the breakout board I am not sure.
In one mode it is a usb host and you plug usb devices in (I have a hub, with ethernet and can plug additional devices in). In the other mode it's a slave and you can plug that usb cable to your PC. The edison's OTA partition will show up as a disk drive in windows.
I think in this mode also the edison tries to get ethernet over usb. Not sure how well that works under windows. And further this is the mode that will let you run flashall.
I provided these instructions for the Edison Arduino https://github.com/htot/meta-intel-edison/wiki/Build-and-flash-U-Boot-separately Build and flash U Boot separately · htot/meta-intel-edison Wiki · GitHub just in case someone breaks there u-boot. Unfortunately no instructions for the breakout board.
Are you sure you need to use flashall --recovery? If you didn't break u-boot you should be able to use flashall. The difference: --recovery will connect to the Edison in an earlier stage during boot, it will connect to the microkernel that will allow to flash u-boot (flashall --recovery calls a tool called xfsk for this). When u-boot is there and boots, the linux kernel will be flashed by u-boot (flashall calls a tool called dfu for this)
Hi FerryT, thanks for taking the time to reply.
If you read this (and related) treads you will see that I (as a hobby) build "S100 bus" boards which a number of "users" also use.
My concern is that now there seems to be issues with flashing the OS on to the Edison breakout boards. The 'old' way Intel describes at least with Windows 10 no longer works. In my hands neither does the new batch file approach. In spite of a number of back and forth postings here nobody seems to be able to explain the problem. I have a number of these breakout boards. All fail to flash. I am using a very generic Windows 10 (64 bit) with no other USB ports used when trying the falshall.
I am reluctant to recommend new boards to users until this problem is cleared up.
The reason I want to flash is because as I understand it new boards supplied by the likes of Mouser or Sparkfun etc. do not come with an OS installed.
How are people expected to get them running? I would be curious to know if anybody else out the has flashing or re-flashing problems with the current Intel Edison downloads using Windows 10.
If so we should let the vendors of these Intel units know that they are selling not only Intel unsupported products but unusable ones.
Comments by all please.
You are saying the Edison on the breakout board has no OS installed.
Does it have have at least u-boot installed? What do you see when you power up with a terminal program connected to usb J3?
I have a fully functional OS running on all the boards. I got them about 1 year ago and installed it (on Windows 10) using the Intel download at that time. It was a dialog box driven process. Since then Intel in their wisdom no longer supports that process. There are treads on this forum complaining that it did not work with more recent Microsoft W10 updates. Intel dropped it and now tells users to use the CMD Window and a batch file "Flashall.bat" That does not work for me on these Edisons with their current OS (The previous Intel downloads did).
What I'm trying to determine is
1. Why I'm having a problem with the above.
2. Are other people successful in doing what I described above.
3. These days is the OS already installed on the Edisons when purchased new from say the likes of Mouser. (In the past the OS had to be installed by the user).
Yes, unfortunately Intel 'in their wisdom' stopped supporting the Edison completely. That are of course not the same Intel people providing support in this forum.
Anyway, I'm curious about the problems you are having, but my experience is limited to linux (unfortunately there is no GUI to flash the Edison there, only the flashall.sh script) and the Edison Arduino. That flashall.sh script also causes some irritations:
- it needs to be run as 'sudo' (as root), even though Intel engineers think not. When run as regular user it just times out without any warning message. On windows this is probably not the case.
- Sometimes it just doesn't work and you need to restart the Edison again and then it works. I suspect this is because there is a short time window during boot when the update can be initiated and the window is just missed.
This is how I think the boot process works:
- microkernel is loaded from ROM
- some binary stuff (ifwi?) is loaded by microkernel
- this loads u-boot
- u-boot waits 2 sec for a prompt appears, otherwise u-boot boots linux according to the default env variables)
(I do this all the time to boot my 64 bit kernel manually)
I think flashall misses the 2 sec window.
When I flash u-boot from a working u-boot (i.e. an upgrade, not a recovery) I have both usb cables connected, connect a terminal program to the serial port to interrupt u-boot during boot with
(you can then also list the env variables with 'printenv').
I force u-boot to start waiting for flashing using 'dfu' with 'run do_force_flash_os' (this command inside the terminal, so is run on the edison). '
Then on the host (in another 'command prompt' window) I run 'sudo dfu-util -v -d 8087:0a99 --alt u-boot0 -D u-boot.bin'. This would flash u-boot, which is probably not what you want. But it does always work. When finished you need to type and the command 'exit' to reboot.
I see in flashall.bat this is done by the line "call:flash-command --alt u-boot0 -D "%BASE_DIR%u-boot-edison.bin"". Before that line all kind of 'ifwi' files are flashed, then u-boot, then 2 sets of u-boot env. Then the boot partition "call:flash-command --alt boot -D "%BASE_DIR%edison-image-edison.hddimg"" and then the rootfs "call:flash-command --alt rootfs -D "%BASE_DIR%edison-image-edison.ext4" -R".
Probably if you run 'run do_force_flash_os' in the terminal, your flashall.bat should just work.
So, there are 2 usb cables connected, this should provide sufficient power for the Edison, without a PSU connected. And on the terminal you can follow the flashing process.
Thanks Ferry but since I (and millions of others), only use Windows the approach you suggest is of no use to me.
Do you know if new "out of the box" Edison units sold these days by the likes of Mouser or Spark Fun come with the OS installed. Anybody?
Yes, I know you prefer the graphical interface. But as you are trying to figure out why that doesn't work I thought you would like to figure out step by step what's wrong. And maybe at least get it to work on the command line.
The commands I gave are actually 'windows' programs (run from the DOS prompt). Except for command that run on the edison.