
Application Note
Alternate Solutions
AN1288
MOTOROLA
3
Alternate Solutions
As mentioned earlier, the design of the MC68HC(8)05K3’s PEEPROM
prevents the MMDS/MMEVS development systems from providing
users with direct access to this peripheral. Unlike with emulator pseudo-
RAM or on-chip EEPROM, users cannot modify or read the contents of
the PEEPROM with instructions from the MMDS/MMEVS command
line. Two features of the PEEPROM’s design in particular prevent the
MMDS and MMEVS systems from gaining access to the PEEPROM.
The first feature is that the PEEPROM data can be accessed only one
bit at a time through the manipulation of on-chip registers by software
stored in user memory space. Secondly, the PEEPROM is not a part of
the MC68HC(8)05K3’s memory map. This requires that alternative
methods be found to provide users with access to this peripheral during
the development process. Before considering the design and
implementation of K3EEPROG, two alternate methods of accessing the
PEEPROM will be discussed in this application note.
The simplest method of accessing the PEEPROM on an MMDS’s or
MMEVS’s resident MC68HC(8)05K3 is to remove the MCU from the
M68EM05K3 emulator board, program or read the PEEPROM with the
programmer provided for the MC68HC(8)05K3, and reinstall it on the
M68EM05K3.
When a developer wants to read or program the PEEPROM more
frequently, small assembly code routines can be written and kept for use
whenever the PEEPROM is to be accessed. When the PEEPROM is to
be programmed, the user can fill a designated section of the
MMDS/MMEVS’s memory with the data to be programmed into the
PEEPROM. The assembly code module designed to program the
PEEPROM then can be loaded and executed from the MMDS/MMEVS
command line. The software then can read the user-entered data from
the emulator’s memory and program the PEEPROM with it. The same
process can be used to read the contents of the PEEPROM, except
instead of reading data from the designated memory, the assembly code
module writes the contents of the PEEPROM into a designated area of
the emulator’s memory where it can be read by the user. This method
can be automated by utilizing the MMDS/MMEVS’s scripting feature.