CC1110Fx / CC1111Fx
Interrupt Number
Interrupt Name
0
RFTXRX
16
8
RF
Polling sequence
DMA
1
ADC
9
T1
2
URX0
10
3
T2
URX1 / I2SRX
11
4
T3
ENC
12
5
T4
ST
13
6
P0INT / (USB Resume)
P2INT / USB
UTX0
7
14
15
17
URX1 / I2STX
P1INT
WDT
Table 43: Interrupt Polling Sequence
12 Debug Interface
The debug interface uses the I/O pins P2_1 as
Debug Data and P2_2 as Debug Clock during
Debug mode. These I/O pins can be used as
general purpose I/O only while the device is
not in Debug mode. Thus the debug interface
does not interfere with any peripheral I/O pins.
The CC1110Fx/CC1111Fx includes an on-chip
debug module which communicates over a
two-wire interface. The debug interface allows
programming of the on-chip flash. It also
provides access to memory and registers
contents, and debug features such as
breakpoints, single-stepping, and register
modification.
12.1 Debug Mode
Debug mode is entered by forcing two rising
edge transitions on pin P2_2 (Debug Clock)
while the RESET_N input is held low.
Note: Debugging of PM2 and PM3 is not
supported. Also note that CLKCON.CLKSPD
must be 000 or 001 when using the debug
interface
While in Debug mode pin P2_1 is the Debug
Data bi-directional pin and P2_2 is the Debug
Clock input pin.
12.2 Debug Communication
The debug interface uses an SPI-like two-wire
interface consisting of the P2_1 (Debug Data)
and P2_2 (Debug Clock) pins. Data is driven
on the bi-directional Debug Data pin at the
positive edge of Debug Clock and data is
sampled on the negative edge of this clock.
Debug commands are sent by an external host
and consist of 1 to 4 output bytes (including
command byte) from the host and an optional
input byte read by the host. Command and
data is transferred with MSB first. Figure 17
shows a timing diagram of data on the debug
interface.
SWRS033E
Page 71 of 239
TAOS [ TEXAS ADVANCED OPTOELECTRONIC SOLUTIONS ]
