User Profile
User Widgets
Contributions
Re: Quartus did not start
We understand how disruptive the “The application was unable to start correctly (0xc0000142)” error can be. We have attempted to replicate the problem in our in-house environment, but so far we have been unable to duplicate the issue. As a result, your assistance with the following debugging steps is essential to help us narrow down the root cause and resolve this matter as efficiently as possible. Debugging Steps: Reregister All DLL Files Open Command Prompt as Administrator (search for cmd, right-click, select "Run as administrator"). Run the following command and press Enter:for %i in (%windir%\system32\*.dll) do regsvr32.exe /s %i Then run:for %i in (%windir%\system32\*.ocx) do regsvr32.exe /s %i Close Command Prompt. Set Correct System Locale Press Windows + R, enter intl.cpl, and click OK. In the Administrative tab, click Change system locale... and select the English region (e.g., English (United States)). Click OK and restart your computer. Run Quartus as Administrator Right-click the Quartus icon, select Properties. Under the Compatibility tab, check Run this program as an administrator. Click Apply and OK. Reset LoadAppInit_DLLs Registry Value Press Windows + R, type regedit, and press OK. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows Double-click LoadAppInit_DLLs and set the value to 0. Click OK and restart your PC. Install Latest Microsoft C++, .NET Framework, and DirectX Download and install the latest versions: Microsoft Visual C++ Redistributables .NET Framework DirectX End-User Runtime Web Installer Restart your PC. Use Process Monitor (Advanced) Download Process Monitor. Run Procmon.exe, start Quartus, and look for any “NAME NOT FOUND” or “PATH NOT FOUND” errors indicating missing DLLs. Update Graphics Drivers Visit your graphics card vendor’s website (e.g., NVIDIA Driver Downloads), download and install the latest driver for your GPU, and restart your system. Next Steps: Please proceed through these steps, restarting your system after each major change. If the error persists after completing these steps, kindly let us know which steps you have tried and any observations or error messages you encounter. This will help us further isolate the issue and recommend the next course of action. We greatly appreciate your cooperation and patience1View0likes0CommentsRe: log signal to signal tap
Yes — in Quartus / Signal Tap, the closest SystemVerilog attribute is: (* preserve_for_debug *) logic [7:0] dbg_sig; This preserves the signal for debug visibility and prevents it from being optimized away during compilation. Please note that this is not exactly the same as Vivado’s mark_debug behavior: In Quartus, preserve_for_debug does not automatically add the signal into Signal Tap. It preserves the signal so that it remains available and can be found more easily in the Signal Tap Node Finder. The signal still needs to be added manually to the .stp file / Signal Tap configuration. Also, preserve_for_debug only takes effect when Preserve for Debug is enabled in the project, for example with: set_global_assignment -name PRESERVE_FOR_DEBUG_ENABLE ON So in summary, Quartus does provide an RTL syntax to mark signals for debug preservation, but it does not automatically instantiate or populate Signal Tap the way Vivado mark_debug does.3Views0likes0Comments