TM1100 Preliminary Data Book
Philips Semiconductors
3-8
PRELIMINARY INFORMATION
File: arch.fm5, modified 7/23/99
Some devices can autonomously access data memory
(DMA) and most devices can cause CPU interrupts.
The MMIO aperture is 2 MB in size and initially located at
address 0xEFE00000 on RESET; it is relocated by the
PCI BIOS for PC hosted TM1100 boards; its final loca-
tion is determined by the boot EEPROM for stand-alone
mation.
Figure 3-5 gives a detailed overview of the
MMIO memory map (addresses used are offsets with re-
spect to the MMIO base). The operating system on
TM1100 can change MMIO_BASE by writing to the
MMIO_BASE MMIO location. User programs should not
attempt this. Refer to the TriMedia SDE Reference Man-
ual for the standard method to access the device regis-
ters from C language device drivers.
Only 32-bit load and store operations are allowed to ac-
cess MMIO registers in the MMIO address aperture. The
results are undefined for other loads and stores. Reads
from non-existent MMIO registers return undefined val-
ues. Writes to nonexistent MMIO registers time out.
There are no sideeffects of accesses to non-existent
MMIO registers. The state of the PCSW BSX bit has no
effect on the result of MMIO accesses.
The Icache tag & LRU bit access aperture gives the
DSPCPU read-only access to the Icache status. Refer
details.
The EXCVEC MMIO location is explained in
Sectiondescribes
the locations that deal with the setup and handling of in-
terrupts: ISETTING, IPENDING, ICLEAR, IMASK and
the interrupt vectors. The timer MMIO locations are de-
The instruction and
Support.” The MMIO locations of each device are treat-
ed in the respective device chapters.
3.5
SPECIAL EVENT HANDLING
The TM1100 microprocessor responds to the special
events shown in
Table 3-9, ordered by priority.
With the exception of RESET, which is enabled at all
times, the architecture of the DSPCPU allows special
event handling to begin only during an
interruptible jump
operation (ijmpt, ijmpf or ijmpi) that succeeds (i.e., is a
taken jump). EXC, NMI and INT handling can be initiated
during handling of an EXC or an INT, but
only during suc-
cessful interruptible jumps.
The
instruction scheduler uses interruptible jumps exclu-
sively for inter-decision tree jumps. Hence, within a deci-
sion tree, no special-event processing can be initiated. If
a tree-to-tree jump is taken, special-event processing is
allowed. Since the only registers live at this point (i.e.,
that contain useful data) are the
global registers allocat-
0x00 0000
Reserved
for
Future Use
Reserved
for
Future Use
0x10 3800
JTAG Interface
0x10 3400
I2C Interface
0x10 3000
PCI Interface
0x10 2C00
SSI Interface
0x10 2800
VLD Coprocessor
0x10 2400
Image Coprocessor (ICP)
0x10 2000
Audio Out
0x10 1C00
Audio In
0x10 1800
Video Out
0x10 1400
Video In
0x10 1000
Debug Support
0x10 0C00
Timers
0x10 0800
Vectored Interrupt Controller
0x10 0400
MMIO Base
0x10 0000
Main-Memory, Cache Control
0x1F FFFFF
0x10 1200
data breakpoints
0x10 1000
instruction breakpoints
0x10 0C60
systimer
0x10 0C40
timer3
0x10 0C20
timer2
0x10 0C00
timer1
0x10 08Fc
intvec31
0x10 08F8
intvec30
0x10 0888
intvec2
0x10 0884
intvec1
0x10 0880
intvec0
0x10 0828
imask
0x10 0824
iclear
0x10 0820
ipending
0x10 081C
isetting3
0x10 0818
isetting2
0x10 0814
isetting1
0x10 0810
isetting0
0x10 0800
excvec
0x10 0400
MMIO_BASE
0x10 0004
DRAM_LIMIT
0x10 0000
DRAM_BASE
0x01 0000
Icache tags & LRU (r/o)
Figure 3-5. Memory map of MMIO address space (addresses are offset from MMIO_BASE).