"C6414 Device Cycle Accurate Simulator" profiling woes
when running profiling tests on the "C6414 Device Cycle Accurate
Simulator", I get different profile numbers when I exceed the 1MB core
memory than when my application and test reside within it.
My problem is that that the core-application is approaching the 1MB
Is there a way, without having to break up the application and
test-code into smaller portions, to not suffer the changing profile
b.t.w. I do not experience profile-number differences when testing
the same with the CPU-Cycle-Accurate-Simulator.