Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile .

Again and again I see this error every time I edit the BSP settings:

make all

Makefile not up to date.

settings.bsp has been modified since the BSP Makefile was generated.

Generate the BSP to update the Makefile, and then build again.

To generate from Eclipse:

1. Right-click the BSP project.

2. In the Nios® II Menu, click Generate BSP.

To generate from the command line:

nios2-bsp-generate-files --settings= --bsp-dir=

make: *** [makefile] Error 1

I do these steps and still seeing the same damn error. Every thing is ok and don't tell me to just do the steps above.

Sometimes the compiler isn't able to update the Makefile and when you update the BSP settings the Makefile will be out of date: To work around this, do the following: 1- Open the BSP project folder 2- Right click the Makefile>> Delete 3- Open the NIOS II Command Shill 4- Write the following command: cd <...../project_bsp> nios2-bsp-generate-files --settings=settings.bsp --bsp-dir=<C:/…./<project_bsp/> 5- Build your project again. I've tried this and the issue gone. Sometimes the compiler isn't able to update the Makefile and when you update the BSP settings the Makefile will be out of date: To work around this, do the following: 1- Open the BSP project folder 2- Right click the Makefile>> Delete 3- Open the NIOS II Command Shill 4- Write the following command: cd <...../project_bsp> nios2-bsp-generate-files --settings=settings.bsp --bsp-dir=<C:/…./<project_bsp/> 5- Build your project again. I've tried this and the issue gone.

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here .

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice .