User manual

DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-68
VE Verify S-Records Against Memory VE
3.34 VERIFY S-RECORDS AGAINST MEMORY
VE [<port>][<addr>][;<X/-C>][=<text>]
VE is identical to the LO command with the exception that data is not stored to memory but
merely compared to the contents of memory.
The VE command accepts serial data from a host system in the form of a Motorola S-records file
and compares it to data already in memory. If the data does not compare, then the user is alerted
via information sent to the terminal screen.
The optional port number allows the user to specify which is the download port. If the port
number is omitted the default is port 0. The port number must be within the range 0 to $1F.
The BCC default hardware configuration consists of one I/O port; P4 on the BCC or P9 on the
PFB. This limits the user to one host computer running a terminal emulation program. To send S-
records, the user must escape out of the terminal emulation program because the host computer
can not perform terminal emulation and send S-records at the same time. When the host is not in
terminal emulation mode, all status messages from CPU32Bug would be lost. Thus the user must
press <CR> twice after re-entering the terminal emulation program to signal CPU32Bug that
status messages can now be sent.
The optional <addr> field allows the user to enter an offset address which is added to the address
contained in the record address field. This causes the records to be compared to memory at
different locations than would normally occur. The contents of the automatic offset register are
not added to the S-record addresses. If the address is in the range $0 to $1F and the port number
is omitted, precede the address with a comma to distinguish it from a port number. Only absolute
addresses (i.e., "1000") should be entered, as other addressing modes cause unpredictable results.
An address is allowed here rather than an offset (expression) to permit support for function codes
(see paragraph 2.5).
The optional text field, entered after the equals sign (=), is sent to the host before CPU32Bug
begins to look for S-records at the host port. This allows the user to send a command to the host
device to initiate the download. Do not delimited text with quote marks. The text follows the
equals sign and terminates with a carriage return. If the host is operating full duplex, the string
echoes back to the host port and appears on the user’s terminal screen.
Some host systems echo all received characters so the text string is sent to and received from the
host one character at a time. After the entire command is sent to the host, VE looks for an LF
character from the host signifying the end of the echoed command. No data records are processed
until LF is received. If the host system does not echo characters, VE still looks for an LF
character before data records are processed. For this reason it is required in situations where the
DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-69
VE Verify S-Records Against Memory VE
host system does not echo characters that the first record transferred by the host system be a
header record. The header record is not used, but the LF after the header record serves to break
VE out of the loop so that data records are processed.
Other VE options are:
-C option Ignore checksum. A checksum for the data contained within an S-Record
is calculated as the S-record is read in at the port. Normally, this calculated
checksum is compared to the checksum contained within the S-Record and
if the compare fails, an error message is sent to the screen. If this option is
selected, the comparison is not made.
X option Echo. This option echoes the S-records to the user’s terminal as they are
read in at the host port. Do not use this option when port 0 is specified.
During a verify operation S-record data is compared to memory. Verification begins with the
address contained in the S-record address field (plus the offset address). If the verification fails,
then the non-comparing record is set aside until the verify is complete and then it is displayed on
the screen. If three non-comparing records are encountered in the course of a verify operation,
then the command is aborted.
If a non-hex character is encountered within the data field, then the received portion of the record
is printed to the screen and CPU32Bug’s error handler points to the faulty character.
An error condition exists if the embedded checksum of a record does not agree with the
checksum calculated by CPU32Bug. A message is displayed showing the address of the record
(as obtained from the address field of the record), the calculated checksum, and the checksum
read with the record. A copy of the record is also output. This is a fatal error and causes the
command to abort.
EXAMPLES
This short program was developed on a host system.
1 * Test Program
2*
3 65004000 ORG $65004000
4
5 65004000 7001 MOVEQ.L #1,D0
6 65004002 D088 ADD.L A0,D0
7 65004004 4A00 TST.B D0
8 65004006 4E75 RTS
9 END
****** TOTAL ERRORS 0--
****** TOTAL WARNINGS 0--
Fr
eescale S
emiconduct
or
, I
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
nc...