- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello,
I'm having trouble with the Nios V Command Shell; specifically, I cannot start the shell (niosv-shell.exe) or the RiscFree IDE. Sometimes the program starts, and sometimes it does not.
Operating system: Windows 10 19045.5737 version 22H2.
Tool: Quartus Prime Pro 23.4
I'm getting an application error 0xc0000142: I've already reinstalled the Quartus tool a few times.
Also followed the steps from the link below.
https://thegeekpage.com/how-to-solve-application-error-0xc0000142-in-windows-10/
still getting the same issue.
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
It appears you’ve already reinstalled the tools, yet the issue still persists.
Are there any other files remaining in the Quartus installation directory? Could you perform a completely clean install to ensure no outdated files are left behind?
Let me know if that works.
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Divya,
Thank you for the reply,
Yes, I have make sure that there is no outdated files in installation directory.
Best Regards,
Prashant Gohel
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi divya,
Also the similar issue faced in some of my colleague system, in which we have intall Quartus 24.3 prime pro first time.
Best Regards,
Prashant Gohel
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
We are not aware of any known issue and I cannot reproduce this at my end. It's interesting to see that two versions (23.4 and 24.3) far apart from each other show the exact same behavior. Do you only see this problem on a Windows machine ?
Can you share a screenshot of how the environment variables are setup.
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Divya,
We haven't tried on Linux system. As we only use windows system for Quartus tool.
Best Regards,
Prashant Gohel
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi @DivyaG_Altera,
Any inputs from the environment variables from the windows system above.
Hope to hear from you soon.
Best Wishes
BB
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
Since I’m unable to reproduce this issue, it’s hard to pinpoint the cause. I’ve checked the environment variable on my system and it mostly matches with yours, perhaps you could try updating the SOPC_KIT_NIOS2 under user variable to reference your current installation?
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Divya,
Thank you for your response.
I have updated the SOPC_KIT_NIOS2 path as suggested, but unfortunately, the issue persists—I am still encountering the application error.
My Windows system operates under administrative restrictions. Could there be any background services or registry settings that require additional permissions to run the application properly?
I have also attempted to run the application using "Run as Administrator," but the error remains the same.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
Is WSL installed on this Windows machine? If so, please try running the same process in WSL and let me know if that avoids the error you’re seeing on Windows.
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
HI Divya,
I’ve attempted to run niosv-shell.exe using WSL, but I’m still encountering the application error.
Interestingly, the behavior seems to change with every system restart — sometimes it works after a reboot, and other times it doesn’t.
Please let me know if you need any additional information.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
Please bear with me - I'm checking with our tools team internally.
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
I'll follow up internally once more to get an update. But in the meantime, here's what they've shared :
For the NIOS V tools to function correctly, quartus_py.exe must be operational. We have not seen any issues with this executable in our regressions. The team suggests checking for any PYTHON* environment variables. To do this, run set in a cmd.exe shell to display all environment variables. If you find any PYTHON* entries, try removing them to see if that resolves the issue. You can remove a variable by running: "set name_of_variable="
Let me if this helps.
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Prashant,
I just wanted to follow up on this thread. Did you find any PYTHON environment variables on your system ?
Our tools team suggest running these steps and let us know if it resolves the issue :
1. running the Windows Resource Checker as Adminstrator w/ following command:
sfc /scannow
2. Try simplifying the PATH to the minimal and execute.
Example: C:\Windows\System32>set Path=C:\Program Files\Python312\;C:\WINDOWS\system32;C:\WINDOWS;
C:\Windows\System32>c:\altera_pro\25.1_129\quartus\bin64\quartus_py
C:\Windows\System32>c:\altera_pro\25.1_129\quartus\bin64\quartus_py "print(\"hello\")"
hello
Regards,
Divya
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi @prashant_gohel,
Greetings, just checking in to see if there is any further doubts in regards to this matter.
Hope your doubts have been clarified.
Best Wishes
BB
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Divya and BB,
Thank you for sharing the information, as it required Administrator access, I will share this step with admin team and check. It required few days. Will share the result with you.
Best regards,
Prashant Gohel
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Did you find any PYTHON environment variables on your system ?
I didn't get any path with PYTHON in environment variables.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hi Divya,
We have executed the suggested steps in administrator mode. But while running the qurtus_py we are getting the same application error message.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
We have also run the sfc/scannow command but still the behaviour is same.
