Hi,
I noticed that some Hardware Trace configurations contain a workaround for the MFENCE issue in Keystone devices. But some configurations like "PC Trace" don't create a trace job for this issue.
Trace configurations with MFENCE workaround:
- Statistical Function Profiling
- Stall Profiling
- Cache Analysis
Trace configurations without MFENCE workaround:
- Function Profiling
- Code Coverage
- PC Trace
- Custom Core Trace
Is there any particular reason for the difference?
I'm using CCS v6.1, but I also noticed this in v5.5.
Thanks,
Ralf
