Honored Contributor
Honored ContributorI think your results show pretty clearly that, in some cases, tightly coupled memory is not worth the hassle.
On the other hand, here are some cases in which tightly coupled instruction memory can be very helpful: -It is a way to have some code "cached" that is guaranteed to not contend with other parts of your code, so you can avoid potential "thrashing" of the cache. Since the processor only has direct-map caches, it is easy to have two functions occupying the same cache lines and always bumping each-other out. -If other components or processors are contending for your SDRAM or on-chip mem, and you want guaranteed access to some code. In your case, it looks like all the important functions fit in the cache and there is no contention with other components. Is that true?
