Motorola M68CPU32BUG Manuel d'utilisateur Page 62

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 196
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 61
DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1 3-32
LO Load S-Records From Host LO
Other options:
-C Ignore checksum. A checksum for the data contained within an S-record is
calculated as the S-record is read in through the port. Normally this calculated
checksum is compared to the checksum contained within the S-record. If the
compare fails, an error message is sent to the screen on completion of the
download. If this option is selected, then the comparison is not made.
X Echo. As the S-records are read in at the host port, they are echoed to the user’s
terminal. Do not use this option when port 0 is specified.
T TRAP #15 code. This option causes LO to set the target register D4 = ’LO’x, with
x = $0C ($4C4F200C). The ASCII string ’LO’ indicates that this is the LO
command; the code $0C indicates TRAP #15 support with stack parameter/result
passing and TRAP #15 disk support. This code is used by the downloaded
program to select the appropriate calling convention when executing debugger
functions. Since some Motorola debuggers use conventions different from
CPU32Bug, they set a different code in D4.
The S-record format (refer to Appendix A) allows a specified entry point in the address field of
the S-record-block termination record. The contents of the termination-record address field (plus
any offset address) is put into the target PC. Thus after a download the user need only enter G or
GO instead of G <addr> or GO <addr> to execute the downloaded code.
If a non-hex character is encountered within the data field of a data record, then that part of the
record, preceeding the non-hex character, is displayed. This causes the CPU32Bug error handler
to point at the faulty character.
An error condition exists if the embedded-record checksum does not agree with the checksum
calculated by CPU32Bug. An output message displays 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. A checksum error is a fatal error and causes the
command to abort.
When a load is in progress, each data byte is written to memory and then the contents of this
memory location are compared to the data to determine if the data is stored properly. If for some
reason the compare fails, then an output message displays the address where the data was to be
stored, the data written, and the data read back during the compare. This is also a fatal error and
causes the command to abort.
S-records are processed character-by-character. So if the command aborts due to an error, all data
stored previous to the error is still in memory .
Vue de la page 61
1 2 ... 57 58 59 60 61 62 63 64 65 66 67 ... 195 196

Commentaires sur ces manuels

Pas de commentaire