Forums

I also tried using  "do opm 6 -f" and the new setting still does not stick but always return to OPM2.

David,

In ARM_A8_01_02 release, opp mode can be changed from Eboot. Did you upgrade your Eboot to 01_02 release?

"opm" command only works in the build with KITL enabled. In a build without KITL, you have to change it in EBoot right now.

Thanks,

Tao

The problem is not with the shell command. All other shell commands work just fine.

I have an image built with TI Shell extensions included. I open a dos prompt and do the"do" command on the device.

The symptoms are the same whether I use kitl shell or dos shell.

I am using A8_01.02 all be it a slightly modified version for my platform.

I see no setting for adjusting OPM in in eboot. Only the default startup setting in the .bat file.

The issue is I need to programactly change the opm at run time.

David,

With ARM_A8_01.02, the Eboot main menu is shown as follows, the opp can be changed from "b"

--------------------------------------------------------------------------------
 Main Menu
--------------------------------------------------------------------------------
 [1] Show Current Settings
 [2] Select Boot Device
 [3] Select KITL (Debug) Device
 [4] Network Settings
 [5] SDCard Settings
 [6] Set Device ID
 [7] Save Settings
 [8] Flash Management
 [9] Enable/Disable OAL Retail Messages
 [a] Select Display Resolution
 [b] Select OPP Mode
 [0] Exit and Continue

To change to 720MHz MPU speed, "OpmCeiling" registry setting should be changed from 5 to 6. I already tried out this change, and it works for me.

"OPM" command only works from KITL build(Target Control command window), this is because in the build without KITL, when the "do" command exit, it will Close DVFS Constraint, which results in OPP mode changed back to the original settings. This is exactly what you observed - "If I do a "do opm 6" I see it set to OPM6 but then it pops back to OPM2 right away."

A couple of questions:

If you change to other OPMs except OPM6, does it work for you? Could you please post your logs when you change "OPP" modes?

Thanks,

Tao

David,

Here is the log from Target Control window for your reference.

Windows CE>opm ?

Operating Mode Choices
 6 - MPU[720Mhz @ 1.35V],  IVA2[520Mhz @ 1.35V],  CORE[332Mhz @ 1.15V]
 5 - MPU[600Mhz @ 1.35V],  IVA2[430Mhz @ 1.35V],  CORE[332Mhz @ 1.15V]
 4 - MPU[550Mhz @ 1.27V],  IVA2[400Mhz @ 1.27V],  CORE[332Mhz @ 1.15V]
 3 - MPU[500Mhz @ 1.20V],  IVA2[360Mhz @ 1.20V],  CORE[332Mhz @ 1.15V]
 2 - MPU[250Mhz @ 1.05V],  IVA2[180Mhz @ 1.05V],  CORE[332Mhz @ 1.15V]
 1 - MPU[125Mhz @ 0.975V], IVA2[ 90Mhz @ 0.975V], CORE[332Mhz @ 1.15V]
 0 - MPU[125Mhz @ 0.975V], IVA2[ 90Mhz @ 0.975V], CORE[166Mhz @ 1.05V]
Current Frequencies: MPU-250.00, IVA-180.00, CORE-332.00

Windows CE>opm 6 -f


Windows CE>opm ?

Operating Mode Choices
 6 - MPU[720Mhz @ 1.35V],  IVA2[520Mhz @ 1.35V],  CORE[332Mhz @ 1.15V]
 5 - MPU[600Mhz @ 1.35V],  IVA2[430Mhz @ 1.35V],  CORE[332Mhz @ 1.15V]
 4 - MPU[550Mhz @ 1.27V],  IVA2[400Mhz @ 1.27V],  CORE[332Mhz @ 1.15V]
 3 - MPU[500Mhz @ 1.20V],  IVA2[360Mhz @ 1.20V],  CORE[332Mhz @ 1.15V]
 2 - MPU[250Mhz @ 1.05V],  IVA2[180Mhz @ 1.05V],  CORE[332Mhz @ 1.15V]
 1 - MPU[125Mhz @ 0.975V], IVA2[ 90Mhz @ 0.975V], CORE[332Mhz @ 1.15V]
 0 - MPU[125Mhz @ 0.975V], IVA2[ 90Mhz @ 0.975V], CORE[166Mhz @ 1.05V]
Current Frequencies: MPU-720.00, IVA-520.00, CORE-332.00

Windows CE>

Thanks,

Tao