
B-2
DINK32 PowerPC ISA Debugger User’s Manual
For More Information On This Product,
Go to: www.freescale.com
MOTOROLA
agentboot
B.1
agentboot
The directory contains source files that can be built to build an application that can then be
downloaded into dink at address 0x100000 and run. This example program is meant to
demonstrate how to boot an MPC8240/MPC107 based PCI Agent from Host local memory
space on the Sandpoint reference platform.
B.1.1
Background
DINK32 V12.0 and later is currently setup up so that once the Host boots up from the DINK
image in ROM, it then configures the Agent. Once the Agent is configured, its PCI
Command Register is then set and it is allowed to boot up from the same DINK image in
ROM. What this example code does is force the Agent to boot up from code it thinks is in
ROM, but is actually in Host local memory space.
B.1.2
In This Directory
README.txt—this appendix
main.c—C code routines
agentboot.s—ASM code routines
makefile—UNIX makefile
agentboot.txt—agentboot demo summary file including the source files and readme.
B.1.3
Assumptions
Running on a Sandpoint Reference Platform.
MPC8240/MPC107 based Agent in 32bit PCI slot #4 (Third from PMC). See Note 3
below on using alternate PCI slots.
Running DINK32 V12.0 or later.
B.1.4
Usage
Compile/Assemble the code below and link into S-Record format downloadable to
0x100000 using makefile or makefile_pc. Simply type make to use the UNIX
makefile, or type make -f makefile_pc to use the PC makefile.
Download the S-Record to Host local memory using dl -k at the Host’s DINK32
command prompt.
Launch the program using go 100000 at the Host’s DINK32 command prompt.
The program should set up the Agent to boot from the Host’s local memory space at
0x0100. The agent boot code located there will have the Agent write the value 777
(0x309) to Host local memory at 0x4C04. The user can verify this by using DINK
to display that memory location by typing md 4c04 at the DINK command prompt.
F
Freescale Semiconductor, Inc.
n
.