TMS320C6201 Silicon Errata | SPRZ153 |
Advisory 3.1.9
Revision(s) Affected:
Details:
Workaround:
Alternative: If a
Cache During Emulation With Extremely Slow External Memory
3.1, 3.0, 2.1, and 2.0
If a program requests fetch packet “A” followed immediately by fetch packet “B”, and all of the following four conditions are true:
1. A and B are separated by a multiple of 64K in memory (i.e., they will occupy the same cache frame)
2. B is currently located in cache
3. You are using the emulator to
4. The code is running off of an extremely slow external memory that transfers one
Then A will be registered as a “miss” and B will be registered as a “hit”. B will not be reloaded into cache, and A will be executed twice. This condition is extremely rare because B has to be in cache memory, and must be the next fetch packet requested after A (which is not in cache memory). In addition, this problem only occurs if you
•Do not
•Do not use an extremely slow external memory (transfers one
11