HPI Registers
7-17
Host-Port Interface
Figure 7–10. HPIC Register
31
21
20
19
18
17
16
rsvd
HRDY
HINT
DSPINT
HWOB
HR,CR,+0
HRW,CR,+0
HR,CR,+0
HRW,CR,+0
HRW,CR,+0
HRW,CR,+0
15
5
4
3
2
1
0
rsvd
FETCH
HRDY
HINT
DSPINT
HWOB
HR,CR,+0
HRW,CR,+0
HR,CR,+1
HRW,CRW,+0
HRW,CRW,+0
HRW,CR,+0
Table 7–6. HPI Control Register (HPIC) Bit Descriptions
Bit
Description
Section
HWOB
Halfword ordering bit
If HWOB = 1, the first halfword is least significant. If HWOB = 0, the first halfword
is most significant. HWOB affects both data and address transfers. Only the host
can modify this bit. HWOB must be initialized before the first data or address reg-
ister access.
7.4
DSPINT
The host processor-to-CPU/DMA interrupt
7.3.3
HINT
DSP-to-host interrupt. The inverted value of this bit determines the state of the
CPU HINT output.
7.3.4
HRDY
Ready signal to host. Not masked by HCS (as the HRDY pin is).
If HRDY = 0, the internal bus is waiting for an HPI data access request to finish.
7.3.2
FETCH
Host fetch request
The value read by the host or CPU from this register field is always 0.
The host writes a 1 to this bit to request a fetch into HPID of the word at the
address pointed to by HPIA. The 1 is never actually written to this bit, however.
7.3.2
7.3.2
Software Handshaking Using HRDY and FETCH
As described previously, the HRDY pin can indicate to a host that an HPID
access has not finished. For example, the current HPID access can be waiting
for a previous HPID access write to finish or for a previous HPID prefetched read
to finish. Also, the current HPID read access can be waiting for its requested
data to arrive. The HRDY and FETCH bits in the HPIC register allow for a soft-
ware handshake that allows an HPI connection in systems in which a hardware
ready control is not desired. The FETCH and HRDY bits can be used to perform
a read transfer as follows: