Getting some strange errors when I try to compile my code onto my DE2 board using Quartus. My friend has tried my code on his computer and it compiles without error, however on mine, it gives me the following errors.
Info: Running Quartus II 64-Bit Analysis & Synthesis
Info: Version 13.0.1 Build 232 06/12/2013 Service Pack 1 SJ Web Edition
Info: Processing started: Sun May 17 15:11:37 2015
Info: Command: quartus_map --read_settings_files=on --write_settings_files=off 353lab2 -c lab2
Warning (20028): Parallel compilation is not licensed and has been disabled
Error (10430): VHDL Primary Unit Declaration error at std_logic_1164.vhd(51): primary unit "std_logic_1164" already exists in library "ieee"
Error (10784): HDL error at std_1164.vhd(46): see declaration for object "std_logic_1164"
Error (10430): VHDL Primary Unit Declaration error at syn_unsi.vhd(34): primary unit "STD_LOGIC_UNSIGNED" already exists in library "ieee"
Error (10784): HDL error at std_logic_unsigned.vhd(30): see declaration for object "STD_LOGIC_UNSIGNED"
Error (10431): VHDL Secondary Unit Declaration error at std_logic_1164.vhd(252): secondary unit "std_logic_1164" already exists in primary unit "std_logic_1164"
Error (10784): HDL error at std_1164.vhd(246): see declaration for object "std_logic_1164"
Error (10523): Ignored construct STD_LOGIC_UNSIGNED at std_logic_unsigned.vhd(87) due to previous errors
Error (10523): Ignored construct VITAL_Timing at timing_b.vhd(54) due to previous errors
Error (10523): Ignored construct LPM_COMPONENTS at lpm_pack.vhd(678) due to previous errors
Error (10523): Ignored construct std_logic_arith at mgc_arit.vhd(270) due to previous errors
Error (10523): Ignored construct qsim_logic at mgc_qsim.vhd(755) due to previous errors
Error (10523): Ignored construct TEXTIO at textio_vhdl93.vhd(103) due to previous errors
Error (10523): Ignored construct std_logic_arith at syn_arit.vhd(204) due to previous errors
Error (10523): Ignored construct std_logic_misc at syn_misc.vhd(182) due to previous errors
Error (10523): Ignored construct STD_LOGIC_SIGNED at syn_sign.vhd(95) due to previous errors
Error (10523): Ignored construct std_logic_textio at syn_textio.vhd(68) due to previous errors
Error (10523): Ignored construct STD_LOGIC_UNSIGNED at syn_unsi.vhd(93) due to previous errors
Info (12021): Found 2 design units, including 1 entities, in source file lab2.vhd
Info (12022): Found design unit 1: lab2-impl
Info (12023): Found entity 1: lab2
Info (12021): Found 2 design units, including 1 entities, in source file dflip.vhd
Info (12022): Found design unit 1: dFlip-impl
Info (12023): Found entity 1: dFlip
Error: Quartus II 64-Bit Analysis & Synthesis was unsuccessful. 17 errors, 1 warning
Error: Peak virtual memory: 529 megabytes
Error: Processing ended: Sun May 17 15:11:38 2015
Error: Elapsed time: 00:00:01
Error: Total CPU time (on all processors): 00:00:01
From what I understand, Quartus is possibly detecting multiple copies of std_logic_1164 in "ieee", however when I click the error loation, it takes me to quartus/libraries/ieee/std_logic_1164.vhd.
Related
I installed MPI on macOS Mojave following this tutorial on Stack Overflow. I installed openmpi-2.0.4.tar.gz.
But when I tried to run that hello world program I get error:
[My-MacBook-Pro.local:40731] [[30181,0],0] ORTE_ERROR_LOG: Bad parameter in file orted/pmix/pmix_server.c at line 262
[My-MacBook-Pro.local:40731] [[30181,0],0] ORTE_ERROR_LOG: Bad parameter in file ess_hnp_module.c at line 667
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
pmix server init failed
--> Returned value Bad parameter (-5) instead of ORTE_SUCCESS
Does anyone know how to fix this?
export TMPDIR=/tmp
(or some other temp directory, where the directory name is not too long)
I installed OPNET modeler 14.5 at my laptop (OS: Windows 8).
I slightly modified a process model, and ran simulation. But I see the following errors.
<<< Recoverable Error >>>
Pipeline stage model (dpt_ecc_pon) compilation failed
Source code was unavailable to the compiler
----
<<< Recoverable Error >>>
Object repository construction failed
Pipeline stage (dpt_ecc_pon) compilation failed, no source code found.
T (0), EV (-), MOD (NONE)
----
<<< Program Abort >>>
Error encountered rebuilding repository -- unable to proceed
T (0), EV (-), MOD (NONE)
How can i overcome this?
If you create dpt_ecc_pon pipeline stage source, there are some rules to define them. Based on your error message, the dpt_ecc_pon.ps.c/cpp is not included in the model_dirs.
All source code should be included in model_dirs. Press Ctrl+Alt+P. In preference dialog, search 'model_dirs' and make sure the directory where your codes are included in the 'model_dirs'.
I have installed Mplab version 8.9, I have downloaded a firmware package from this link
But, when I hit build all it shows me the following output and build fails:
----------------------------------------------------------------------
Debug build of project `D:\microchip\WFF Generic HID Demo 3\WFF_GenericHID_Demo_3.mcp' started.
Language tool versions: mplink.exe v9.80, mcc18.exe v9.80, mplib.exe v9.80
Preprocessor symbol `__DEBUG' is defined.
Thu May 29 15:44:49 2014
----------------------------------------------------------------------
Make: The target "D:\microchip\WFF Generic HID Demo 3\main.o" is out of date.
Executing: "C:\Program Files (x86)\Microchip\xc8\v1.31\bin\mcc18.exe" -p=18F4550 /i"..\Microchip Solutions v2011-07-14\Microchip\Include" "main.c" -fo="main.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
Make: The target "D:\microchip\WFF Generic HID Demo 3\usb_descriptors.o" is out of date.
Executing: "C:\Program Files (x86)\Microchip\xc8\v1.31\bin\mcc18.exe" -p=18F4550 /i"..\Microchip Solutions v2011-07-14\Microchip\Include" "usb_descriptors.c" -fo="usb_descriptors.o" -D__DEBUG -Ou- -Ot- -Ob- -Op- -Or- -Od- -Opa-
usb_descriptors.c:
125: rom struct{BYTE report[28];}hid_rpt01={
(984) type redeclared ^
^ (1098) conflicting declarations for variable "hid_rpt01" (usb_descriptors.c:125)
(908) exit status = 1
(908) exit status = 1
Halting build on first failure as requested.
----------------------------------------------------------------------
Debug build of project `D:\microchip\WFF Generic HID Demo 3\WFF_GenericHID_Demo_3.mcp' failed.
Language tool versions: mplink.exe v9.80, mcc18.exe v9.80, mplib.exe v9.80
Preprocessor symbol `__DEBUG' is defined.
Thu May 29 15:44:51 2014
----------------------------------------------------------------------
BUILD FAILED
I tried to find the problem in this link also, but i could not find its root cause.
I started to try this because i wanted to make my own shields and pcb for my projects instead of arduino and the like.
Please help me with this problem.
we are building a very large Visual C++ 2010 solution (about 150 projects, full build takes about an hour) on a build server (Jenkins) with MSBuild. Unfortunately when a project fails, it is difficiult to find out which and why, because the console log is so long and errors are hard to find.
Is there a nice msbuild log parser or msbuild logger that nicely lists all failed projects and the error messages? The best we've found so far is the Warnings Plugin but this is pretty much useless in many cases.
I find the Log Parser Plugin very useful, though you need to provide your own parser file (in /jobs/vs_parsing_rules). I use the following, which works well for msbuild
error /[Ee]rror *:/
error /Error on line/
error /error [CM]/
error /fatal error/
error /unresolved external/
error /[aA]ccess is denied/
error /aborted/
warning /[Ww]arning *:/
warning /[Ww]arning C/
warning /WARNING/
warning /Couldn't/
warning /Can't/
warning /Cannot/
warning /ld.*unsupported/
error /[uU]ndefined symbols/
warning /[rR]eferenced from/
warning /[nN]ot found/
warning /exit status/
warning /no symbols/
error /ERROR[^A-Za-z]/
info /INFO/
start /BUILD/
Another useful parsing rules that works for msbuild:
# Divide into sections based on project compile start
start /^------/
# Compiler Error
error /(?i)error [A-Z]+[0-9]+:/
error /MSBUILD : (?i)error :/
error /\(\d+(,\d+)?\): (?i)error [A-Za-z]*:/
# Compiler Warning
warning /(?i)warning [A-Z]+[0-9]+:/
I'm using fsyacc within Visual Studio (using the Parsed Language Starter template), but the build output doesn't show the line/column where the error occured (only: fsyacc exited with code 1). I have to build from the command prompt to get this information, somewhat negating the benefit of VS integration.
Is there a way to show this in the output window?
EDIT
Here are some examples of errors that aren't shown in the output window.
Parser.fsy(74,4): error: parse error
and
building tables
FSYACC: error FSY000: NonTerminal 'query' has no productions
Here's success output that would be nice to see also:
building tables
computing first function...time: 00:00:00.1318603
building kernels...time: 00:00:00.1027372
building kernel table...time: 00:00:00.0533044
computing lookahead relations.............................
..............time: 00:00:00.0517415
building lookahead table...time: 00:00:00.0207993
building action table...state 29: shift/reduce error on AS
state 49: shift/reduce error on OR
state 49: shift/reduce error on AND
...
time: 00:00:00.1457792
building goto table...time: 00:00:00.0035636
returning tables.
39 shift/reduce conflicts
62 states
11 nonterminals
41 terminals
46 productions
#rows in action table: 62
Instead of using Parsed Language Starter template, I build parser/lexer by using Pre-build event in Build Events from VS Project Properties:
fslex "$(ProjectDir)Lexer.fsl"
fsyacc --module Grammar "$(ProjectDir)Grammar.fsy"
It is not very desirable since I have to set fsyacc/fslex in Path environment variable. Whenever I don't want to rebuild parser/lexer, I have to comment out the following part in fsproj file:
<PropertyGroup>
<PreBuildEvent>fslex "$(ProjectDir)Lexer.fsl"
fsyacc --module Grammar "$(ProjectDir)Grammar.fsy"
</PreBuildEvent>
</PropertyGroup>
However, the winning point is clear. We have all messages including errors and success output in stdout which is convenient for debugging.