| Electronic Components Datasheet Search |
|
TMS320C6472 Datasheet(PDF) 21 Page - Texas Instruments |
|
|
|
|||||||||||||||||||||||||||||
TMS320C6472 Datasheet(HTML) 21 Page - Texas Instruments |
|
21 / 65 page ![]() 31 X+1 X 6 5 4 2 1 0 Tag Set Offset Sub-line Bank Byte www.ti.com Silicon Revision 2.0 Usage Notes and Known Design Exceptions to Functional Specifications of two addresses. The mapping of an address to a location in L1D cache is shown in Figure 2. The value X is determined by how large the L1D cache is in the particular application (see Table 10). Figure 2. L1D Cache Address Mapping Table 10. Value of X for L1D Cache AMOUNT OF L1D CACHE X BIT POSITION 0KB N/A 4KB 10 8KB 11 16KB 12 32KB 13 If you use the default configuration, 32KB, as an example, bits [13:6] are a set match if they are identical in two different addresses. Some examples of set matches are shown below: • 0x0080 2A80 00000000100000000010101010000000 • 0x8000 2A80 10000000100000000010101010000000 • 0x0080 2A8A 00000000100000000010101010001010 • This results in a cache miss from the CPU for an external address and sends a read request to L2 cache for the line (and possibly to the external source on an L2 cache miss or if no L2 cache is present). The results of the above cause the following: L2 sends both the return data for the L1D read miss request (response of Step 3 above) and the data for the snoop-write (response of Step 2 above). The L1D commits the snoop-write data after the L2 return data. As a result, L1D now holds the wrong data for the external address (Cache Line B) and commits the data to cache. Cache Line B remains marked "clean." If the program does not write to the uncorrupted portion of the line and does not read the corrupted portion of the line, the corruption goes unnoticed. If the program writes to the uncorrupted portion of the line, the corrupted data gets written back to L2 cache and/or external memory. Otherwise, the corruption disappears when L1D discards the line. Cache lines holding external addresses are the only cache lines that exhibit corruption. Corruption only happens when DMA buffers in UMAP1 get cached in L1D. Additionally, corruption only happens when the DMA buffer is clean, meaning that it gets discarded without generating a victim. Thus, this affects buffers where the DMA writes and the CPU reads. It does not affect buffers that the CPU only writes and/or DMA only reads. One can identify this bug unambiguously by examining the corrupted memory range in CCStudio using the cache tag viewer. The corrupted data shows up in the include L1D view in a memory window, but not in the exclude L1D view. The cache tag viewer should indicate that the line is also "clean" and the corrupt data should also be visible in its intended destination, which must be in UMAP1 and map to the same L1D set as the corrupted line. Figure 3 shows the flow of these operations, the incorrect order that causes the bug, and the correct order. The blue line is Cache Line A and the yellow line is Cache line B. 21 SPRZ300 – October 2009 TMS320C6472 DSP Silicon Revisions 2.0, 1.2, 1.1, 1.0 Submit Documentation Feedback Copyright © 2009, Texas Instruments Incorporated |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |