
C-4
DINK32 PowerPC ISA Debugger User’s Manual
For More Information On This Product,
Go to: www.freescale.com
MOTOROLA
Extending DINK
— Press enter
— Select Disconnect icon
— Select Properties icon
— Press Configure button
— Change bits per second (baud rate) to 57600
— Press Okay button
— Select connect button
— Press enter
6. Type fl -dsi (Only required on mdink32 V10.6)
7. Type dl -fl -o ffc00000
8. Select pull down menu “transfer” use option “send text file” and select the
dink32.src file from the list of files. (DO NOT use the option “send file”.)
MDINK32 is not supplied as elf or sfiles on this site. However, all the code (some code is
purposefully removed and the object files are substituted) is available to build mdink32.
Loading MDINK32 requires unprotecting sector 15 on the Excimer and Maximer and using
some type of emulator to download the code.
Selected DINK32 code is available at this site. Some files are not released in source form,
and starting with this release R12.3, no objects are supplied so that DINK32 can
NOT
be
built.
All the source, including the removed code, is available from the Motorola confidential site
and can be obtained from your Motorola Salesperson.
C.5
Extending DINK
DINK uses a shell processor to collect various command arguments and pass them to the
command function, in addition to managing help. To extend DINK functions by adding new
commands, the following procedure is used:
1. The command is written in ‘C’ and linked into the DINK executable. The function
is passed command arguments and may invoke an argument processor. When the
command has completed its task, it returns a status code (SUCCESS or an error code
from “errors.h”).
2. A descriptive line is added to the function “shell.c”.
C.5.1
Writing Commands
To write a new command, it is easiest to use the following template:
F
Freescale Semiconductor, Inc.
n
.