SM320F2808-EP Datasheet, PDF (32/118 Pages) Texas Instruments – Digital Signal Processors

SM320F2808-EP, SM320F2806-EP
SM320F2801-EP
Digital Signal Processors
SGLS316A – MARCH 2006 – REVISED FEBRUARY 2007
www.ti.com
Table 3-7. Peripheral Frame 1 Registers⁽¹⁾⁽²⁾
NAME
ADDRESS RANGE
SIZE (x16)
ACCESS TYPE
eCANA Registers
0x6000
0x60FF
256
(128 x 32)
Some eCAN control registers (and selected bits in other eCAN
control registers) are EALLOW-protected.
eCANA Mailbox RAM
0x6100
0x61FF
256
(128 x 32)
Not EALLOW-protected
eCANB Registers
0x6200
0x62FF
256
(128 x 32)
Some eCAN control registers (and selected bits in other eCAN
control registers) are EALLOW-protected.
eCANB Mailbox RAM
0x6300
0x63FF
256
(128 x 32)
Not EALLOW-protected
ePWM1 Registers
0x6800
0x683F
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2
ePWM2 Registers
0x6840
0x687F
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2.
ePWM3 Registers
0x6880
0x68BF
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2.
ePWM4 Registers
0x68C0
0x68FF
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2.
ePWM5 Registers
0x6900
0x693F
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2.
ePWM6 Registers
0x6940
0x697F
64
(32 x 32)
Some ePWM registers are EALLOW protected.
See Table 4-2.
eCAP1 Registers
0x6A00
0x6A1F
32
(16 x 32)
Not EALLOW protected
eCAP2 Registers
0x6A20
0x6A3F
32
(16 x 32)
Not EALLOW protected
eCAP3 Registers
0x6A40
0x6A5F
32
(16 x 32)
Not EALLOW protected
eCAP4 Registers
0x6A60
0x6A7F
32
(16 x 32)
Not EALLOW protected
eQEP1 Registers
0x6B00
0x6B3F
64
(32 x 32)
Not EALLOW protected
eQEP2 Registers
0x6B40
0x6B7F
64
(32 x 32)
Not EALLOW protected
GPIO Control Registers
0x6F80
0x6FBF
128
(64 x 32)
EALLOW protected
GPIO Data Registers
0x6FC0
0x6FDF
32
(16 x 32)
Not EALLOW protected
GPIO Interrupt and LPM
Select Registers
0x6FE0
0x6FFF
32
(16 x 32)
EALLOW protected
(1) The eCAN control registers only support 32-bit read/write operations. All 32-bit accesses are aligned to even address boundaries.
(2) Missing segments of memory space are reserved and should not be used in applications.
32
Functional Overview
Submit Documentation Feedback