This document describes the silicon updates to the functional specifications for the TMS320C6201 silicon
releases 3.1, 3.0, 2.1, and 2.0.
1.1Quality and Reliability Conditions
TMX Definition
Texas Instruments (TI) does not warranty either (1) electrical performance to specification, or (2) product reliability
for products classified as “TMX.” By definition, the product has not completed data sheet verification or reliability
performance qualification according to TI Quality Systems Specifications.
The mere fact that a “TMX” device was tested over a particular temperature and voltage ranges should not, in any
way, be construed as a warranty of performance.
TMP Definition
TI does not warranty product reliability for products classified as “TMP.” By definition, the product has not
completed reliability performance qualification according to TI Quality Systems Specifications; however, products
are tested to a published electrical and mechanical specification.
SPRZ153
TMS Definition
Fully-qualified production device.
4
TMS320C6201 Silicon Errata
1.2Revision Identification
The device revision can be determined by the lot trace code marked on the top of the package. The
location for the lot trace codes for the GJL package is shown in Figure 1 and the revision numbers are
listed in Table 1.
Figure 1. Example, Lot Trace Code for TMS320C6201
SPRZ153
DSP
TMS320C6201GJL
Cxx–YMLLLLS
Lot trace code
NOTE: Qualified devices are marked with the letters “TMS” at the beginning of the device name, while nonqualified devices are marked with
the letters “TMX” at the beginning of the device name.
TMS320C6201GJL
C31–YMLLLLS
Lot trace code with revision 3.1
DSP
Table 1. Lot Trace Number Names
Lot Trace CodeSilicon RevisionComments
202.0
212.1
303.0
313.1
5
TMS320C6201 Silicon Errata
NO.
UNIT
2Changes to the TMS320C6201 Data Sheet (literature number SPRS051)
Table 2. Timing Requirements for Interrupt Response Cycles
SPRZ153
NO.
4t
5t
6t
NO.
1T
4T
d(CKO2L-IACKV)
d(CKO2L-INUMV)
d(CKO2L-INUMIV)
c(TCK)
h(TCKH-TDIV)
Figure 2. SBSRAM Read Timing (1/2 Rate SSCLK) (See Note)
SSCLK
CE
BE_ [3:0]
EA [21:2]
C6201B
MINMAX
Delay time, CLKOUT2 low to IACK valid–46ns
Delay time, CLKOUT2 low to INUMx valid6ns
Delay time, CLKOUT2 low to INUMx invalid–4ns
UNIT
Table 3. JTAG Test-Port Timing
C6201,
C6201B
MINMAX
Cycle time, TCK50ns
Hold time, TDI/TMS/TRST valid after TCK high9ns
43
BE1BE2BE3BE4
65
A1A2A3A4
UNIT
21
8
7
ED [31:0]
SSADS
SSOE
SSWE
Q1Q2Q3Q4
109
1211
NOTE: The CEx output setup and hold times are specified to be accurate relative to the clock cycle to which they are referenced, since
these timings are specified as minimums. However, the CE
in the data sheet in multiples of P ns. In other words, for output setup time, the CE
2P, …, or nP ns before the time specified by the data sheet. Similarly, for output hold time, the CE
output setup and hold time may be greater than that shown
x transition from high to low may happen P,
x low-to-high transition may
happen P, 2P, …, or nP ns after the time specified by the data sheet. This is indicated by the period of uncertainty for specs 1
and 2 in Figure 2, and Figure 3.
6
TMS320C6201 Silicon Errata
SPRZ153
Figure 3. SBSRAM Write Timing (1/2 Rate SSCLK) (See Note)
SSCLK
21
CE
BE_ [3:0]
EA [21:2]
ED [31:0]
SSADS
SSOE
SSWE
BE1
A1A2A3A4
Q1
BE2
Q2
BE3
Q3Q4
NOTE: The CEx output setup and hold times are specified to be accurate relative to the clock cycle to which they are referenced, since
these timings are specified as minimums. However, the CE
in the data sheet in multiples of P ns. In other words, for output setup time, the CEx
output setup and hold time may be greater than that shown
transition from high to low may happen P,
2P, …, or nP ns before the time specified by the data sheet. Similarly, for output hold time, the CEx
happen P, 2P, …, or nP ns after the time specified by the data sheet. This is indicated by the period of uncertainty for specs 1
and 2 in Figure 2, and Figure 3.
43
BE4
65
1413
109
1615
low-to-high transition may
7
TMS320C6201 Silicon Errata
3Silicon Revision 3.1 Known Design Exceptions to Functional Specifications
SPRZ153
Advisory 3.1.1
Revision(s) Affected:3.1, 3.0, 2.1, and 2.0
Details:The following problems exist when a DMA channel is paused at a block boundary:
Issues When Pausing at a Block Boundary
•DMA does not flush internal FIFO when a channel is paused across block boundary.
As a result, data from old and new blocks of that channel are in FIFO simultaneously.
This prevents other channels from using the FIFO for high performance until that
channel is restarted. Data is not lost when that channel is started again. (Internal
reference number C601299)
•For DMA transfers with autoinitialization, if a channel is paused just as the last transfer in a
block completes (just as the transfer counter reaches zero), none of the register reloads
take place (count, source address, and destination address). When the same channel is
restarted, the channel will not transfer anything due to the zero transfer count. This
problem only occurs at block boundaries. (Internal reference number C601258)
Workaround:Do not pause across block boundary if the internal FIFO is to be used by other channels for
high performance. For DMA transfers with autoinitialization, if a channel is paused with a zero
transfer count, manually reload all registers before restarting the channel.
Advisory 3.1.2
Revision(s) Affected:3.1, 3.0, 2.1, and 2.0
DMA: Transfer Incomplete When Pausing a Synchronized Transfer in Mid-frame
Details:If a frame-synchronized transfer is paused in mid-frame and then restarted again, a DMA
channel does not continue the transfer. Instead, the channel waits for synchronization. If the
channel is manually synchronized, it will properly complete the frame, but will immediately begin
the transfer of the next frame. This behavior occurs for both a software pause (setting START =
10b) and for an emulation halt (with EMOD = 1). (Internal reference number C601257)
Workaround:If pausing the DMA channel in software, do the following to restart:
1.Set the RSYNC bit in the Secondary Control Register.
2.Read the Transfer Count Register and then write back to Transfer Count Register. This
enables the present frame to transfer but will wait for the next sync event to trigger the
next frame transfer.
3.Set START to 01b or 11b.
If pausing the DMA channel with an emulation halt, do the following to restart:
1.Double-click on the Transfer Count Register and hit enter (rewrite current transfer count).
2.Set the RSYNC STAT bit in the Secondary Control Register (change 0xXXXX4XXX to
0xXXXX1XXX).
3.Run.
NOTE: The sequence of 1 and 2 is critical for an emulator halt (EMOD = 1), but not for the software
pause.
8
TMS320C6201 Silicon Errata
SPRZ153
Advisory 3.1.3
Revision(s) Affected:3.1, 3.0, 2.1, and 2.0
Details:If a DMA channel is configured to do a multiframe split-mode transfer with SRC_DIR = Index
Workaround:For multiframe transfers, use two DMA channels instead of using the split mode. Source Index
Advisory 3.1.4
Revision(s) Affected:3.1, 3.0, 2.1, and 2.0
Details:If any non-synchronized transfer (e.g., auto-init transfer) is stopped, and then the same
Workaround:Perform a nonsynchronized dummy transfer of one element to/from the same location before
DMA Multiframe Split-mode Transfers Source Address Indexing Not Functional
(11b), the source address is always modified using the Element Index, even during the last
element transfer of a frame. The transfer of the last element in a frame should index the
source address using the Frame Index instead of the Element Index. DST_DIR = 11b
functions properly. (Internal reference number C601256)
works properly for non-split-mode transfers.
DMA: Stopped Transfer Reprogrammed Does Not Wait for Sync
channel is programmed to do a write-synchronized transfer (e.g., split-mode transfer), the
write transfer does not wait for the sync event. (Internal reference number C601261)
starting the synchronized transfer.
Advisory 3.1.5
Revision(s) Affected:3.1, 3.0, 2.1, and 2.0
Details:For any DMA transfers with source/destination address postincrement/decrement, if the last
element to be transferred is aligned on a port boundary, then the DMA may freeze before
transferring this element. A port boundary is the address boundary between external memory
and program memory, between external memory and the peripheral address space, or
between program memory and the peripheral address space.
The following conditions cause DMA to freeze:
DMA Freezes if Postincrement/Decrement Across Port Boundary
•For non-sync and frame-sync transfers: if a channel is paused after the second-to-last
element is read, the DMA will freeze when the channel is then restarted with a request
to the address at a port boundary.
•For split-mode transfers or read/write-sync transfers: the DMA will freeze while
transferring the element aligned on the port boundary. A continuous burst transfer with
post-increment/decrement source/destination address does not exhibit this problem.
(Internal reference number C601300)
Workaround:Do not transfer to boundary addresses if the DMA source/destination address is
post-incremented/
decremented.
9
Loading...
+ 20 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.