Why verilog “always_comb block contains only one event control” error flagged on always procedural block with multiple “@”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
the following code below generates this error message:
"verilog always_comb imposes the restriction that it contains one and only one event control and no blocking timing controls"
always_comb begin
if (sig_a)begin
@(posedge sig_b); // wait for a sig_b posedge event
@(negedge sig_b); // then wait for a sig_b negedge event
event_true=1;
end
if (event_true)begin
@((sig_c==1)&&(sig_a==0)); //wait for sig_a to deassert and sig_c assert event to be true
yes =1;
end
else yes =0;
end
Why does the combi logic procedural block generate this error ?
And would an always block with @
event wait be synthesizable ?
verilog system-verilog hdl
add a comment |
the following code below generates this error message:
"verilog always_comb imposes the restriction that it contains one and only one event control and no blocking timing controls"
always_comb begin
if (sig_a)begin
@(posedge sig_b); // wait for a sig_b posedge event
@(negedge sig_b); // then wait for a sig_b negedge event
event_true=1;
end
if (event_true)begin
@((sig_c==1)&&(sig_a==0)); //wait for sig_a to deassert and sig_c assert event to be true
yes =1;
end
else yes =0;
end
Why does the combi logic procedural block generate this error ?
And would an always block with @
event wait be synthesizable ?
verilog system-verilog hdl
add a comment |
the following code below generates this error message:
"verilog always_comb imposes the restriction that it contains one and only one event control and no blocking timing controls"
always_comb begin
if (sig_a)begin
@(posedge sig_b); // wait for a sig_b posedge event
@(negedge sig_b); // then wait for a sig_b negedge event
event_true=1;
end
if (event_true)begin
@((sig_c==1)&&(sig_a==0)); //wait for sig_a to deassert and sig_c assert event to be true
yes =1;
end
else yes =0;
end
Why does the combi logic procedural block generate this error ?
And would an always block with @
event wait be synthesizable ?
verilog system-verilog hdl
the following code below generates this error message:
"verilog always_comb imposes the restriction that it contains one and only one event control and no blocking timing controls"
always_comb begin
if (sig_a)begin
@(posedge sig_b); // wait for a sig_b posedge event
@(negedge sig_b); // then wait for a sig_b negedge event
event_true=1;
end
if (event_true)begin
@((sig_c==1)&&(sig_a==0)); //wait for sig_a to deassert and sig_c assert event to be true
yes =1;
end
else yes =0;
end
Why does the combi logic procedural block generate this error ?
And would an always block with @
event wait be synthesizable ?
verilog system-verilog hdl
verilog system-verilog hdl
asked Nov 16 '18 at 11:46
TheSprintingEngineerTheSprintingEngineer
4319
4319
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The message reported by that error is misleading. You are not allowed ANY event controls in an always_comb
block. It creates the event sensitivity list automatically for you. Maybe it is combining the implicit event control with the ones you added to it, then generating the error.
Unless you are using a high-level synthesis tool, you are restricted to having one event control at the beginning of a basic always
block.
I'm using VCS, it might allow multiple@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replacedalways_comb
withalways
in my code, would the syntax that follow, be allowed? As in multiple event controls@ (posedge sig_b)
and@(negedge sig_b)
in one always block as shown here in link
– TheSprintingEngineer
Nov 18 '18 at 15:22
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
add a comment |
always_comb
is for combinational logic only. the @
statements you use have nothing to do with combinational.
from lrm 9.2.2.2.2
Statements in an always_comb shall not include those that block, have blocking timing or event controls, or fork-join statements.
In your case you need to use a general purpose always. always @*
will probably do.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337248%2fwhy-verilog-always-comb-block-contains-only-one-event-control-error-flagged-on%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The message reported by that error is misleading. You are not allowed ANY event controls in an always_comb
block. It creates the event sensitivity list automatically for you. Maybe it is combining the implicit event control with the ones you added to it, then generating the error.
Unless you are using a high-level synthesis tool, you are restricted to having one event control at the beginning of a basic always
block.
I'm using VCS, it might allow multiple@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replacedalways_comb
withalways
in my code, would the syntax that follow, be allowed? As in multiple event controls@ (posedge sig_b)
and@(negedge sig_b)
in one always block as shown here in link
– TheSprintingEngineer
Nov 18 '18 at 15:22
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
add a comment |
The message reported by that error is misleading. You are not allowed ANY event controls in an always_comb
block. It creates the event sensitivity list automatically for you. Maybe it is combining the implicit event control with the ones you added to it, then generating the error.
Unless you are using a high-level synthesis tool, you are restricted to having one event control at the beginning of a basic always
block.
I'm using VCS, it might allow multiple@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replacedalways_comb
withalways
in my code, would the syntax that follow, be allowed? As in multiple event controls@ (posedge sig_b)
and@(negedge sig_b)
in one always block as shown here in link
– TheSprintingEngineer
Nov 18 '18 at 15:22
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
add a comment |
The message reported by that error is misleading. You are not allowed ANY event controls in an always_comb
block. It creates the event sensitivity list automatically for you. Maybe it is combining the implicit event control with the ones you added to it, then generating the error.
Unless you are using a high-level synthesis tool, you are restricted to having one event control at the beginning of a basic always
block.
The message reported by that error is misleading. You are not allowed ANY event controls in an always_comb
block. It creates the event sensitivity list automatically for you. Maybe it is combining the implicit event control with the ones you added to it, then generating the error.
Unless you are using a high-level synthesis tool, you are restricted to having one event control at the beginning of a basic always
block.
answered Nov 16 '18 at 15:45
dave_59dave_59
20.9k21639
20.9k21639
I'm using VCS, it might allow multiple@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replacedalways_comb
withalways
in my code, would the syntax that follow, be allowed? As in multiple event controls@ (posedge sig_b)
and@(negedge sig_b)
in one always block as shown here in link
– TheSprintingEngineer
Nov 18 '18 at 15:22
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
add a comment |
I'm using VCS, it might allow multiple@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replacedalways_comb
withalways
in my code, would the syntax that follow, be allowed? As in multiple event controls@ (posedge sig_b)
and@(negedge sig_b)
in one always block as shown here in link
– TheSprintingEngineer
Nov 18 '18 at 15:22
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
I'm using VCS, it might allow multiple
@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replaced always_comb
with always
in my code, would the syntax that follow, be allowed? As in multiple event controls @ (posedge sig_b)
and @(negedge sig_b)
in one always block as shown here in link– TheSprintingEngineer
Nov 18 '18 at 15:22
I'm using VCS, it might allow multiple
@
event trigger to function as a wait in one always block (not so sure, how do i check for this ?). Anyhow, so say if I replaced always_comb
with always
in my code, would the syntax that follow, be allowed? As in multiple event controls @ (posedge sig_b)
and @(negedge sig_b)
in one always block as shown here in link– TheSprintingEngineer
Nov 18 '18 at 15:22
1
1
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
Simulators allow more syntax than what is synthesizable.
– dave_59
Nov 18 '18 at 16:02
add a comment |
always_comb
is for combinational logic only. the @
statements you use have nothing to do with combinational.
from lrm 9.2.2.2.2
Statements in an always_comb shall not include those that block, have blocking timing or event controls, or fork-join statements.
In your case you need to use a general purpose always. always @*
will probably do.
add a comment |
always_comb
is for combinational logic only. the @
statements you use have nothing to do with combinational.
from lrm 9.2.2.2.2
Statements in an always_comb shall not include those that block, have blocking timing or event controls, or fork-join statements.
In your case you need to use a general purpose always. always @*
will probably do.
add a comment |
always_comb
is for combinational logic only. the @
statements you use have nothing to do with combinational.
from lrm 9.2.2.2.2
Statements in an always_comb shall not include those that block, have blocking timing or event controls, or fork-join statements.
In your case you need to use a general purpose always. always @*
will probably do.
always_comb
is for combinational logic only. the @
statements you use have nothing to do with combinational.
from lrm 9.2.2.2.2
Statements in an always_comb shall not include those that block, have blocking timing or event controls, or fork-join statements.
In your case you need to use a general purpose always. always @*
will probably do.
answered Nov 16 '18 at 12:18
SergeSerge
4,13721016
4,13721016
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337248%2fwhy-verilog-always-comb-block-contains-only-one-event-control-error-flagged-on%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown