1.Can you post the errors notified in the console tab?
2.Have you checked the tool chain settings before and after the re-start?
3.Do you have any other softwares installed in the same PC which uses the other tool chains?
4. Are you facing the same problem in any other PCs?
Here I attached errors from console.
Regarding toolchain settings before and after restart, It's look similar (I took screenshots and compare it).
I have 2 another tools which is based on eclipse, but I think it doesn't influence each other because other two software works fine.
I can't test it on another PC because I only have a linux machine, but I will install Virtual Machine with Fedora to see if problem appear again.
ErrorEZUSB0.png 38.2 K
1 of 1 people found this helpful
It looks like the other tool chain might be influencing the SDK tool chian path.
Check out this: 1. FAQ
I have done some test and another solution to fix my problem is to declare FX3_INSTALL_PATH, ARMGCC_INSTALL_PATH and ARMGCC_VERSION as global build variables (Window > Preferences > C/C++ > Build > Build Variables) in EzUSB IDE ( see printscreen in attachment).
After this step I got only "/bin/sh: arm-none-eabi-gcc: command not found" error. To fix It I followed instruction from your answer (Check out this: 1. FAQ)
solution.png 55.0 K