Motorola M68CPU32BUG Manuel d'utilisateur Page 87

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 98
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 86
USER CUSTOMIZATION
M68CPU32BUG REV 1 C-2
C.2 CPU32BUG CUSTOMIZATION
The general procedure for customizing CPU32Bug is as follows:
1. Copy the parameter area from the CPU32Bug EPROM to RAM by entering the
following command:
CPU32Bug>BM E0000 E01FF 4000<CR>
2. Modify the parameters in RAM using the offsets shown in Table C-1. For example,
the CHECKSUM value would begin at location $4000 plus offset $0E, or $400E.
Thus the word at $400E must be changed to $FFFF so a new checksum value for the
customized CPU32Bug can be calculated. Enter the following command to change
the CHECKSUM value.
CPU32Bug>MS 400E FFFF<CR>
Change the SIGNON message to indicate customization has been performed. Change
the spaces after "Version 1.01" to read ".XX <title>", where "XX" is your
customized version number starting with 01 and <title> is the name of your company
or school/lab. Use the MS command with text input (’string’).
3. Create an S-record file of the changes on the host computer by entering the ALT-F1
key on the host computer terminal (for ProComm emulator program) to open a log
file. Enter the file name C32B1.MX and then complete the CPU32Bug DU
command by pressing <CR>. The offset of DC000 is required to create the S-records
with the proper starting address of $E0000.
CPU32Bug>DU 4000 41FF ’C32B1.MX’ ,,DC000<ALT-F1><CR>
CPU32Bug><ALT-F1><CR>
Close log file
4. Create an S-record file of the rest of CPU32Bug on the host computer by entering the
ALT-F1 key on the host computer terminal (for ProComm emulator program) to
open a log file. Enter the file name C32B23.MX and then complete the CPU32Bug
DU command by pressing <CR>.
CPU32Bug>DU E0200 FFFFF ’C32B23.MX’<ALT-F1><CR>
CPU32Bug><ALT-F1><CR>
Close log file
5. If desired, the two S-record files can be edited on the host computer to remove the
"Effective address" lines at the beginning of the file and the CPU32Bug> prompt at
the end, but it is not required. If the two S-record files are concatenated into one file,
edit the first file to remove the S8 termination record at the end of the file.
SELF-TEST ERROR MESSAGES
M68CPU32BUG REV 1 B-1
APPENDIX B
SELF-TEST ERROR MESSAGES
B.1 INTRODUCTION
On power-up or reset, CPU32Bug executes a system self-test (confidence test) to verify system
integrity before issuing the sign-on message (SIGNON) and monitor prompt (CPU32Bug>). If an
error is detected, testing is aborted and an error message is printed after the sign on message and
monitor prompt. Error messages are summarized in Table B-1. The error address is displayed as
"000EXXXXXX" because the actual error address is only significant to qualified repair
personnel. Additional error values, such as address and data information, may also be printed.
Table B-1. Self-Test Error Messages
Test Type and Error Message Failure Description
CPU Register Test:
ERROR $01 @ $000EXXXX, CONFIDENCE TEST FAILED Dn test #1
ERROR $02 @ $000EXXXX, CONFIDENCE TEST FAILED Dn test #2
ERROR $03 @ $000EXXXX, CONFIDENCE TEST FAILED Dn test #3
ERROR $04 @ $000EXXXX, CONFIDENCE TEST FAILED SR
ERROR $05 @ $000EXXXX, CONFIDENCE TEST FAILED VBR, USP
ERROR $06 @ $000EXXXX, CONFIDENCE TEST FAILED An
ERROR $07 @ $000EXXXX, CONFIDENCE TEST FAILED Exchange
CPU Instruction Test:
ERROR $10 @ $000EXXXX, CONFIDENCE TEST FAILED AND, OR, NOT, EOR
ERROR $11 @ $000EXXXX, CONFIDENCE TEST FAILED ADD, SUB
ERROR $12 @ $000EXXXX, CONFIDENCE TEST FAILED MUL, DIV
ERROR $13 @ $000EXXXX, CONFIDENCE TEST FAILED BSET, BCLR
ERROR $14 @ $000EXXXX, CONFIDENCE TEST FAILED LSR
ERROR $15 @ $000EXXXX, CONFIDENCE TEST FAILED LSL
ERROR $16 @ $000EXXXX, CONFIDENCE TEST FAILED DBF
Fr
eescale S
emiconduct
or
, I
Freescale Semiconductor, Inc.
For More Information On This Product,
Go to: www.freescale.com
nc...
Vue de la page 86
1 2 ... 82 83 84 85 86 87 88 89 90 91 92 ... 97 98

Commentaires sur ces manuels

Pas de commentaire