02.07.2013 Views

Type III C lass A Program

Type III C lass A Program

Type III C lass A Program

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

BREAK<br />

Format:<br />

I I<br />

I BREAK I<br />

I I<br />

id<br />

symbol<br />

hexloc<br />

id is any decimal number between 0 and 15 inclusive<br />

symbol is a name which has been assigned (using the DEF<br />

request) to the core address at which a breakpoint<br />

is to be set<br />

hexloc is the hexadecimal core location (relative to the<br />

current origin) at which a breakpoint is to be set<br />

Usage:<br />

This request enables the user to stop execution of a program<br />

at specific instruction location called breakpoints.<br />

Issuing the BREAK request causes only one breakpoint to be<br />

set. separate BREAK requests must be issued for each<br />

breakpoint desired. A maximum of sixteen breakpoints may be<br />

in effect at any given time, and any attempt to set more<br />

than sixteen is rejected .•<br />

The first operand of the BREAK request specifies the<br />

identification number assigned to the breakpoint being set.<br />

It must be a decimal number between 0 and 15 inclusive. If<br />

an identification number is specified which is the same as a<br />

currently set breakpointl• the previous breakpoint is cleared<br />

and the new one is set.<br />

The second operand of the BREAK request indicates the core<br />

address at which the breakpoint is to be set. If this<br />

operand contains any non-numeric characters, the DEBUG<br />

symbol table is searched for a matching symbol entry. If a<br />

match is found, the breakpoint is set at the core address to<br />

which the symbol name is assigned provided that address is<br />

on an even (halfword) boundary. If no match 1S found in the<br />

DEBUG symbol table" or if the second operand contains only',<br />

numeric characters, the current origin as established by<br />

the ORIGIN request is added to the specified operand and the<br />

breakpoint is set at the resulting core address provided<br />

that address is on a halfword boundary.<br />

The DEBUG program sets a breakpoint by saving the contents<br />

of the byte located at the core address specified by the<br />

second operand of the BREAK request,. This byte is replaced<br />

by the byte EX where x is the hexadecimal equivalent of the<br />

breakpoint identifier specified in the first operand. For<br />

the breakpoint setting to have meaning, the core address<br />

indicated by the second operand must be the location of an<br />

DEBUG - BREAK 221'"

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!