Employ two EVBPlus units in the lab to exchange (simultaneously) two lists of by

Question

Employ two EVBPlus units in the lab to exchange (simultaneously) two lists of bytes

starting at $0000. Each list is 16 bytes long.

List in microcontroller #1 :

ORG $0000

FCB $AB,$AB,$AB,$AB,$AB,$AB,$AB,$AB

FCB $AB,$AB,$AB,$AB,$AB,$AB,$AB,$AB

List in microcontroller #2:

ORG $0000

FCB $BA,$BA,$BA,$BA,$BA,$BA,$BA,$BA

FCB $BA,$BA,$BA,$BA,$BA,$BA,$BA,$BA

After the execution is complete, the exchanged lists are also to start at $0000 in both

microcontrollers. You must not save the data at any other temporary memory locations

during the execution of the program. The transfer must proceed in sequence starting by

exchanging the first byte in the lists, then the second byte, and so on.

The program that you write for both microcontrollers must be the same (except for the

lists). You are to employ Ports B, and C and the STRA and STRB of both

microcontrollers.

Explanation / Answer

A breakpoint makes your program stop whenever a certain point in the program is reached. For each breakpoint, you can add conditions to control in finer detail whether your program stops. You can set breakpoints with the break command and its variants (see section Setting breakpoints), to specify the place where your program should stop by line number, function name or exact address in the program. In languages with exception handling (such as GNU C++), you can also set breakpoints where an exception is raised (see section Breakpoints and exceptions).

In SunOS 4.x, SVR4, and Alpha OSF/1 configurations, you can now set breakpoints in shared libraries before the executable is run.

A watchpoint is a special breakpoint that stops your program when the value of an expression changes. You must use a different command to set watchpoints (see section Setting watchpoints), but aside from that, you can manage a watchpoint like any other breakpoint: you enable, disable, and delete both breakpoints and watchpoints using the same commands.

You can arrange to have values from your program displayed automatically whenever GDB stops at a breakpoint. See section Automatic display.

GDB assigns a number to each breakpoint or watchpoint when you create it; these numbers are successive integers starting with one. In many of the commands for controlling various features of breakpoints you use the breakpoint number to say which breakpoint you want to change. Each breakpoint may be enabled or disabled; if disabled, it has no effect on your program until you enable it again.

Breakpoints are set with the break command (abbreviated b). The debugger convenience variable `$bpnum' records the number of the breakpoints you've set most recently; see section Convenience variables, for a discussion of what you can do with convenience variables.

You have several ways to say where the breakpoint should go.

Related Questions

Navigate

• Browse (All)
• Browse E
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.