User`s manual

VE - Verify S-Records Against Memory
3-228
3
and should begin immediately following the equals sign, and
terminate with the carriage return. If the host is operating full
duplex, the string is also echoed back to the host port by the host
and appears on your terminal screen.
In order to accommodate host systems that echo all received
characters, the above-mentioned text string is sent to the host one
character at a time and characters received from the host are read
one at a time. After the entire command has been sent to the host,
VE keeps looking for an <LF> character from the host, signifying
the end of the echoed command. No data records are processed
until this <LF> is received. If the host system does not echo
characters, VE still keeps looking for an <LF> character before data
records are processed. For this reason, it is required in situations
where the 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.
During a verify operation, data from an S-record is compared to
memory beginning with the address contained in the S-record
address field (plus the offset address, if it was specified). If the
verification fails, then the non-comparing record is set aside until
the verify is complete and then it is printed out to the screen. If three
non-comparing records are encountered in the course of a verify
operation, then the command is aborted.
If a non-hexadecimal character is encountered within the data field
of a data record, then the part of the record which had been received
up to that time is printed to the screen and the PPCBug error
handler is invoked to point to the faulty character.
As mentioned, if the embedded checksum of a record does not
agree with the checksum calculated by PPCBug and if the
checksum comparison has not been disabled via the C option, then
an error condition exists. A message is output stating 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.