• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 459 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

720Mhz support

DavidVescovi
Genius 5470 points
Other Parts Discussed in Thread: OMAP3530

I have been trying to get 720Mhz support OMAP3530 A8_1_02 BSP.

I have a OSDESIGN with PMExt and DVFS Constrained Adapter selected. I do not have any Policy Adapters selected.

I modified the "OpmCeiling" registry setting from the default 5 to 6.

The "OpmInit" is still set at default 5.

I noticed I am still getting console messages showing different OPM settings after powerup even thought I am not changing anything.

The final message shows OPM2 and the BSP Information from the control panel shows 250Mhz. (again I DO NOT have any Policy Adapters selected from the catalog).

If I do a "do opm ?" I see Current frequencies: MPU-250.00 ...

If I do a "do opm 6" I see it set to OPM6 but then it pops back to OPM2 right away.

If I do a "do opm ?" again it still shows MPU-250.00

So how do I get 720Mhz support?

How can I manually scale the operating frequency up and down?

  • 0
    Genius 5470 points

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

  • 0 in reply to DavidVescovi
    TI__Expert 4155 points

    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

  • 0 in reply to Tao Zhang
    Genius 5470 points

    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.

  • 0 in reply to DavidVescovi
    TI__Expert 4155 points

    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

  • 0 in reply to Tao Zhang
    Genius 5470 points

    OK I better understand now. I will retest again using kitl version of "do".

    I missed the new opm setting in the boot loader as I migrated from an earlier release.

    Thank you for the quick feedback.

     

  • 0 in reply to DavidVescovi
    TI__Expert 4155 points

    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

  • 0 in reply to Tao Zhang
    Genius 5470 points

    After upgrading my BSPs bootloader to sync with A8_1_02 all is fine.

    Speed settings now work as expected.

    Thank you.

     

    DV