
MOTOROLA
Appendix C. Building and Extending DINK
For More Information On This Product,
Go to: www.freescale.com
C-1
Appendix C
Building and Extending DINK
C.1
Obtaining DINK32 Source
Limited source is available for downloading from the Motorla website. Full source can also
be requested through the same web site.
The DINK32 webpage is available through the Motorola web site at
http://www.motorola.com. Search for the keyword “DINK32.”
C.2
Building DINK32
Instructions are supplied with the full source code.
C.3
DINK Software Build Process
DINK32 is a sophisticated debug ROM program. Most hardware specific features such as
the specific processor, the memory map, the target platforms, etc. are automatically
detected at run time. This flexibility allows a single version of DINK32 to run on different
platforms with different processors; for example the same version of DINK32 will boot tthe
Sandpoint as well as the Excimer and Maximer platforms with all the supported processors.
The ROM device on the Sandpoint system is the Plastic Leaded Chip Carrier (PLCC)
device. Upgrading the firmware on such system could be as easy as removing and replacing
the old ROM with the new one. The ROM devices on the Excimer and Maximer platform
however are the thin small surface mount packages (TSSOP). It is not easy to remove such
devices on the target hardware for upgrading. To solve this problem, Motorola provides a
smaller version of DINK32 called MDINK. The main purpose of mdink is to download
DINK32 or other boot program to ROM, thus it provides a robust way for upgrading the
firmware.
There are four different versions of DINK:
1. DINK32 provides the capability to download and debug application programs,
2. MDINK32 provides the capability to download and upgrade firmware.
3. VDINK provides simulation of PowerPC processors in a UNIX enviornment.
F
Freescale Semiconductor, Inc.
n
.