02-06-2015 01:41 PM
I've recently had to upgrade to Win 8.1 and now when i try to build in SDK i get "arm-xilinx-eabi-gcc.exe - Application Error - The application was unable to start correctly(0xc0000142). Click OK to close the application".
I've checked gcc versions, paths, folders(some prolems i had with other compilers) and reinstalled windows and vivado.
02-09-2015 03:00 AM
check the MD5SUM value of downloaded file and see if it matches with the one available on site.
10-08-2015 05:26 AM
Same here. I already tried it on two computers, but still same error. Also downloaded the whole webpack twice!
It drives me nuts.
10-09-2015 02:15 AM
Ok i finally got it to work. Problem was that i had MinGW and Python installed on both machines. Don't know what exactely caused this problem, but after uninstalling those programs, it just works. I also deleted the Systemvariables in "PATH" of Python..
Hope this can help someone else..
07-01-2016 03:06 AM
the issue also happens with ver. 2016.2. In my case it was caused by WinAVR.
Hope this helps anyone.
07-02-2016 01:04 PM
08-24-2016 08:12 AM
I'm having this problem too. Has anyone figured out a solution? I'm using 2016.1 SDK and I'm running it in the standalone mode. It still doesn't work.
12-22-2016 10:56 AM
I am having this same issue using SDK 2016.4 on Windows 10.
I completely cleared my PATH environment variable and it did not help. I also tried running the settings64.bat file as mentioned in this thread but it did not resolve the issue either.
07-10-2017 03:57 PM
I had the same problem (Xilinx SDK 2017.2). After uninstalling all AVR compilers on my machine I was instantaneously able to compile. So thanks for this advice.
09-04-2017 04:47 AM
Thank you for your answers. I also encountered this problem with 2017.2. After i deleted the AVR compiler, it works. I also deleted its path.
10-21-2017 07:11 PM
I've got my environment to work by reinstalling the latest msys-1.0.dll used by make.exe in the build process.
11-19-2017 08:05 AM
Had the same problem. Uninstalling WinAVR will help. It worked fine for me in windows 10.