logo

Crowdly

Browser

Add to Chrome

ECE 564 (001) Fall 2025 ASIC and FPGA Design with Verilog

Looking for ECE 564 (001) Fall 2025 ASIC and FPGA Design with Verilog test answers and solutions? Browse our comprehensive collection of verified answers for ECE 564 (001) Fall 2025 ASIC and FPGA Design with Verilog at moodle-courses2527.wolfware.ncsu.edu.

Get instant access to accurate answers and detailed explanations for your course questions. Our community-driven platform helps students succeed!

What is wrong with the following code fragment intended for synthesis?

reg foo;

 

counter u2 (.clock(clock), .in(in), .latch(latch), .dec(dec), .zero(foo)); // counter is from the notes
View this question

Consider the following code (implemented exactly as described):

reg A, B, C;

always@(posedge clock) 

A <= B;

always@(posedge clock) 

B <= (A | C) & B;

always@(posedge clock)

C <= A;

The minimum and maximum delays between each set of successive gates are marked as #(min: typical: max) ns and are marked on the output node of the driving gate. (Remember the timing equations are ≤ and ≥ constraints). You also need the following:

  • T_setup = #(1 : 1 : 2) ns.
  • T_hold = #(1: 1 :2) ns.
  • T_skew = #(1: 1 : 1) ns for the clock.
  • T_clock-Q = #(2 : 3 : 5) ns.
  • T_logic = #(1 : 2 : 3) ns for each and every logic gate from any input to any output.

What is the fastest possible clock period that satisfies setup constraints across all variations? Give the answer in ns without the units

View this question

What is wrong with the following code fragment intended for synthesis?

wire foo;

always@(*)

foo = A | B;

View this question

In the following test fixture, what is the timing diagram being specified?

initial

begin

dec = 0; run = 0; ck = 1;

#10 dec =1; run = 1;

#10 run = 0;

#20 $finish;

end

always #5 ck = ~ck;
View this question

In general, the designer can choose whether the clock skew is positive or negative between any pair of flip-flops.

0%
100%
View this question

Consider the following code (implemented exactly as described):

reg A, B, C;

always@(posedge clock) 

A <= B;

always@(posedge clock) 

B <= (A | C) & B;

always@(posedge clock)

C <= A;

The minimum and maximum delays between each set of successive gates are marked as #(min: typical: max) ns and are marked on the output node of the driving gate. (Remember the timing equations are ≤ and ≥ constraints). You also need the following:

  • T_setup = #(1 : 1 : 2) ns.
  • T_hold = #(1: 1 :2) ns.
  • T_skew = #(1: 1 : 1) ns for the clock.
  • T_clock-Q = #(2 : 3 : 5) ns.
  • T_logic = #(1 : 2 : 3) ns for each and every logic gate from any input to any output.

Is there potential for a hold violation? T/F 

0%
0%
View this question

What is wrong with the following code fragment intended for synthesis?

reg[3:0] A;

initial

A =’4’b000 1;

always@(posedge clock)

A <= C;

View this question

Is there potential for a hold violation in the schematic above?

100%
0%
View this question

Consider the 3-level clock tree shown. If the 6-sigma variation in clock buffer delay is +/- 20 ps, and the post-routed delay of each buffer-to-buffer or buffer-flip-flop wire can vary by +/- 5 ps from the pre-layout delay estimate, what is the expected clock skew? 

Assume you can just add the 6-sigma variation to get the final variation.

Give your answer as a number (in ps). For example, if the answer is 25 ps, just enter 25

View this question

The details of the logic design have a strong impact on achievable clock speed

0%
0%
View this question

Want instant access to all verified answers on moodle-courses2527.wolfware.ncsu.edu?

Get Unlimited Answers To Exam Questions - Install Crowdly Extension Now!

Browser

Add to Chrome