Motorola M68CPU32BUG Bedienungsanleitung Seite 176

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 196
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 175
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.
Seitenansicht 175
1 2 ... 171 172 173 174 175 176 177 178 179 180 181 ... 195 196

Kommentare zu diesen Handbüchern

Keine Kommentare