Motorola M68CPU32BUG Manuel d'utilisateur Page 178

  • 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 177
USER CUSTOMIZATION
M68CPU32BUG REV 1 C-4
9. Power up the newly programmed BCC and note the checksum value indicated.
Repeat steps 1 through 8 above, to set the checksum to this value but with the
changes noted below. The CODESIZE parameter at offset $08 can be altered to make
the checksum valid only over the CPU32Bug half of the EPROM so user code in the
second half can be freely changed. Since a checksum error is simply reported on the
display terminal and code execution continues, it is not mandatory to set the
checksum.
STEP 1: No change.
STEP 2: Change checksum to the value noted on power-up per the command
below where "XXXX" is the value noted.
CPU32Bug>MS 400E XXXX<CR>
STEP 3: Change the filename to C32B1C.MX. To speed up reprogramming, a
temporary file consisting of only the checksum word could be used by
entering DU 400E 400F ’TMP.MX’ ,DC000<ALT-F1><CR> after
creating the C32B1C.MX file.
STEP 4: Skip this step.
STEP 5: No change.
STEP 6: Change the filename to C32B1C.MX.
STEP 7: This step is optional.
STEP 8: Only the checksum value needs to be programmed using the indicated
value. Since the checksum was set to the unprogrammed state of the
EPROM ($FFFF), programming can start immediately. DO NOT
ERASE THE BCC EPROM!
10. Power-up the BCC once again. The checksum message should not appear.
11. On the host computer, enter the following commands to update the two CPU32Bug S-
record files so they may be properly archived to a floppy disk for safe keeping:
C>DEL TMP.MX<CR>
C>DEL C32B1.MX<CR>
C>RENAME C32B1C.MX C32B1.MX<CR>
C>COPY C32B*.MX A:<CR>
12. The customization procedure is now complete.
Vue de la page 177
1 2 ... 173 174 175 176 177 178 179 180 181 182 183 ... 195 196

Commentaires sur ces manuels

Pas de commentaire