Other Parts Discussed in Thread: BIOSLINUXMCSDK
Hi,
I recently got K2H evm (Rev 3.0) and started its evaluation.
And now I have a trouble to work with OProfile.
When I started OProfile, I had the following error :-
command:
opcontrol --no-vmlinux
error:
cpu_type 'unset' is not valid
OProfile manual says that it supports timer interrupt mode as below:
http://oprofile.sourceforge.net/doc/detailed-parameters.html#timer
So I tried to OProfile with timer interrupt mode (OProfile had been built as a module and
loaded later by "insmod oprofile.ko timer=1") and OProfile itself got working now,
but its report looks curious.
The following is the result of opreport command when executing a simple hello world application:-
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
TIMER:0|
samples| %|
------------------
6753 99.9704 no-vmlinux
1 0.0148 bash
1 0.0148 libc-2.15.so
As you see, timer speed looks like 0 Mhz.
I'm wondering if OProfile is really working correctly or not...
Could you please suggest me if this is expected, or the way to work without timer interrupt mode ?
Lastly, I'm using the latest version of MCSDK, i.e., v3.00. It is available from:
http://www.ti.com/tool/bioslinuxmcsdk
Best Regards,
Kawada