Flashall.bat

[Marine Farinha]

Thestandard method of flashing Intel Edison SOC modules involved downloading zipped image files that contain dfu-util drivers and scripts; Usually flashall.bat and flashall.sh for Windows and Linux.

The normal procdure is to bring up flashall.bat in a windows command window or flashall.sh in a Linux terminal session, reboot the Edison SOC module, then quickly run the flashall.bat or flashall.sh scripts and allow the flashall scripts to grab control of the Edison SOC as it boots when it pauses during the load process.

If you want, you can also establish a Putty serial link to the Edison SOC as well and watch the boot process. If you establish the link and then press the button on the board to shutdown the SOC, then press it again, you will not lose the Putty connection so you can see the SOC boot.

If for some reason this process does not work, the flashall script will tell you that you have the option of running flashall --recovery, but you need additional software to do that which is called xfstk-downloader. If you search you will find out that this is a software package that Intel has deemed open source now and loaded it into a public repository. If you want to use it, there are no commonly available versions compiled for Windows or Linux. Compiling the software can be done, but it requires other software packages as well. I first found it on sourceforge in a repository that Intel setup.

The truth is that when Intel dropped their endeavor into IOT, they tossed the baby out the window with the bath water. The Edison SOC is a really good device but it was not cheap. When cheaper chips came out, the Edison fell out of favor for the most common applications, which is unfortunate as it is x86 compatible and easily runs a full installation of Linux, but it wasn't cheap. However if you want a robust device to run critical applications like OpenAPS, the Edison SOC simply rocks! They have been known to run for years with never a hiccup.

I can't find any compiled xtf_stk__ software that works on windows. So you are stuck with doing this on Linux which isn't bad if you have any Linux experience. This was done on a 64 bit Intel CPU running Linux Ubuntu 19.04.

I just tried to update the aDSP image on my Intrinsyc DragonBoard APQ8074 to the one included in the latest Hexagon SDK release (v1.1.0) using push_adsp.cmd. It seemed as though the push was successful, but now the board boots up to displaying the Intrinsyc banner, then goes unresponsive and does not appear to Windows over USB. Has anyone experienced anything like this? Any advice?

I was finally able to resolve this issue. The BSP for the DragonBoard does not include images for the proprietary partitions on the board, including the the modem partition where the aDSP image reside, so reflashing using the BSP's flashall.bat script did not help. The solution was to use the FlashingUtility, available separately on Intrinsyc's support site. The documentation made it seem as though that tool was only necessary to initialize legacy boards, but apparently it's needed any time these undocumented proprietary partitions are corrupted.

It also seems that this was a known issue between the new SDK and the 1.1 version of the BSP that may be resolved in a BSP update coming soon. Unfortunately, that was not communicated with the developer community. See -sw-8074/board-fails-to-boot-after-....

Using terminal window, a lot of error messages like "is not ready", "permission error" and ... are reported. Also there is no graphical output on HDMI, while previously I had the graphic view using this port on native android image.

My dragonboard APQ8074 (KK2.2) also boots and got many errors entering idle screen, after I run flashingutility_1.2 with DB8074_UpgradePackage_2.3.zip, it fails with an error "unkown reason", now seems like bootloader is broken... I plug-in power jack (press on power button needed?) and no output from DB9 uart, also blue led is never on...

I am trying to learn how to use Yocto. After a successful build of an Intel Edison image, I see all the files in the output directory, but I don't know where to go from here (ie All the hard stuff should be done, now I just need to flash the Intel Edison with this image). There does not seem to be any documentation on next steps anywhere either. Can someone please point me in the right next direction?

I'm confused because none of the files seem to match up with what you normally drop in the Edison storage. Just a little confused on what is needed (All, just one image, some files, etc?) and where to drop them in order to flash the Edison. Intel's documentation is still lacking quite a bit.

Ok, I got a little bit of help from Intel. Once finished compiling the image, these images are stored in the edison-src/build/tmp/deploy/images directory (screenshot I previously included). All thats left is to run this script: ./edison-src/device-software/utils/flash/postBuild.sh The files to flash to the Edison are stored in: ./edison-src/build/toFlash

Now all I am trying to figure out is how to run the flashall.sh or flashall.bat file. The batch file does not appear to be working on Windows, and I don't have a local Linux box at the moment to connect the Edison to in order to run the .sh script. I assume the Edison needs to be connected directly to the a Linux box, mount the flash in a specific way and run the flashall.sh script. Will do a bit more research and see if I can maybe spin up a VM to test. Any suggestions or input are welcomed and appreciated. Thanks

3a8082e126