Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++
12745 Discusiones

How to resolve the error 'modelsim (vsim) is not on the path'?

ZikunTan
Principiante
7.211 Vistas

Hi!

 

I am initializing Intel HLS compiler according to the instruction. I have downloaded Quartus, Visual Studio and Modelsim.

 

What I typed 'C:\intelFPGA\18.1\hls\init_hls' in command prompt and press 'Enter', it says that 'Modelsim (vsim) is not on the path'. What's wrong with it? How can I resolve this error to initialize HLS compiler?

 

The error screenshot is shown below.

 

Thanks.Capture.PNG

0 kudos
4 Respuestas
MuhammadAr_U_Intel
Empleados
5.941 Vistas

Hi,

 

Vsim is looking for Modelsim executable path.

 

Make sure you have any version of Modelsim installed in your system and the executable path is added to windows environment variable "PATH"

 

Once Modelsim executable path is added, close, re-open command prompt and try executing the .bat script again to initialize.

 

thanks,

Arslan

Abe
Colaborador Valioso II
5.941 Vistas

Capture.JPGClick the Start button and type Control, in the list of search items , select Control Panel and then System and Security. Then select View amount of RAM and Processor Speed under System . Next click the Advanced System Settings option in the left pane.

 

In the window that opens, click the Environment Variables option and select the Path option to highlight it. Now, click the Edit... button.

 

In the window that opens up, make sure to enter the Quartus and ModelSim installation path as shown in the screenshot. Then click Ok to close the windows, and then finally open the Command Prompt and try again.

 

ZikunTan
Principiante
5.941 Vistas

Yes, this problem was caused by my wrong environment setting of ModelSim. I have corrected my path and now it is going well. Thanks for your response.

xiaoshe
Principiante
1.126 Vistas

retry run visual_studio_2010 setup.exe and select repair

Responder