Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Understanding eCode Functionality, Input Differences, and Fragment Outputs with Examples, Exams of Engineering Mathematics

University of LincolnEngineering Mathematics

Various aspects of ecode functionality, explaining the behavior of specific ecode structures through examples. Topics include understanding the functionality of extend transactions, deciphering the difference between two packet structures, and determining the output of given ecode fragments. Additionally, concepts such as testbenches, reducing verification time, deciding on verification levels, and the distinction between testing and verification are touched upon.

Typology: Exams

2015/2016

Uploaded on 02/13/2016

.12165
.12165 🇬🇧

2 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1. Explain the functionality of the following e codes (5 points)
(a)
extend transaction {
keep address in [10..50];
keep soft address == select {
20: min;
60: others;
30: max;
};
};
(b)
extend instr {
keep soft opcode == select {
40: [ADD, ADDI, SUB, SUBI];
20: [AND, ANDI, XOR, XORI];
10: [JMP, CALL, RET, NOP];
‘top.carry' * 90: JMPC;
};
};
2. Explain the difference between the input generated using the following two
constrained structures (7 points)
pf3
pf4

Partial preview of the text

Download Understanding eCode Functionality, Input Differences, and Fragment Outputs with Examples and more Exams Engineering Mathematics in PDF only on Docsity!

  1. Explain the functionality of the following e codes (5 points)

(a)

extend transaction { keep address in [10..50]; keep soft address == select { 20: min; 60: others; 30: max; }; };

(b)

extend instr { keep soft opcode == select { 40: [ADD, ADDI, SUB, SUBI]; 20: [AND, ANDI, XOR, XORI]; 10: [JMP, CALL, RET, NOP]; ‘top.carry' * 90: JMPC; }; };

  1. Explain the difference between the input generated using the following two constrained structures (7 points)

struct packet {

kind: [tx, rx]; size: byte; keep size > 15 => kind == rx; };

struct packet {

size: byte; kind: [tx, rx]; keep size > 15 => kind == rx; };

  1. What is the output of Num1 and Num4 produced by following e code fragment ( points)? Num2 = 0x1234; Num3 = 0x7777;

Num1 = %{Num2,Num3};

Num4 = pack(packing.high,num2,num3);

  1. Explain in your own words the temporal relationship expressed by the expect command in the following code (8 points)

event enter_exec_st is (change('top.cpu.curr_FSM') and true('top.cpu.curr_FSM' == exec_st))@sys.cpuclk; event fetch1_assert is (change('top.fetch1') and true('top.fetch1' == 1))@sys.cpuclk; expect @enter_exec_st => { @fetch1_assert}@sys.cpuclk else dut_error("PROTOCOL ERROR");