Hi all,
My customer wants to monitor EMIF bandwitdh, and found omapconf has comannd "omapconf trace bw".
But it does not work for OMAP4430 and below error is reported. (It works on OMAP4460)
Is this known issue ? Do we have a workaround ?
// log starts from here//
shell@android:/ # omapconf trace bw
OMAPCONF (rev 1.65 built Wed Feb 6 16:43:27 CET 2013)
HW Platform:
Blaze_Tablet
OMAP4430 ES2.2 GP Devic[ 1608.374206] Unhandled fault: external abort on non-linefetch (0x1018) at 0x40325000
e (STANDARD performance (1.0GHz))
TWL6030 ES2.0 (EPROM rev6.0)
TWL6040 ES1.1
SW Build Details:
Build:
Version: blaze_tablet-userdebug 4.1.1 JRO03L 157 test-keys
Pastry: Jelly Bean
Type: userdebug
Date: Sun Sep 2 03:57:15 CDT 2012
Kernel:
Version: 3.0.31
Author: a0273819@magpie
Toolchain: gcc version 4.4.3 (GCC)
Type: #1 SMP PREEMPT
Date: Sun Sep 2 03:53:37 CDT 2012
Counter: 0 Master: alldmm Transaction: w Probe: emif1
Counter: 1 Master: alldmm Transaction: w Probe: emif2
Counter: 2 Master: alldmm Transaction: r Probe: emif1
Counter: 3 Master: alldmm Transaction: r Probe: emif2
delay in us: 1000000
overflow delay in us: 1000000 (iterations=1)
accumulation type: 2
iterations (0=infinite): 0
Overflow counter index: DISABLED (overflow delay used)
Overflow threshold: DISABLED (overflow delay used)
!!! OUPS... MEMORY ERROR @ 0x00000000 !!!
Are you sure that:
MEMORY ADDRESS IS VALID?
TARGETED MODULE IS CLOCKED?
// log ends here//
Thanks and regards,
Koichiro
